hw/nvme: SR-IOV with Virtualization Enhancements
v7 cover hw/nvme: SR-IOV with Virtualization Enhancements
Resubmitting v6 as v7 since Patchew got lost with my sophisticated CC of all maintainers just for the cover letter.
Changes since v5:
- Fixed PCI hotplug issue related to deleting VF twice
- Corrected error messages for SR-IOV parameters
- Rebased on master, patches for PCI got pulled into the tree
- Added Reviewed-by labels
Lukasz Maniak (4):
hw/nvme: Add support for SR-IOV
hw/nvme: Add support for Primary Controller Capabilities hw/nvme: Add support for Secondary Controller List
docs: Add documentation for SR-IOV and Virtualization Enhancements
Łukasz Gieryk (8):
hw/nvme: Implement the Function Level Reset
hw/nvme: Make max_ioqpairs and msix_qsize configurable in runtime hw/nvme: Remove reg_size variable and update BAR0 size calculation hw/nvme: Calculate BAR attributes in a function hw/nvme: Initialize capability structures for primary/secondary
controllers
hw/nvme: Add support for the Virtualization Management command hw/nvme: Update the initalization place for the AER queue hw/acpi: Make the PCI hot-plug aware of SR-IOV
docs/system/devices/nvme.rst | 82 +++++ hw/acpi/pcihp.c | 6 +- hw/nvme/ctrl.c | 673 ++++++++++++++++++++++++++++++++--- hw/nvme/ns.c | 2 +- hw/nvme/nvme.h | 55 ++- hw/nvme/subsys.c | 75 +++- hw/nvme/trace-events | 6 + include/block/nvme.h | 65 ++++ include/hw/pci/pci_ids.h | 1 + 9 files changed, 909 insertions(+), 56 deletions(-)
Signature · 1 line
2.25.1
PATCH v7 1/12 hw/nvme: Add support for SR-IOV
This patch implements initial support for Single Root I/O Virtualization on an NVMe device.
Essentially, it allows to define the maximum number of virtual functions supported by the NVMe controller via sriov_max_vfs parameter.
Passing a non-zero value to sriov_max_vfs triggers reporting of SR-IOV capability by a physical controller and ARI capability by both the physical and virtual function devices.
NVMe controllers created via virtual functions mirror functionally the physical controller, which may not entirely be the case, thus consideration would be needed on the way to limit the capabilities of the VF.
NVMe subsystem is required for the use of SR-IOV.
--- hw/nvme/ctrl.c | 85 ++++++++++++++++++++++++++++++++++++++-- hw/nvme/nvme.h | 3 +- include/hw/pci/pci_ids.h | 1 + 3 files changed, 85 insertions(+), 4 deletions(-)
hw/nvme/ctrl.c +82 -3
@@ -35,6 +35,7 @@* mdts=<N[optional]>,vsl=<N[optional]>, \ * zoned.zasl=<N[optional]>, \ * zoned.auto_transition=<on|off[optional]>, \ +* sriov_max_vfs=<N[optional]> \ * subsys=<subsys_id> * -device nvme-ns,drive=<drive_id>,bus=<bus_name>,nsid=<nsid>,\ * zoned=<true|false[optional]>, \
@@ -106,6 +107,12 @@* transitioned to zone state closed for resource management purposes. * Defaults to 'on'. * +* - `sriov_max_vfs` +* Indicates the maximum number of PCIe virtual functions supported +* by the controller. The default value is 0. Specifying a non-zero value +* enables reporting of both SR-IOV and ARI capabilities by the NVMe device. +* Virtual function controllers will not report SR-IOV capability. +* * nvme namespace device parameters * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * - `shared`
@@ -160,6 +167,7 @@#include "sysemu/block-backend.h" #include "sysemu/hostmem.h" #include "hw/pci/msix.h" +#include "hw/pci/pcie_sriov.h" #include "migration/vmstate.h" #include "nvme.h"
@@ -176,6 +184,9 @@#define NVME_TEMPERATURE_CRITICAL 0x175#define NVME_NUM_FW_SLOTS 1#define NVME_DEFAULT_MAX_ZA_SIZE (128 * KiB) +#define NVME_MAX_VFS 127 +#define NVME_VF_OFFSET 0x1 +#define NVME_VF_STRIDE 1#define NVME_GUEST_ERR (trace, fmt, ...) \ do { \
@@ -5886,6 +5897,10 @@ static void nvme_ctrl_reset(NvmeCtrl *n)g_free (event); } +if (!pci_is_vf (&n->parent_obj) && n->params.sriov_max_vfs) { +pcie_sriov_pf_disable_vfs (&n->parent_obj); + } + n->aer_queued =0 ; n->outstanding_aers =0 ; n->qs_created = false;
@@ -6567,6 +6582,29 @@ static void nvme_check_constraints(NvmeCtrl *n, Error **errp)error_setg (errp,"vsl must be non-zero" );return ; } + +if (params->sriov_max_vfs) { +if (!n->subsys) { +error_setg (errp,"subsystem is required for the use of SR-IOV" ); +return ; + } + +if (params->sriov_max_vfs >NVME_MAX_VFS ) { +error_setg (errp,"sriov_max_vfs must be between 0 and %d" , +NVME_MAX_VFS ); +return ; + } + +if (params->cmb_size_mb) { +error_setg (errp,"CMB is not supported with SR-IOV" ); +return ; + } + +if (n->pmr.dev) { +error_setg (errp,"PMR is not supported with SR-IOV" ); +return ; + } + } }static void nvme_init_state (NvmeCtrl *n)
@@ -6624,6 +6662,20 @@ static void nvme_init_pmr(NvmeCtrl *n, PCIDevice *pci_dev)memory_region_set_enabled (&n->pmr.dev->mr, false); } +static void nvme_init_sriov (NvmeCtrl *n,PCIDevice *pci_dev,uint16_t offset, +uint64_t bar_size) +{ +uint16_t vf_dev_id = n->params.use_intel_id ? +PCI_DEVICE_ID_INTEL_NVME :PCI_DEVICE_ID_REDHAT_NVME ; + +pcie_sriov_pf_init (pci_dev, offset,"nvme" , vf_dev_id, + n->params.sriov_max_vfs, n->params.sriov_max_vfs, +NVME_VF_OFFSET ,NVME_VF_STRIDE ); + +pcie_sriov_pf_init_vf_bar (pci_dev,0 ,PCI_BASE_ADDRESS_SPACE_MEMORY | +PCI_BASE_ADDRESS_MEM_TYPE_64 , bar_size); +} +static int nvme_init_pci (NvmeCtrl *n,PCIDevice *pci_dev,Error **errp) {uint8_t *pci_conf = pci_dev->config;
@@ -6638,7 +6690,7 @@ static int nvme_init_pci(NvmeCtrl *n, PCIDevice *pci_dev, Error **errp)if (n->params.use_intel_id) {pci_config_set_vendor_id (pci_conf,PCI_VENDOR_ID_INTEL ); -pci_config_set_device_id (pci_conf,0x5845 ); +pci_config_set_device_id (pci_conf,PCI_DEVICE_ID_INTEL_NVME ); }else {pci_config_set_vendor_id (pci_conf,PCI_VENDOR_ID_REDHAT );pci_config_set_device_id (pci_conf,PCI_DEVICE_ID_REDHAT_NVME );
@@ -6646,6 +6698,9 @@ static int nvme_init_pci(NvmeCtrl *n, PCIDevice *pci_dev, Error **errp)pci_config_set_class (pci_conf,PCI_CLASS_STORAGE_EXPRESS );pcie_endpoint_cap_init (pci_dev,0x80 ); +if (n->params.sriov_max_vfs) { +pcie_ari_init (pci_dev,0x100 ,1 ); + } bar_size =QEMU_ALIGN_UP (n->reg_size,4 * KiB); msix_table_offset = bar_size;
@@ -6664,8 +6719,12 @@ static int nvme_init_pci(NvmeCtrl *n, PCIDevice *pci_dev, Error **errp) n->reg_size);memory_region_add_subregion (&n->bar0,0 , &n->iomem); -pci_register_bar (pci_dev,0 ,PCI_BASE_ADDRESS_SPACE_MEMORY | -PCI_BASE_ADDRESS_MEM_TYPE_64 , &n->bar0); +if (pci_is_vf (pci_dev)) { +pcie_sriov_vf_register_bar (pci_dev,0 , &n->bar0); + }else { +pci_register_bar (pci_dev,0 ,PCI_BASE_ADDRESS_SPACE_MEMORY | +PCI_BASE_ADDRESS_MEM_TYPE_64 , &n->bar0); + } ret =msix_init (pci_dev, n->params.msix_qsize, &n->bar0,0 , msix_table_offset, &n->bar0,0 , msix_pba_offset,0 , &err);
@@ -6686,6 +6745,10 @@ static int nvme_init_pci(NvmeCtrl *n, PCIDevice *pci_dev, Error **errp)nvme_init_pmr (n, pci_dev); } +if (!pci_is_vf (pci_dev) && n->params.sriov_max_vfs) { +nvme_init_sriov (n, pci_dev,0x120 , bar_size); + } +return 0 ; }
@@ -6836,6 +6899,16 @@ static void nvme_realize(PCIDevice *pci_dev, Error **errp)NvmeCtrl *n =NVME (pci_dev);NvmeNamespace *ns;Error *local_err =NULL ; +NvmeCtrl *pn =NVME (pcie_sriov_get_pf (pci_dev)); + +if (pci_is_vf (pci_dev)) { +/* +* VFs derive settings from the parent. PF's lifespan exceeds +* that of VF's, so it's safe to share params.serial. +*/ +memcpy (&n->params, &pn->params,sizeof (NvmeParams)); + n->subsys = pn->subsys; + }nvme_check_constraints (n, &local_err);if (local_err) {
@@ -6900,6 +6973,11 @@ static void nvme_exit(PCIDevice *pci_dev)if (n->pmr.dev) {host_memory_backend_set_mapped (n->pmr.dev, false); } + +if (!pci_is_vf (pci_dev) && n->params.sriov_max_vfs) { +pcie_sriov_pf_exit (pci_dev); + } +msix_uninit (pci_dev, &n->bar0, &n->bar0);memory_region_del_subregion (&n->bar0, &n->iomem); }
@@ -6924,6 +7002,7 @@ static Property nvme_props[] = {DEFINE_PROP_UINT8 ("zoned.zasl" , NvmeCtrl, params.zasl,0 ),DEFINE_PROP_BOOL ("zoned.auto_transition" , NvmeCtrl, params.auto_transition_zones, true), +DEFINE_PROP_UINT8 ("sriov_max_vfs" , NvmeCtrl, params.sriov_max_vfs,0 ), DEFINE_PROP_END_OF_LIST(), };
hw/nvme/nvme.h +2 -1
@@ -24,7 +24,7 @@#include "block/nvme.h" -#define NVME_MAX_CONTROLLERS 32 +#define NVME_MAX_CONTROLLERS 256#define NVME_MAX_NAMESPACES 256#define NVME_EUI64_DEFAULT ((uint64_t)0x5254000000000000)
@@ -405,6 +405,7 @@ typedef struct NvmeParams {uint8_t zasl;bool auto_transition_zones;bool legacy_cmb; +uint8_t sriov_max_vfs; } NvmeParams; typedef struct NvmeCtrl {
include/hw/pci/pci_ids.h +1 -0
@@ -237,6 +237,7 @@#define PCI_DEVICE_ID_INTEL_82801BA_11 0x244e#define PCI_DEVICE_ID_INTEL_82801D 0x24CD#define PCI_DEVICE_ID_INTEL_ESB_9 0x25ab +#define PCI_DEVICE_ID_INTEL_NVME 0x5845#define PCI_DEVICE_ID_INTEL_82371SB_0 0x7000#define PCI_DEVICE_ID_INTEL_82371SB_1 0x7010#define PCI_DEVICE_ID_INTEL_82371SB_2 0x7020
Signature · 1 line
2.25.1
PATCH v7 2/12 hw/nvme: Add support for Primary Controller Capabilities
In reply to Lukasz ManiakImplementation of Primary Controller Capabilities data structure (Identify command with CNS value of 14h).
Currently, the command returns only ID of a primary controller. Handling of remaining fields are added in subsequent patches implementing virtualization enhancements.
--- hw/nvme/ctrl.c | 23 ++++++++++++++++++----- hw/nvme/nvme.h | 2 ++ hw/nvme/trace-events | 1 + include/block/nvme.h | 23 +++++++++++++++++++++++ 4 files changed, 44 insertions(+), 5 deletions(-)
hw/nvme/ctrl.c +18 -5
@@ -4799,6 +4799,14 @@ static uint16_t nvme_identify_ctrl_list(NvmeCtrl *n, NvmeRequest *req,return nvme_c2h (n, (uint8_t *)list,sizeof (list), req); } +static uint16_t nvme_identify_pri_ctrl_cap (NvmeCtrl *n,NvmeRequest *req) +{ +trace_pci_nvme_identify_pri_ctrl_cap (le16_to_cpu (n->pri_ctrl_cap.cntlid)); + +return nvme_c2h (n, (uint8_t *)&n->pri_ctrl_cap, +sizeof (NvmePriCtrlCap), req); +} +static uint16_t nvme_identify_ns_csi (NvmeCtrl *n,NvmeRequest *req,bool active) {
@@ -5018,6 +5026,8 @@ static uint16_t nvme_identify(NvmeCtrl *n, NvmeRequest *req)return nvme_identify_ctrl_list (n, req, true);case NVME_ID_CNS_CTRL_LIST :return nvme_identify_ctrl_list (n, req, false); +case NVME_ID_CNS_PRIMARY_CTRL_CAP : +return nvme_identify_pri_ctrl_cap (n, req);case NVME_ID_CNS_CS_NS :return nvme_identify_ns_csi (n, req, true);case NVME_ID_CNS_CS_NS_PRESENT :
@@ -6609,6 +6619,8 @@ static void nvme_check_constraints(NvmeCtrl *n, Error **errp)static void nvme_init_state (NvmeCtrl *n) { +NvmePriCtrlCap *cap = &n->pri_ctrl_cap; +/* add one to max_ioqpairs to account for the admin queue pair */ n->reg_size =pow2ceil (sizeof (NvmeBar) +2 * (n->params.max_ioqpairs +1 ) *NVME_DB_SIZE );
@@ -6618,6 +6630,8 @@ static void nvme_init_state(NvmeCtrl *n) n->features.temp_thresh_hi =NVME_TEMPERATURE_WARNING ; n->starttime_ms =qemu_clock_get_ms (QEMU_CLOCK_VIRTUAL ); n->aer_reqs = g_new0(NvmeRequest *, n->params.aerl + 1); + + cap->cntlid =cpu_to_le16 (n->cntlid); }static void nvme_init_cmb (NvmeCtrl *n,PCIDevice *pci_dev)
@@ -6919,15 +6933,14 @@ static void nvme_realize(PCIDevice *pci_dev, Error **errp)qbus_init (&n->bus,sizeof (NvmeBus),TYPE_NVME_BUS , &pci_dev->qdev, n->parent_obj.qdev.id); -nvme_init_state (n); -if (nvme_init_pci (n, pci_dev, errp)) { -return ; - } -if (nvme_init_subsys (n, errp)) {error_propagate (errp, local_err);return ; } +nvme_init_state (n); +if (nvme_init_pci (n, pci_dev, errp)) { +return ; + }nvme_init_ctrl (n, pci_dev);/* setup a namespace if the controller drive property was given */
hw/nvme/nvme.h +2 -0
@@ -477,6 +477,8 @@ typedef struct NvmeCtrl {uint32_t async_config;NvmeHostBehaviorSupport hbs; } features; + +NvmePriCtrlCap pri_ctrl_cap; } NvmeCtrl;static inline NvmeNamespace *nvme_ns (NvmeCtrl *n,uint32_t nsid)
hw/nvme/trace-events +1 -0
@@ -56,6 +56,7 @@ pci_nvme_identify_ctrl(void) "identify controller" pci_nvme_identify_ctrl_csi(uint8_t csi) "identify controller, csi=0x%"PRIx8"" pci_nvme_identify_ns(uint32_t ns) "nsid %"PRIu32"" pci_nvme_identify_ctrl_list(uint8_t cns, uint16_t cntid) "cns 0x%"PRIx8" cntid %"PRIu16"" +pci_nvme_identify_pri_ctrl_cap(uint16_t cntlid) "identify primary controller capabilities cntlid=%"PRIu16"" pci_nvme_identify_ns_csi(uint32_t ns, uint8_t csi) "nsid=%"PRIu32", csi=0x%"PRIx8"" pci_nvme_identify_nslist(uint32_t ns) "nsid %"PRIu32"" pci_nvme_identify_nslist_csi(uint16_t ns, uint8_t csi) "nsid=%"PRIu16", csi=0x%"PRIx8""
include/block/nvme.h +23 -0
@@ -1033,6 +1033,7 @@ enum NvmeIdCns {NVME_ID_CNS_NS_PRESENT =0x11 ,NVME_ID_CNS_NS_ATTACHED_CTRL_LIST =0x12 ,NVME_ID_CNS_CTRL_LIST =0x13 , +NVME_ID_CNS_PRIMARY_CTRL_CAP =0x14 ,NVME_ID_CNS_CS_NS_PRESENT_LIST =0x1a ,NVME_ID_CNS_CS_NS_PRESENT =0x1b , NVME_ID_CNS_IO_COMMAND_SET = 0x1c,
@@ -1553,6 +1554,27 @@ typedef enum NvmeZoneState {NVME_ZONE_STATE_OFFLINE =0x0f , } NvmeZoneState; +typedef struct QEMU_PACKED NvmePriCtrlCap { +uint16_t cntlid; +uint16_t portid; +uint8_t crt; +uint8_t rsvd5[27 ]; +uint32_t vqfrt; +uint32_t vqrfa; +uint16_t vqrfap; +uint16_t vqprt; +uint16_t vqfrsm; +uint16_t vqgran; +uint8_t rsvd48[16 ]; +uint32_t vifrt; +uint32_t virfa; +uint16_t virfap; +uint16_t viprt; +uint16_t vifrsm; +uint16_t vigran; +uint8_t rsvd80[4016 ]; +} NvmePriCtrlCap; +static inline void _nvme_check_size (void ) {QEMU_BUILD_BUG_ON (sizeof (NvmeBar) !=4096 );
@@ -1588,5 +1610,6 @@ static inline void _nvme_check_size(void)QEMU_BUILD_BUG_ON (sizeof (NvmeIdNsDescr) !=4 );QEMU_BUILD_BUG_ON (sizeof (NvmeZoneDescr) !=64 );QEMU_BUILD_BUG_ON (sizeof (NvmeDifTuple) !=16 ); + QEMU_BUILD_BUG_ON(sizeof(NvmePriCtrlCap) != 4096); }#endif
Signature · 1 line
2.25.1
PATCH v7 3/12 hw/nvme: Add support for Secondary Controller List
In reply to Lukasz ManiakIntroduce handling for Secondary Controller List (Identify command with CNS value of 15h).
Secondary controller ids are unique in the subsystem, hence they are reserved by it upon initialization of the primary controller to the number of sriov_max_vfs.
ID reservation requires the addition of an intermediate controller slot state, so the reserved controller has the address 0xFFFF.
A secondary controller is in the reserved state when it has no virtual function assigned, but its primary controller is realized. Secondary controller reservations are released to NULL when its primary controller is unregistered.
--- hw/nvme/ctrl.c | 35 +++++++++++++++++++++ hw/nvme/ns.c | 2 +- hw/nvme/nvme.h | 18 +++++++++++ hw/nvme/subsys.c | 75 ++++++++++++++++++++++++++++++++++++++------ hw/nvme/trace-events | 1 + include/block/nvme.h | 20 ++++++++++++ 6 files changed, 141 insertions(+), 10 deletions(-)
hw/nvme/ctrl.c +35 -0
@@ -4807,6 +4807,29 @@ static uint16_t nvme_identify_pri_ctrl_cap(NvmeCtrl *n, NvmeRequest *req) sizeof(NvmePriCtrlCap), req); } +static uint16_t nvme_identify_sec_ctrl_list (NvmeCtrl *n,NvmeRequest *req) +{ +NvmeIdentify *c = (NvmeIdentify *)&req->cmd; +uint16_t pri_ctrl_id =le16_to_cpu (n->pri_ctrl_cap.cntlid); +uint16_t min_id =le16_to_cpu (c->ctrlid); +uint8_t num_sec_ctrl = n->sec_ctrl_list.numcntl; +NvmeSecCtrlList list = {0 }; +uint8_t i; + +for (i =0 ; i < num_sec_ctrl; i++) { +if (n->sec_ctrl_list.sec[i].scid >= min_id) { + list.numcntl = num_sec_ctrl - i; +memcpy (&list.sec, n->sec_ctrl_list.sec + i, + list.numcntl *sizeof (NvmeSecCtrlEntry)); +break ; + } + } + +trace_pci_nvme_identify_sec_ctrl_list (pri_ctrl_id, list.numcntl); + +return nvme_c2h (n, (uint8_t *)&list,sizeof (list), req); +} +static uint16_t nvme_identify_ns_csi (NvmeCtrl *n,NvmeRequest *req,bool active) {
@@ -5028,6 +5051,8 @@ static uint16_t nvme_identify(NvmeCtrl *n, NvmeRequest *req)return nvme_identify_ctrl_list (n, req, false);case NVME_ID_CNS_PRIMARY_CTRL_CAP :return nvme_identify_pri_ctrl_cap (n, req); +case NVME_ID_CNS_SECONDARY_CTRL_LIST : +return nvme_identify_sec_ctrl_list (n, req);case NVME_ID_CNS_CS_NS :return nvme_identify_ns_csi (n, req, true);case NVME_ID_CNS_CS_NS_PRESENT :
@@ -6620,6 +6645,9 @@ static void nvme_check_constraints(NvmeCtrl *n, Error **errp)static void nvme_init_state (NvmeCtrl *n) {NvmePriCtrlCap *cap = &n->pri_ctrl_cap; +NvmeSecCtrlList *list = &n->sec_ctrl_list; +NvmeSecCtrlEntry *sctrl; +int i;/* add one to max_ioqpairs to account for the admin queue pair */ n->reg_size = pow2ceil(sizeof(NvmeBar) +
@@ -6631,6 +6659,13 @@ static void nvme_init_state(NvmeCtrl *n) n->starttime_ms =qemu_clock_get_ms (QEMU_CLOCK_VIRTUAL ); n->aer_reqs = g_new0(NvmeRequest *, n->params.aerl + 1); + list->numcntl =cpu_to_le16 (n->params.sriov_max_vfs); +for (i =0 ; i < n->params.sriov_max_vfs; i++) { + sctrl = &list->sec[i]; + sctrl->pcid =cpu_to_le16 (n->cntlid); + sctrl->vfn =cpu_to_le16 (i +1 ); + } + cap->cntlid =cpu_to_le16 (n->cntlid); }
hw/nvme/ns.c +1 -1
@@ -596,7 +596,7 @@ static void nvme_ns_realize(DeviceState *dev, Error **errp)for (i =0 ; i <ARRAY_SIZE (subsys->ctrls); i++) {NvmeCtrl *ctrl = subsys->ctrls[i]; -if (ctrl) { +if (ctrl && ctrl !=SUBSYS_SLOT_RSVD ) {nvme_attach_ns (ctrl, ns); } }
hw/nvme/nvme.h +18 -0
@@ -43,6 +43,7 @@ typedef struct NvmeBus {#define TYPE_NVME_SUBSYS "nvme-subsys"#define NVME_SUBSYS (obj) \ OBJECT_CHECK(NvmeSubsystem, (obj), TYPE_NVME_SUBSYS) +#define SUBSYS_SLOT_RSVD (void *)0xFFFF typedef struct NvmeSubsystem { DeviceState parent_obj;
@@ -67,6 +68,10 @@ static inline NvmeCtrl *nvme_subsys_ctrl(NvmeSubsystem *subsys,return NULL ; } +if (subsys->ctrls[cntlid] ==SUBSYS_SLOT_RSVD ) { +return NULL ; + } +return subsys->ctrls[cntlid]; }
@@ -479,6 +484,7 @@ typedef struct NvmeCtrl { } features;NvmePriCtrlCap pri_ctrl_cap; +NvmeSecCtrlList sec_ctrl_list; } NvmeCtrl;static inline NvmeNamespace *nvme_ns (NvmeCtrl *n,uint32_t nsid)
@@ -513,6 +519,18 @@ static inline uint16_t nvme_cid(NvmeRequest *req)return le16_to_cpu (req->cqe.cid); } +static inline NvmeSecCtrlEntry *nvme_sctrl (NvmeCtrl *n) +{ +PCIDevice *pci_dev = &n->parent_obj; +NvmeCtrl *pf =NVME (pcie_sriov_get_pf (pci_dev)); + +if (pci_is_vf (pci_dev)) { +return &pf->sec_ctrl_list.sec[pcie_sriov_vf_number (pci_dev)]; + } + +return NULL ; +} +void nvme_attach_ns (NvmeCtrl *n,NvmeNamespace *ns);uint16_t nvme_bounce_data (NvmeCtrl *n,void *ptr,uint32_t len,NvmeTxDirection dir,NvmeRequest *req);
hw/nvme/subsys.c +66 -9
93 lines not on this page · raw message
hw/nvme/trace-events +1 -0
@@ -57,6 +57,7 @@ pci_nvme_identify_ctrl_csi(uint8_t csi) "identify controller, csi=0x%"PRIx8"" pci_nvme_identify_ns(uint32_t ns) "nsid %"PRIu32"" pci_nvme_identify_ctrl_list(uint8_t cns, uint16_t cntid) "cns 0x%"PRIx8" cntid %"PRIu16"" pci_nvme_identify_pri_ctrl_cap(uint16_t cntlid) "identify primary controller capabilities cntlid=%"PRIu16"" +pci_nvme_identify_sec_ctrl_list(uint16_t cntlid, uint8_t numcntl) "identify secondary controller list cntlid=%"PRIu16" numcntl=%"PRIu8"" pci_nvme_identify_ns_csi(uint32_t ns, uint8_t csi) "nsid=%"PRIu32", csi=0x%"PRIx8"" pci_nvme_identify_nslist(uint32_t ns) "nsid %"PRIu32"" pci_nvme_identify_nslist_csi(uint16_t ns, uint8_t csi) "nsid=%"PRIu16", csi=0x%"PRIx8""
include/block/nvme.h +20 -0
@@ -1034,6 +1034,7 @@ enum NvmeIdCns {NVME_ID_CNS_NS_ATTACHED_CTRL_LIST =0x12 ,NVME_ID_CNS_CTRL_LIST =0x13 ,NVME_ID_CNS_PRIMARY_CTRL_CAP =0x14 , +NVME_ID_CNS_SECONDARY_CTRL_LIST =0x15 ,NVME_ID_CNS_CS_NS_PRESENT_LIST =0x1a ,NVME_ID_CNS_CS_NS_PRESENT =0x1b , NVME_ID_CNS_IO_COMMAND_SET = 0x1c,
@@ -1575,6 +1576,23 @@ typedef struct QEMU_PACKED NvmePriCtrlCap {uint8_t rsvd80[4016 ]; } NvmePriCtrlCap; +typedef struct QEMU_PACKED NvmeSecCtrlEntry { +uint16_t scid; +uint16_t pcid; +uint8_t scs; +uint8_t rsvd5[3 ]; +uint16_t vfn; +uint16_t nvq; +uint16_t nvi; +uint8_t rsvd14[18 ]; +} NvmeSecCtrlEntry; + +typedef struct QEMU_PACKED NvmeSecCtrlList { +uint8_t numcntl; +uint8_t rsvd1[31 ]; +NvmeSecCtrlEntry sec[127 ]; +} NvmeSecCtrlList; +static inline void _nvme_check_size (void ) {QEMU_BUILD_BUG_ON (sizeof (NvmeBar) !=4096 );
@@ -1611,5 +1629,7 @@ static inline void _nvme_check_size(void)QEMU_BUILD_BUG_ON (sizeof (NvmeZoneDescr) !=64 );QEMU_BUILD_BUG_ON (sizeof (NvmeDifTuple) !=16 );QEMU_BUILD_BUG_ON (sizeof (NvmePriCtrlCap) !=4096 ); +QEMU_BUILD_BUG_ON (sizeof (NvmeSecCtrlEntry) !=32 ); + QEMU_BUILD_BUG_ON(sizeof(NvmeSecCtrlList) != 4096); }#endif
Signature · 1 line
2.25.1
PATCH v7 4/12 hw/nvme: Implement the Function Level Reset
In reply to Lukasz ManiakFrom: Łukasz Gieryk <[email protected]>
This patch implements the Function Level Reset, a feature currently not implemented for the Nvme device, while listed as a mandatory ("shall") in the 1.4 spec.
The implementation reuses FLR-related building blocks defined for the pci-bridge module, and follows the same logic:
- FLR capability is advertised in the PCIE config,
- custom pci_write_config callback detects a write to the trigger register and performs the PCI reset,
- which, eventually, calls the custom dc->reset handler.
Depending on reset type, parts of the state should (or should not) be cleared. To distinguish the type of reset, an additional parameter is passed to the reset function.
This patch also enables advertisement of the Power Management PCI capability. The main reason behind it is to announce the no_soft_reset=1 bit, to signal SR-IOV support where each VF can be reset individually.
The implementation purposedly ignores writes to the PMCS.PS register, as even such naïve behavior is enough to correctly handle the D3->D0 transition.
It’s worth to note, that the power state transition back to to D3, with all the corresponding side effects, wasn't and stil isn't handled properly.
--- hw/nvme/ctrl.c | 52 ++++++++++++++++++++++++++++++++++++++++---- hw/nvme/nvme.h | 5 +++++ hw/nvme/trace-events | 1 + 3 files changed, 54 insertions(+), 4 deletions(-)
hw/nvme/ctrl.c +48 -4
@@ -5901,7 +5901,7 @@ static void nvme_process_sq(void *opaque) } } -static void nvme_ctrl_reset (NvmeCtrl *n) +static void nvme_ctrl_reset (NvmeCtrl *n,NvmeResetType rst) {NvmeNamespace *ns;int i;
@@ -5933,7 +5933,9 @@ static void nvme_ctrl_reset(NvmeCtrl *n) }if (!pci_is_vf (&n->parent_obj) && n->params.sriov_max_vfs) { -pcie_sriov_pf_disable_vfs (&n->parent_obj); +if (rst !=NVME_RESET_CONTROLLER ) { +pcie_sriov_pf_disable_vfs (&n->parent_obj); + } } n->aer_queued =0 ;
@@ -6167,7 +6169,7 @@ static void nvme_write_bar(NvmeCtrl *n, hwaddr offset, uint64_t data, } }else if (!NVME_CC_EN (data) &&NVME_CC_EN (cc)) {trace_pci_nvme_mmio_stopped (); -nvme_ctrl_reset (n); +nvme_ctrl_reset (n,NVME_RESET_CONTROLLER ); cc =0 ; csts &= ~NVME_CSTS_READY ; }
@@ -6725,6 +6727,28 @@ static void nvme_init_sriov(NvmeCtrl *n, PCIDevice *pci_dev, uint16_t offset, PCI_BASE_ADDRESS_MEM_TYPE_64, bar_size); } +static int nvme_add_pm_capability (PCIDevice *pci_dev,uint8_t offset) +{ +Error *err =NULL ; +int ret; + + ret =pci_add_capability (pci_dev,PCI_CAP_ID_PM , offset, +PCI_PM_SIZEOF , &err); +if (err) { +error_report_err (err); +return ret; + } + +pci_set_word (pci_dev->config + offset +PCI_PM_PMC , +PCI_PM_CAP_VER_1_2 ); +pci_set_word (pci_dev->config + offset +PCI_PM_CTRL , +PCI_PM_CTRL_NO_SOFT_RESET ); +pci_set_word (pci_dev->wmask + offset +PCI_PM_CTRL , +PCI_PM_CTRL_STATE_MASK ); + +return 0 ; +} +static int nvme_init_pci (NvmeCtrl *n,PCIDevice *pci_dev,Error **errp) {uint8_t *pci_conf = pci_dev->config;
@@ -6746,7 +6770,9 @@ static int nvme_init_pci(NvmeCtrl *n, PCIDevice *pci_dev, Error **errp) }pci_config_set_class (pci_conf,PCI_CLASS_STORAGE_EXPRESS ); +nvme_add_pm_capability (pci_dev,0x60 );pcie_endpoint_cap_init (pci_dev,0x80 ); +pcie_cap_flr_init (pci_dev);if (n->params.sriov_max_vfs) {pcie_ari_init (pci_dev,0x100 ,1 ); }
@@ -6997,7 +7023,7 @@ static void nvme_exit(PCIDevice *pci_dev)NvmeNamespace *ns;int i; -nvme_ctrl_reset (n); +nvme_ctrl_reset (n,NVME_RESET_FUNCTION );if (n->subsys) {for (i =1 ; i <=NVME_MAX_NAMESPACES ; i++) {
@@ -7096,6 +7122,22 @@ static void nvme_set_smart_warning(Object *obj, Visitor *v, const char *name, } } +static void nvme_pci_reset (DeviceState *qdev) +{ +PCIDevice *pci_dev =PCI_DEVICE (qdev); +NvmeCtrl *n =NVME (pci_dev); + +trace_pci_nvme_pci_reset (); +nvme_ctrl_reset (n,NVME_RESET_FUNCTION ); +} + +static void nvme_pci_write_config (PCIDevice *dev,uint32_t address, +uint32_t val,int len) +{ +pci_default_write_config (dev, address, val, len); +pcie_cap_flr_write_config (dev, address, val, len); +} +static const VMStateDescription nvme_vmstate = { .name ="nvme" , .unmigratable =1 ,
@@ -7107,6 +7149,7 @@ static void nvme_class_init(ObjectClass *oc, void *data)PCIDeviceClass *pc =PCI_DEVICE_CLASS (oc); pc->realize = nvme_realize; + pc->config_write = nvme_pci_write_config; pc->exit = nvme_exit; pc->class_id =PCI_CLASS_STORAGE_EXPRESS ; pc->revision =2 ;
@@ -7115,6 +7158,7 @@ static void nvme_class_init(ObjectClass *oc, void *data) dc->desc ="Non-Volatile Memory Express" ;device_class_set_props (dc, nvme_props); dc->vmsd = &nvme_vmstate; + dc->reset = nvme_pci_reset; }static void nvme_instance_init (Object *obj)
hw/nvme/nvme.h +5 -0
@@ -487,6 +487,11 @@ typedef struct NvmeCtrl {NvmeSecCtrlList sec_ctrl_list; } NvmeCtrl; +typedef enum NvmeResetType { +NVME_RESET_FUNCTION =0 , +NVME_RESET_CONTROLLER =1 , +}NvmeResetType ; +static inline NvmeNamespace *nvme_ns (NvmeCtrl *n,uint32_t nsid) {if (!nsid || nsid >NVME_MAX_NAMESPACES ) {
hw/nvme/trace-events +1 -0
@@ -110,6 +110,7 @@ pci_nvme_zd_extension_set(uint32_t zone_idx) "set descriptor extension for zone_ pci_nvme_clear_ns_close(uint32_t state, uint64_t slba) "zone state=%"PRIu32", slba=%"PRIu64" transitioned to Closed state" pci_nvme_clear_ns_reset(uint32_t state, uint64_t slba) "zone state=%"PRIu32", slba=%"PRIu64" transitioned to Empty state" pci_nvme_zoned_zrwa_implicit_flush(uint64_t zslba, uint32_t nlb) "zslba 0x%"PRIx64" nlb %"PRIu32"" +pci_nvme_pci_reset(void) "PCI Function Level Reset" # error conditions pci_nvme_err_mdts(size_t len) "len %zu"
Signature · 1 line
2.25.1
PATCH v7 5/12 hw/nvme: Make max_ioqpairs and msix_qsize configurable in runtime
In reply to Lukasz ManiakFrom: Łukasz Gieryk <[email protected]>
The NVMe device defines two properties: max_ioqpairs, msix_qsize. Having them as constants is problematic for SR-IOV support.
SR-IOV introduces virtual resources (queues, interrupts) that can be assigned to PF and its dependent VFs. Each device, following a reset, should work with the configured number of queues. A single constant is no longer sufficient to hold the whole state.
This patch tries to solve the problem by introducing additional variables in NvmeCtrl’s state. The variables for, e.g., managing queues are therefore organized as:
- n->params.max_ioqpairs – no changes, constant set by the user
- n->(mutable_state) – (not a part of this patch) user-configurable, specifies number of queues available _after_ reset
- n->conf_ioqpairs - (new) used in all the places instead of the ‘old’ n->params.max_ioqpairs; initialized in realize() and updated during reset() to reflect user’s changes to the mutable state
Since the number of available i/o queues and interrupts can change in runtime, buffers for sq/cqs and the MSIX-related structures are allocated big enough to handle the limits, to completely avoid the complicated reallocation. A helper function (nvme_update_msixcap_ts) updates the corresponding capability register, to signal configuration changes.
--- hw/nvme/ctrl.c | 52 ++++++++++++++++++++++++++++++++++---------------- hw/nvme/nvme.h | 2 ++ 2 files changed, 38 insertions(+), 16 deletions(-)
hw/nvme/ctrl.c +36 -16
@@ -448,12 +448,12 @@ static bool nvme_nsid_valid(NvmeCtrl *n, uint32_t nsid)static int nvme_check_sqid (NvmeCtrl *n,uint16_t sqid) { -return sqid < n->params.max_ioqpairs +1 && n->sq[sqid] !=NULL ?0 :-1 ; +return sqid < n->conf_ioqpairs +1 && n->sq[sqid] !=NULL ?0 :-1 ; }static int nvme_check_cqid (NvmeCtrl *n,uint16_t cqid) { -return cqid < n->params.max_ioqpairs +1 && n->cq[cqid] !=NULL ?0 :-1 ; +return cqid < n->conf_ioqpairs +1 && n->cq[cqid] !=NULL ?0 :-1 ; }static void nvme_inc_cq_tail (NvmeCQueue *cq)
@@ -4290,8 +4290,7 @@ static uint16_t nvme_create_sq(NvmeCtrl *n, NvmeRequest *req)trace_pci_nvme_err_invalid_create_sq_cqid (cqid);return NVME_INVALID_CQID |NVME_DNR ; } -if (unlikely (!sqid || sqid > n->params.max_ioqpairs || - n->sq[sqid] !=NULL )) { +if (unlikely (!sqid || sqid > n->conf_ioqpairs || n->sq[sqid] !=NULL )) {trace_pci_nvme_err_invalid_create_sq_sqid (sqid);return NVME_INVALID_QID |NVME_DNR ; }
@@ -4643,8 +4642,7 @@ static uint16_t nvme_create_cq(NvmeCtrl *n, NvmeRequest *req)trace_pci_nvme_create_cq (prp1, cqid, vector, qsize, qflags,NVME_CQ_FLAGS_IEN (qflags) !=0 ); -if (unlikely (!cqid || cqid > n->params.max_ioqpairs || - n->cq[cqid] !=NULL )) { +if (unlikely (!cqid || cqid > n->conf_ioqpairs || n->cq[cqid] !=NULL )) {trace_pci_nvme_err_invalid_create_cq_cqid (cqid);return NVME_INVALID_QID |NVME_DNR ; }
@@ -4660,7 +4658,7 @@ static uint16_t nvme_create_cq(NvmeCtrl *n, NvmeRequest *req)trace_pci_nvme_err_invalid_create_cq_vector (vector);return NVME_INVALID_IRQ_VECTOR |NVME_DNR ; } -if (unlikely (vector >= n->params.msix_qsize)) { +if (unlikely (vector >= n->conf_msix_qsize)) {trace_pci_nvme_err_invalid_create_cq_vector (vector);return NVME_INVALID_IRQ_VECTOR |NVME_DNR ; }
@@ -5261,13 +5259,12 @@ defaults:break ;case NVME_NUMBER_OF_QUEUES : - result = (n->params.max_ioqpairs -1 ) | - ((n->params.max_ioqpairs -1 ) <<16 ); + result = (n->conf_ioqpairs -1 ) | ((n->conf_ioqpairs -1 ) <<16 );trace_pci_nvme_getfeat_numq (result);break ;case NVME_INTERRUPT_VECTOR_CONF : iv = dw11 &0xffff ; -if (iv >= n->params.max_ioqpairs +1 ) { +if (iv >= n->conf_ioqpairs +1 ) {return NVME_INVALID_FIELD |NVME_DNR ; }
@@ -5423,10 +5420,10 @@ static uint16_t nvme_set_feature(NvmeCtrl *n, NvmeRequest *req)trace_pci_nvme_setfeat_numq ((dw11 &0xffff ) +1 , ((dw11 >>16 ) &0xffff ) +1 , - n->params.max_ioqpairs, - n->params.max_ioqpairs); - req->cqe.result =cpu_to_le32 ((n->params.max_ioqpairs -1 ) | - ((n->params.max_ioqpairs -1 ) <<16 )); + n->conf_ioqpairs, + n->conf_ioqpairs); + req->cqe.result =cpu_to_le32 ((n->conf_ioqpairs -1 ) | + ((n->conf_ioqpairs -1 ) <<16 ));break ;case NVME_ASYNCHRONOUS_EVENT_CONF : n->features.async_config = dw11;
@@ -5901,8 +5898,24 @@ static void nvme_process_sq(void *opaque) } } +static void nvme_update_msixcap_ts (PCIDevice *pci_dev,uint32_t table_size) +{ +uint8_t *config; + +if (!msix_present (pci_dev)) { +return ; + } + +assert (table_size >0 && table_size <= pci_dev->msix_entries_nr); + + config = pci_dev->config + pci_dev->msix_cap; +pci_set_word_by_mask (config +PCI_MSIX_FLAGS ,PCI_MSIX_FLAGS_QSIZE , + table_size -1 ); +} +static void nvme_ctrl_reset (NvmeCtrl *n,NvmeResetType rst) { +PCIDevice *pci_dev = &n->parent_obj;NvmeNamespace *ns;int i;
@@ -5932,15 +5945,17 @@ static void nvme_ctrl_reset(NvmeCtrl *n, NvmeResetType rst)g_free (event); } -if (!pci_is_vf (&n->parent_obj) && n->params.sriov_max_vfs) { +if (!pci_is_vf (pci_dev) && n->params.sriov_max_vfs) {if (rst !=NVME_RESET_CONTROLLER ) { -pcie_sriov_pf_disable_vfs (&n->parent_obj); +pcie_sriov_pf_disable_vfs (pci_dev); } } n->aer_queued =0 ; n->outstanding_aers =0 ; n->qs_created = false; + +nvme_update_msixcap_ts (pci_dev, n->conf_msix_qsize); }static void nvme_ctrl_shutdown (NvmeCtrl *n)
@@ -6651,6 +6666,9 @@ static void nvme_init_state(NvmeCtrl *n)NvmeSecCtrlEntry *sctrl;int i; + n->conf_ioqpairs = n->params.max_ioqpairs; + n->conf_msix_qsize = n->params.msix_qsize; +/* add one to max_ioqpairs to account for the admin queue pair */ n->reg_size =pow2ceil (sizeof (NvmeBar) +2 * (n->params.max_ioqpairs +1 ) *NVME_DB_SIZE );
@@ -6812,6 +6830,8 @@ static int nvme_init_pci(NvmeCtrl *n, PCIDevice *pci_dev, Error **errp) } } +nvme_update_msixcap_ts (pci_dev, n->conf_msix_qsize); +if (n->params.cmb_size_mb) {nvme_init_cmb (n, pci_dev); }
hw/nvme/nvme.h +2 -0
@@ -438,6 +438,8 @@ typedef struct NvmeCtrl {uint64_t starttime_ms;uint16_t temperature;uint8_t smart_critical_warning; +uint32_t conf_msix_qsize; +uint32_t conf_ioqpairs;struct {MemoryRegion mem;
Signature · 1 line
2.25.1
PATCH v7 6/12 hw/nvme: Remove reg_size variable and update BAR0 size calculation
In reply to Lukasz ManiakFrom: Łukasz Gieryk <[email protected]>
The n->reg_size parameter unnecessarily splits the BAR0 size calculation in two phases; removed to simplify the code.
With all the calculations done in one place, it seems the pow2ceil, applied originally to reg_size, is unnecessary. The rounding should happen as the last step, when BAR size includes Nvme registers, queue registers, and MSIX-related space.
Finally, the size of the mmio memory region is extended to cover the 1st 4KiB padding (see the map below). Access to this range is handled as interaction with a non-existing queue and generates an error trace, so actually nothing changes, while the reg_size variable is no longer needed.
--------------------
| BAR0 |
--------------------
[Nvme Registers ]
[Queues ]
[power-of-2 padding] - removed in this patch
[4KiB padding (1) ]
[MSIX TABLE ]
[4KiB padding (2) ]
[MSIX PBA ]
[power-of-2 padding]
--- hw/nvme/ctrl.c | 10 +++++----- hw/nvme/nvme.h | 1 - 2 files changed, 5 insertions(+), 6 deletions(-)
hw/nvme/ctrl.c +5 -5
@@ -6669,9 +6669,6 @@ static void nvme_init_state(NvmeCtrl *n) n->conf_ioqpairs = n->params.max_ioqpairs; n->conf_msix_qsize = n->params.msix_qsize; -/* add one to max_ioqpairs to account for the admin queue pair */ - n->reg_size =pow2ceil (sizeof (NvmeBar) + -2 * (n->params.max_ioqpairs +1 ) *NVME_DB_SIZE ); n->sq = g_new0(NvmeSQueue *, n->params.max_ioqpairs + 1); n->cq = g_new0(NvmeCQueue *, n->params.max_ioqpairs + 1); n->temperature =NVME_TEMPERATURE ;
@@ -6795,7 +6792,10 @@ static int nvme_init_pci(NvmeCtrl *n, PCIDevice *pci_dev, Error **errp)pcie_ari_init (pci_dev,0x100 ,1 ); } - bar_size =QEMU_ALIGN_UP (n->reg_size,4 * KiB); +/* add one to max_ioqpairs to account for the admin queue pair */ + bar_size =sizeof (NvmeBar) + +2 * (n->params.max_ioqpairs +1 ) *NVME_DB_SIZE ; + bar_size =QEMU_ALIGN_UP (bar_size,4 * KiB); msix_table_offset = bar_size; msix_table_size =PCI_MSIX_ENTRY_SIZE * n->params.msix_qsize;
@@ -6809,7 +6809,7 @@ static int nvme_init_pci(NvmeCtrl *n, PCIDevice *pci_dev, Error **errp)memory_region_init (&n->bar0,OBJECT (n),"nvme-bar0" , bar_size);memory_region_init_io (&n->iomem,OBJECT (n), &nvme_mmio_ops, n,"nvme" , - n->reg_size); + msix_table_offset);memory_region_add_subregion (&n->bar0,0 , &n->iomem);if (pci_is_vf (pci_dev)) {
hw/nvme/nvme.h +0 -1
@@ -428,7 +428,6 @@ typedef struct NvmeCtrl {uint16_t max_prp_ents;uint16_t cqe_size;uint16_t sqe_size; -uint32_t reg_size;uint32_t max_q_ents;uint8_t outstanding_aers;uint32_t irq_status;
Signature · 1 line
2.25.1
PATCH v7 7/12 hw/nvme: Calculate BAR attributes in a function
In reply to Lukasz ManiakFrom: Łukasz Gieryk <[email protected]>
An NVMe device with SR-IOV capability calculates the BAR size differently for PF and VF, so it makes sense to extract the common code to a separate function.
--- hw/nvme/ctrl.c | 45 +++++++++++++++++++++++++++++++-------------- 1 file changed, 31 insertions(+), 14 deletions(-)
hw/nvme/ctrl.c +31 -14
@@ -6728,6 +6728,34 @@ static void nvme_init_pmr(NvmeCtrl *n, PCIDevice *pci_dev)memory_region_set_enabled (&n->pmr.dev->mr, false); } +static uint64_t nvme_bar_size (unsigned total_queues,unsigned total_irqs, +unsigned *msix_table_offset, +unsigned *msix_pba_offset) +{ +uint64_t bar_size, msix_table_size, msix_pba_size; + + bar_size =sizeof (NvmeBar) +2 * total_queues *NVME_DB_SIZE ; + bar_size =QEMU_ALIGN_UP (bar_size,4 * KiB); + +if (msix_table_offset) { + *msix_table_offset = bar_size; + } + + msix_table_size =PCI_MSIX_ENTRY_SIZE * total_irqs; + bar_size += msix_table_size; + bar_size =QEMU_ALIGN_UP (bar_size,4 * KiB); + +if (msix_pba_offset) { + *msix_pba_offset = bar_size; + } + + msix_pba_size =QEMU_ALIGN_UP (total_irqs,64 ) /8 ; + bar_size += msix_pba_size; + + bar_size =pow2ceil (bar_size); +return bar_size; +} +static void nvme_init_sriov (NvmeCtrl *n,PCIDevice *pci_dev,uint16_t offset,uint64_t bar_size) {
@@ -6767,7 +6795,7 @@ static int nvme_add_pm_capability(PCIDevice *pci_dev, uint8_t offset)static int nvme_init_pci (NvmeCtrl *n,PCIDevice *pci_dev,Error **errp) {uint8_t *pci_conf = pci_dev->config; -uint64_t bar_size, msix_table_size, msix_pba_size; +uint64_t bar_size;unsigned msix_table_offset, msix_pba_offset;int ret;
@@ -6793,19 +6821,8 @@ static int nvme_init_pci(NvmeCtrl *n, PCIDevice *pci_dev, Error **errp) }/* add one to max_ioqpairs to account for the admin queue pair */ - bar_size =sizeof (NvmeBar) + -2 * (n->params.max_ioqpairs +1 ) *NVME_DB_SIZE ; - bar_size =QEMU_ALIGN_UP (bar_size,4 * KiB); - msix_table_offset = bar_size; - msix_table_size =PCI_MSIX_ENTRY_SIZE * n->params.msix_qsize; - - bar_size += msix_table_size; - bar_size =QEMU_ALIGN_UP (bar_size,4 * KiB); - msix_pba_offset = bar_size; - msix_pba_size =QEMU_ALIGN_UP (n->params.msix_qsize,64 ) /8 ; - - bar_size += msix_pba_size; - bar_size =pow2ceil (bar_size); + bar_size =nvme_bar_size (n->params.max_ioqpairs +1 , n->params.msix_qsize, + &msix_table_offset, &msix_pba_offset);memory_region_init (&n->bar0,OBJECT (n),"nvme-bar0" , bar_size); memory_region_init_io(&n->iomem, OBJECT(n), &nvme_mmio_ops, n, "nvme",
Signature · 1 line
2.25.1
PATCH v7 8/12 hw/nvme: Initialize capability structures for primary/secondary controllers
In reply to Lukasz ManiakFrom: Łukasz Gieryk <[email protected]>
With four new properties:
- sriov_v{i,q}_flexible,
- sriov_max_v{i,q}_per_vf,
one can configure the number of available flexible resources, as well as the limits. The primary and secondary controller capability structures are initialized accordingly.
Since the number of available queues (interrupts) now varies between VF/PF, BAR size calculation is also adjusted.
--- hw/nvme/ctrl.c | 141 ++++++++++++++++++++++++++++++++++++++++--- hw/nvme/nvme.h | 4 ++ include/block/nvme.h | 5 ++ 3 files changed, 143 insertions(+), 7 deletions(-)
hw/nvme/ctrl.c +134 -7
@@ -36,6 +36,10 @@* zoned.zasl=<N[optional]>, \ * zoned.auto_transition=<on|off[optional]>, \ * sriov_max_vfs=<N[optional]> \ +* sriov_vq_flexible=<N[optional]> \ +* sriov_vi_flexible=<N[optional]> \ +* sriov_max_vi_per_vf=<N[optional]> \ +* sriov_max_vq_per_vf=<N[optional]> \ * subsys=<subsys_id> * -device nvme-ns,drive=<drive_id>,bus=<bus_name>,nsid=<nsid>,\ * zoned=<true|false[optional]>, \
@@ -113,6 +117,29 @@* enables reporting of both SR-IOV and ARI capabilities by the NVMe device. * Virtual function controllers will not report SR-IOV capability. * +* NOTE: Single Root I/O Virtualization support is experimental. +* All the related parameters may be subject to change. +* +* - `sriov_vq_flexible` +* Indicates the total number of flexible queue resources assignable to all +* the secondary controllers. Implicitly sets the number of primary +* controller's private resources to `(max_ioqpairs - sriov_vq_flexible)`. +* +* - `sriov_vi_flexible` +* Indicates the total number of flexible interrupt resources assignable to +* all the secondary controllers. Implicitly sets the number of primary +* controller's private resources to `(msix_qsize - sriov_vi_flexible)`. +* +* - `sriov_max_vi_per_vf` +* Indicates the maximum number of virtual interrupt resources assignable +* to a secondary controller. The default 0 resolves to +* `(sriov_vi_flexible / sriov_max_vfs)`. +* +* - `sriov_max_vq_per_vf` +* Indicates the maximum number of virtual queue resources assignable to +* a secondary controller. The default 0 resolves to +* `(sriov_vq_flexible / sriov_max_vfs)`. +* * nvme namespace device parameters * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * - `shared`
@@ -185,6 +212,7 @@#define NVME_NUM_FW_SLOTS 1#define NVME_DEFAULT_MAX_ZA_SIZE (128 * KiB)#define NVME_MAX_VFS 127 +#define NVME_VF_RES_GRANULARITY 1#define NVME_VF_OFFSET 0x1#define NVME_VF_STRIDE 1
@@ -6656,6 +6684,53 @@ static void nvme_check_constraints(NvmeCtrl *n, Error **errp)error_setg (errp,"PMR is not supported with SR-IOV" );return ; } + +if (!params->sriov_vq_flexible || !params->sriov_vi_flexible) { +error_setg (errp,"both sriov_vq_flexible and sriov_vi_flexible" +" must be set for the use of SR-IOV" ); +return ; + } + +if (params->sriov_vq_flexible < params->sriov_max_vfs *2 ) { +error_setg (errp,"sriov_vq_flexible must be greater than or equal" +" to %d (sriov_max_vfs * 2)" , params->sriov_max_vfs *2 ); +return ; + } + +if (params->max_ioqpairs < params->sriov_vq_flexible +2 ) { +error_setg (errp,"(max_ioqpairs - sriov_vq_flexible) must be" +" greater than or equal to 2" ); +return ; + } + +if (params->sriov_vi_flexible < params->sriov_max_vfs) { +error_setg (errp,"sriov_vi_flexible must be greater than or equal" +" to %d (sriov_max_vfs)" , params->sriov_max_vfs); +return ; + } + +if (params->msix_qsize < params->sriov_vi_flexible +1 ) { +error_setg (errp,"(msix_qsize - sriov_vi_flexible) must be" +" greater than or equal to 1" ); +return ; + } + +if (params->sriov_max_vi_per_vf && + (params->sriov_max_vi_per_vf -1 ) %NVME_VF_RES_GRANULARITY ) { +error_setg (errp,"sriov_max_vi_per_vf must meet:" +" (sriov_max_vi_per_vf - 1) %% %d == 0 and" +" sriov_max_vi_per_vf >= 1" ,NVME_VF_RES_GRANULARITY ); +return ; + } + +if (params->sriov_max_vq_per_vf && + (params->sriov_max_vq_per_vf <2 || + (params->sriov_max_vq_per_vf -1 ) %NVME_VF_RES_GRANULARITY )) { +error_setg (errp,"sriov_max_vq_per_vf must meet:" +" (sriov_max_vq_per_vf - 1) %% %d == 0 and" +" sriov_max_vq_per_vf >= 2" ,NVME_VF_RES_GRANULARITY ); +return ; + } } }
@@ -6664,10 +6739,19 @@ static void nvme_init_state(NvmeCtrl *n)NvmePriCtrlCap *cap = &n->pri_ctrl_cap;NvmeSecCtrlList *list = &n->sec_ctrl_list;NvmeSecCtrlEntry *sctrl; +uint8_t max_vfs;int i; - n->conf_ioqpairs = n->params.max_ioqpairs; - n->conf_msix_qsize = n->params.msix_qsize; +if (pci_is_vf (&n->parent_obj)) { + sctrl =nvme_sctrl (n); + max_vfs =0 ; + n->conf_ioqpairs = sctrl->nvq ?le16_to_cpu (sctrl->nvq) -1 :0 ; + n->conf_msix_qsize = sctrl->nvi ?le16_to_cpu (sctrl->nvi) :1 ; + }else { + max_vfs = n->params.sriov_max_vfs; + n->conf_ioqpairs = n->params.max_ioqpairs; + n->conf_msix_qsize = n->params.msix_qsize; + } n->sq = g_new0(NvmeSQueue *, n->params.max_ioqpairs + 1); n->cq = g_new0(NvmeCQueue *, n->params.max_ioqpairs + 1);
@@ -6676,14 +6760,41 @@ static void nvme_init_state(NvmeCtrl *n) n->starttime_ms =qemu_clock_get_ms (QEMU_CLOCK_VIRTUAL ); n->aer_reqs = g_new0(NvmeRequest *, n->params.aerl + 1); - list->numcntl =cpu_to_le16 (n->params.sriov_max_vfs); -for (i =0 ; i < n->params.sriov_max_vfs; i++) { + list->numcntl =cpu_to_le16 (max_vfs); +for (i =0 ; i < max_vfs; i++) { sctrl = &list->sec[i]; sctrl->pcid =cpu_to_le16 (n->cntlid); sctrl->vfn =cpu_to_le16 (i +1 ); } cap->cntlid =cpu_to_le16 (n->cntlid); + cap->crt =NVME_CRT_VQ |NVME_CRT_VI ; + +if (pci_is_vf (&n->parent_obj)) { + cap->vqprt =cpu_to_le16 (1 + n->conf_ioqpairs); + }else { + cap->vqprt =cpu_to_le16 (1 + n->params.max_ioqpairs - + n->params.sriov_vq_flexible); + cap->vqfrt =cpu_to_le32 (n->params.sriov_vq_flexible); + cap->vqrfap = cap->vqfrt; + cap->vqgran =cpu_to_le16 (NVME_VF_RES_GRANULARITY ); + cap->vqfrsm = n->params.sriov_max_vq_per_vf ? +cpu_to_le16 (n->params.sriov_max_vq_per_vf) : + cap->vqfrt /MAX (max_vfs,1 ); + } + +if (pci_is_vf (&n->parent_obj)) { + cap->viprt =cpu_to_le16 (n->conf_msix_qsize); + }else { + cap->viprt =cpu_to_le16 (n->params.msix_qsize - + n->params.sriov_vi_flexible); + cap->vifrt =cpu_to_le32 (n->params.sriov_vi_flexible); + cap->virfap = cap->vifrt; + cap->vigran =cpu_to_le16 (NVME_VF_RES_GRANULARITY ); + cap->vifrsm = n->params.sriov_max_vi_per_vf ? +cpu_to_le16 (n->params.sriov_max_vi_per_vf) : + cap->vifrt /MAX (max_vfs,1 ); + } }static void nvme_init_cmb (NvmeCtrl *n,PCIDevice *pci_dev)
@@ -6756,11 +6867,14 @@ static uint64_t nvme_bar_size(unsigned total_queues, unsigned total_irqs,return bar_size; } -static void nvme_init_sriov (NvmeCtrl *n,PCIDevice *pci_dev,uint16_t offset, -uint64_t bar_size) +static void nvme_init_sriov (NvmeCtrl *n,PCIDevice *pci_dev,uint16_t offset) {uint16_t vf_dev_id = n->params.use_intel_id ?PCI_DEVICE_ID_INTEL_NVME :PCI_DEVICE_ID_REDHAT_NVME ; +NvmePriCtrlCap *cap = &n->pri_ctrl_cap; +uint64_t bar_size =nvme_bar_size (le16_to_cpu (cap->vqfrsm), +le16_to_cpu (cap->vifrsm), +NULL ,NULL ); pcie_sriov_pf_init(pci_dev, offset, "nvme", vf_dev_id, n->params.sriov_max_vfs, n->params.sriov_max_vfs,
@@ -6858,7 +6972,7 @@ static int nvme_init_pci(NvmeCtrl *n, PCIDevice *pci_dev, Error **errp) }if (!pci_is_vf (pci_dev) && n->params.sriov_max_vfs) { -nvme_init_sriov (n, pci_dev,0x120 , bar_size); +nvme_init_sriov (n, pci_dev,0x120 ); }return 0 ;
@@ -6882,6 +6996,7 @@ static void nvme_init_ctrl(NvmeCtrl *n, PCIDevice *pci_dev)NvmeIdCtrl *id = &n->id_ctrl;uint8_t *pci_conf = pci_dev->config;uint64_t cap =ldq_le_p (&n->bar.cap); +NvmeSecCtrlEntry *sctrl =nvme_sctrl (n); id->vid =cpu_to_le16 (pci_get_word (pci_conf +PCI_VENDOR_ID )); id->ssvid =cpu_to_le16 (pci_get_word (pci_conf +PCI_SUBSYSTEM_VENDOR_ID ));
@@ -6974,6 +7089,10 @@ static void nvme_init_ctrl(NvmeCtrl *n, PCIDevice *pci_dev)stl_le_p (&n->bar.vs,NVME_SPEC_VER ); n->bar.intmc = n->bar.intms =0 ; + +if (pci_is_vf (&n->parent_obj) && !sctrl->scs) { +stl_le_p (&n->bar.csts,NVME_CSTS_FAILED ); + } }static int nvme_init_subsys (NvmeCtrl *n,Error **errp)
@@ -7114,6 +7233,14 @@ static Property nvme_props[] = {DEFINE_PROP_BOOL ("zoned.auto_transition" , NvmeCtrl, params.auto_transition_zones, true),DEFINE_PROP_UINT8 ("sriov_max_vfs" , NvmeCtrl, params.sriov_max_vfs,0 ), +DEFINE_PROP_UINT16 ("sriov_vq_flexible" , NvmeCtrl, + params.sriov_vq_flexible,0 ), +DEFINE_PROP_UINT16 ("sriov_vi_flexible" , NvmeCtrl, + params.sriov_vi_flexible,0 ), +DEFINE_PROP_UINT8 ("sriov_max_vi_per_vf" , NvmeCtrl, + params.sriov_max_vi_per_vf,0 ), +DEFINE_PROP_UINT8 ("sriov_max_vq_per_vf" , NvmeCtrl, + params.sriov_max_vq_per_vf,0 ), DEFINE_PROP_END_OF_LIST(), };
hw/nvme/nvme.h +4 -0
@@ -411,6 +411,10 @@ typedef struct NvmeParams {bool auto_transition_zones;bool legacy_cmb;uint8_t sriov_max_vfs; +uint16_t sriov_vq_flexible; +uint16_t sriov_vi_flexible; +uint8_t sriov_max_vq_per_vf; +uint8_t sriov_max_vi_per_vf; } NvmeParams; typedef struct NvmeCtrl {
include/block/nvme.h +5 -0
@@ -1576,6 +1576,11 @@ typedef struct QEMU_PACKED NvmePriCtrlCap {uint8_t rsvd80[4016 ]; } NvmePriCtrlCap; +typedef enum NvmePriCtrlCapCrt { +NVME_CRT_VQ =1 <<0 , +NVME_CRT_VI =1 <<1 , +}NvmePriCtrlCapCrt ; + typedef struct QEMU_PACKED NvmeSecCtrlEntry {uint16_t scid;uint16_t pcid;
Signature · 1 line
2.25.1
PATCH v7 9/12 hw/nvme: Add support for the Virtualization Management command
In reply to Lukasz ManiakFrom: Łukasz Gieryk <[email protected]>
With the new command one can:
- assign flexible resources (queues, interrupts) to primary and secondary controllers,
- toggle the online/offline state of given controller.
--- hw/nvme/ctrl.c | 257 ++++++++++++++++++++++++++++++++++++++++++- hw/nvme/nvme.h | 20 ++++ hw/nvme/trace-events | 3 + include/block/nvme.h | 17 +++ 4 files changed, 295 insertions(+), 2 deletions(-)
hw/nvme/ctrl.c +255 -2
@@ -188,6 +188,7 @@#include "qemu/error-report.h" #include "qemu/log.h" #include "qemu/units.h" +#include "qemu/range.h" #include "qapi/error.h" #include "qapi/visitor.h" #include "sysemu/sysemu.h"
@@ -262,6 +263,7 @@ static const uint32_t nvme_cse_acs[256] = { [NVME_ADM_CMD_GET_FEATURES] = NVME_CMD_EFF_CSUPP, [NVME_ADM_CMD_ASYNC_EV_REQ] = NVME_CMD_EFF_CSUPP, [NVME_ADM_CMD_NS_ATTACHMENT] = NVME_CMD_EFF_CSUPP | NVME_CMD_EFF_NIC, + [NVME_ADM_CMD_VIRT_MNGMT] = NVME_CMD_EFF_CSUPP, [NVME_ADM_CMD_FORMAT_NVM] = NVME_CMD_EFF_CSUPP | NVME_CMD_EFF_LBCC, };
@@ -293,6 +295,7 @@ static const uint32_t nvme_cse_iocs_zoned[256] = { };static void nvme_process_sq (void *opaque); +static void nvme_ctrl_reset (NvmeCtrl *n,NvmeResetType rst);static uint16_t nvme_sqid (NvmeRequest *req) {
@@ -5838,6 +5841,167 @@ out:return status; } +static void nvme_get_virt_res_num (NvmeCtrl *n,uint8_t rt,int *num_total, +int *num_prim,int *num_sec) +{ + *num_total =le32_to_cpu (rt ? + n->pri_ctrl_cap.vifrt : n->pri_ctrl_cap.vqfrt); + *num_prim =le16_to_cpu (rt ? + n->pri_ctrl_cap.virfap : n->pri_ctrl_cap.vqrfap); + *num_sec =le16_to_cpu (rt ? n->pri_ctrl_cap.virfa : n->pri_ctrl_cap.vqrfa); +} + +static uint16_t nvme_assign_virt_res_to_prim (NvmeCtrl *n,NvmeRequest *req, +uint16_t cntlid,uint8_t rt, +int nr) +{ +int num_total, num_prim, num_sec; + +if (cntlid != n->cntlid) { +return NVME_INVALID_CTRL_ID |NVME_DNR ; + } + +nvme_get_virt_res_num (n, rt, &num_total, &num_prim, &num_sec); + +if (nr > num_total) { +return NVME_INVALID_NUM_RESOURCES |NVME_DNR ; + } + +if (nr > num_total - num_sec) { +return NVME_INVALID_RESOURCE_ID |NVME_DNR ; + } + +if (rt) { + n->next_pri_ctrl_cap.virfap =cpu_to_le16 (nr); + }else { + n->next_pri_ctrl_cap.vqrfap =cpu_to_le16 (nr); + } + + req->cqe.result =cpu_to_le32 (nr); +return req->status; +} + +static void nvme_update_virt_res (NvmeCtrl *n,NvmeSecCtrlEntry *sctrl, +uint8_t rt,int nr) +{ +int prev_nr, prev_total; + +if (rt) { + prev_nr =le16_to_cpu (sctrl->nvi); + prev_total =le32_to_cpu (n->pri_ctrl_cap.virfa); + sctrl->nvi =cpu_to_le16 (nr); + n->pri_ctrl_cap.virfa =cpu_to_le32 (prev_total + nr - prev_nr); + }else { + prev_nr =le16_to_cpu (sctrl->nvq); + prev_total =le32_to_cpu (n->pri_ctrl_cap.vqrfa); + sctrl->nvq =cpu_to_le16 (nr); + n->pri_ctrl_cap.vqrfa =cpu_to_le32 (prev_total + nr - prev_nr); + } +} + +static uint16_t nvme_assign_virt_res_to_sec (NvmeCtrl *n,NvmeRequest *req, +uint16_t cntlid,uint8_t rt,int nr) +{ +int num_total, num_prim, num_sec, num_free, diff, limit; +NvmeSecCtrlEntry *sctrl; + + sctrl =nvme_sctrl_for_cntlid (n, cntlid); +if (!sctrl) { +return NVME_INVALID_CTRL_ID |NVME_DNR ; + } + +if (sctrl->scs) { +return NVME_INVALID_SEC_CTRL_STATE |NVME_DNR ; + } + + limit =le16_to_cpu (rt ? n->pri_ctrl_cap.vifrsm : n->pri_ctrl_cap.vqfrsm); +if (nr > limit) { +return NVME_INVALID_NUM_RESOURCES |NVME_DNR ; + } + +nvme_get_virt_res_num (n, rt, &num_total, &num_prim, &num_sec); + num_free = num_total - num_prim - num_sec; + diff = nr -le16_to_cpu (rt ? sctrl->nvi : sctrl->nvq); + +if (diff > num_free) { +return NVME_INVALID_RESOURCE_ID |NVME_DNR ; + } + +nvme_update_virt_res (n, sctrl, rt, nr); + req->cqe.result =cpu_to_le32 (nr); + +return req->status; +} + +static uint16_t nvme_virt_set_state (NvmeCtrl *n,uint16_t cntlid,bool online) +{ +NvmeCtrl *sn =NULL ; +NvmeSecCtrlEntry *sctrl; +int vf_index; + + sctrl =nvme_sctrl_for_cntlid (n, cntlid); +if (!sctrl) { +return NVME_INVALID_CTRL_ID |NVME_DNR ; + } + +if (!pci_is_vf (&n->parent_obj)) { + vf_index =le16_to_cpu (sctrl->vfn) -1 ; + sn =NVME (pcie_sriov_get_vf_at_index (&n->parent_obj, vf_index)); + } + +if (online) { +if (!sctrl->nvi || (le16_to_cpu (sctrl->nvq) <2 ) || !sn) { +return NVME_INVALID_SEC_CTRL_STATE |NVME_DNR ; + } + +if (!sctrl->scs) { + sctrl->scs =0x1 ; +nvme_ctrl_reset (sn,NVME_RESET_FUNCTION ); + } + }else { +nvme_update_virt_res (n, sctrl,NVME_VIRT_RES_INTERRUPT ,0 ); +nvme_update_virt_res (n, sctrl,NVME_VIRT_RES_QUEUE ,0 ); + +if (sctrl->scs) { + sctrl->scs =0x0 ; +if (sn) { +nvme_ctrl_reset (sn,NVME_RESET_FUNCTION ); + } + } + } + +return NVME_SUCCESS ; +} + +static uint16_t nvme_virt_mngmt (NvmeCtrl *n,NvmeRequest *req) +{ +uint32_t dw10 =le32_to_cpu (req->cmd.cdw10); +uint32_t dw11 =le32_to_cpu (req->cmd.cdw11); +uint8_t act = dw10 &0xf ; +uint8_t rt = (dw10 >>8 ) &0x7 ; +uint16_t cntlid = (dw10 >>16 ) &0xffff ; +int nr = dw11 &0xffff ; + +trace_pci_nvme_virt_mngmt (nvme_cid (req), act, cntlid, rt ?"VI" :"VQ" , nr); + +if (rt !=NVME_VIRT_RES_QUEUE && rt !=NVME_VIRT_RES_INTERRUPT ) { +return NVME_INVALID_RESOURCE_ID |NVME_DNR ; + } + +switch (act) { +case NVME_VIRT_MNGMT_ACTION_SEC_ASSIGN : +return nvme_assign_virt_res_to_sec (n, req, cntlid, rt, nr); +case NVME_VIRT_MNGMT_ACTION_PRM_ALLOC : +return nvme_assign_virt_res_to_prim (n, req, cntlid, rt, nr); +case NVME_VIRT_MNGMT_ACTION_SEC_ONLINE : +return nvme_virt_set_state (n, cntlid, true); +case NVME_VIRT_MNGMT_ACTION_SEC_OFFLINE : +return nvme_virt_set_state (n, cntlid, false); +default : +return NVME_INVALID_FIELD |NVME_DNR ; + } +} +static uint16_t nvme_admin_cmd (NvmeCtrl *n,NvmeRequest *req) { trace_pci_nvme_admin_cmd(nvme_cid(req), nvme_sqid(req), req->cmd.opcode,
@@ -5880,6 +6044,8 @@ static uint16_t nvme_admin_cmd(NvmeCtrl *n, NvmeRequest *req)return nvme_aer (n, req);case NVME_ADM_CMD_NS_ATTACHMENT :return nvme_ns_attachment (n, req); +case NVME_ADM_CMD_VIRT_MNGMT : +return nvme_virt_mngmt (n, req);case NVME_ADM_CMD_FORMAT_NVM :return nvme_format (n, req);default :
@@ -5941,9 +6107,33 @@ static void nvme_update_msixcap_ts(PCIDevice *pci_dev, uint32_t table_size) table_size - 1); } +static void nvme_activate_virt_res (NvmeCtrl *n) +{ +PCIDevice *pci_dev = &n->parent_obj; +NvmePriCtrlCap *cap = &n->pri_ctrl_cap; +NvmeSecCtrlEntry *sctrl; + +/* -1 to account for the admin queue */ +if (pci_is_vf (pci_dev)) { + sctrl =nvme_sctrl (n); + cap->vqprt = sctrl->nvq; + cap->viprt = sctrl->nvi; + n->conf_ioqpairs = sctrl->nvq ?le16_to_cpu (sctrl->nvq) -1 :0 ; + n->conf_msix_qsize = sctrl->nvi ?le16_to_cpu (sctrl->nvi) :1 ; + }else { + cap->vqrfap = n->next_pri_ctrl_cap.vqrfap; + cap->virfap = n->next_pri_ctrl_cap.virfap; + n->conf_ioqpairs =le16_to_cpu (cap->vqprt) + +le16_to_cpu (cap->vqrfap) -1 ; + n->conf_msix_qsize =le16_to_cpu (cap->viprt) + +le16_to_cpu (cap->virfap); + } +} +static void nvme_ctrl_reset (NvmeCtrl *n,NvmeResetType rst) {PCIDevice *pci_dev = &n->parent_obj; +NvmeSecCtrlEntry *sctrl;NvmeNamespace *ns;int i;
@@ -5973,9 +6163,20 @@ static void nvme_ctrl_reset(NvmeCtrl *n, NvmeResetType rst)g_free (event); } -if (!pci_is_vf (pci_dev) && n->params.sriov_max_vfs) { +if (n->params.sriov_max_vfs) { +if (!pci_is_vf (pci_dev)) { +for (i =0 ; i < n->sec_ctrl_list.numcntl; i++) { + sctrl = &n->sec_ctrl_list.sec[i]; +nvme_virt_set_state (n,le16_to_cpu (sctrl->scid), false); + } + +if (rst !=NVME_RESET_CONTROLLER ) { +pcie_sriov_pf_disable_vfs (pci_dev); + } + } +if (rst !=NVME_RESET_CONTROLLER ) { -pcie_sriov_pf_disable_vfs (pci_dev); +nvme_activate_virt_res (n); } }
@@ -5984,6 +6185,13 @@ static void nvme_ctrl_reset(NvmeCtrl *n, NvmeResetType rst) n->qs_created = false;nvme_update_msixcap_ts (pci_dev, n->conf_msix_qsize); + +if (pci_is_vf (pci_dev)) { + sctrl =nvme_sctrl (n); +stl_le_p (&n->bar.csts, sctrl->scs ?0 :NVME_CSTS_FAILED ); + }else { +stl_le_p (&n->bar.csts,0 ); + } }static void nvme_ctrl_shutdown (NvmeCtrl *n)
@@ -6029,7 +6237,15 @@ static int nvme_start_ctrl(NvmeCtrl *n)uint64_t acq =ldq_le_p (&n->bar.acq);uint32_t page_bits =NVME_CC_MPS (cc) +12 ;uint32_t page_size =1 << page_bits; +NvmeSecCtrlEntry *sctrl =nvme_sctrl (n); +if (pci_is_vf (&n->parent_obj) && !sctrl->scs) { +trace_pci_nvme_err_startfail_virt_state (le16_to_cpu (sctrl->nvi), +le16_to_cpu (sctrl->nvq), + sctrl->scs ?"ONLINE" : +"OFFLINE" ); +return -1 ; + }if (unlikely (n->cq[0 ])) {trace_pci_nvme_err_startfail_cq ();return -1 ;
@@ -6412,6 +6628,12 @@ static uint64_t nvme_mmio_read(void *opaque, hwaddr addr, unsigned size)return 0 ; } +if (pci_is_vf (&n->parent_obj) && !nvme_sctrl (n)->scs && + addr !=NVME_REG_CSTS ) { +trace_pci_nvme_err_ignored_mmio_vf_offline (addr, size); +return 0 ; + } +/* * When PMRWBM bit 1 is set then read from * from PMRSTS should ensure prior writes
@@ -6561,6 +6783,12 @@ static void nvme_mmio_write(void *opaque, hwaddr addr, uint64_t data,trace_pci_nvme_mmio_write (addr, data, size); +if (pci_is_vf (&n->parent_obj) && !nvme_sctrl (n)->scs && + addr !=NVME_REG_CSTS ) { +trace_pci_nvme_err_ignored_mmio_vf_offline (addr, size); +return ; + } +if (addr <sizeof (n->bar)) {nvme_write_bar (n, addr, data, size); }else {
@@ -7295,9 +7523,34 @@ static void nvme_pci_reset(DeviceState *qdev)nvme_ctrl_reset (n,NVME_RESET_FUNCTION ); } +static void nvme_sriov_pre_write_ctrl (PCIDevice *dev,uint32_t address, +uint32_t val,int len) +{ +NvmeCtrl *n =NVME (dev); +NvmeSecCtrlEntry *sctrl; +uint16_t sriov_cap = dev->exp.sriov_cap; +uint32_t off = address - sriov_cap; +int i, num_vfs; + +if (!sriov_cap) { +return ; + } + +if (range_covers_byte (off, len,PCI_SRIOV_CTRL )) { +if (!(val &PCI_SRIOV_CTRL_VFE )) { + num_vfs =pci_get_word (dev->config + sriov_cap +PCI_SRIOV_NUM_VF ); +for (i =0 ; i < num_vfs; i++) { + sctrl = &n->sec_ctrl_list.sec[i]; +nvme_virt_set_state (n,le16_to_cpu (sctrl->scid), false); + } + } + } +} +static void nvme_pci_write_config (PCIDevice *dev,uint32_t address,uint32_t val,int len) { +nvme_sriov_pre_write_ctrl (dev, address, val, len);pci_default_write_config (dev, address, val, len);pcie_cap_flr_write_config (dev, address, val, len); }
hw/nvme/nvme.h +20 -0
@@ -339,6 +339,7 @@ static inline const char *nvme_adm_opc_str(uint8_t opc)case NVME_ADM_CMD_GET_FEATURES :return "NVME_ADM_CMD_GET_FEATURES" ;case NVME_ADM_CMD_ASYNC_EV_REQ :return "NVME_ADM_CMD_ASYNC_EV_REQ" ;case NVME_ADM_CMD_NS_ATTACHMENT :return "NVME_ADM_CMD_NS_ATTACHMENT" ; +case NVME_ADM_CMD_VIRT_MNGMT :return "NVME_ADM_CMD_VIRT_MNGMT" ;case NVME_ADM_CMD_FORMAT_NVM :return "NVME_ADM_CMD_FORMAT_NVM" ;default :return "NVME_ADM_CMD_UNKNOWN" ; }
@@ -490,6 +491,10 @@ typedef struct NvmeCtrl {NvmePriCtrlCap pri_ctrl_cap;NvmeSecCtrlList sec_ctrl_list; +struct { +uint16_t vqrfap; +uint16_t virfap; + } next_pri_ctrl_cap;/* These override pri_ctrl_cap after reset */ } NvmeCtrl; typedef enum NvmeResetType {
@@ -541,6 +546,21 @@ static inline NvmeSecCtrlEntry *nvme_sctrl(NvmeCtrl *n)return NULL ; } +static inline NvmeSecCtrlEntry *nvme_sctrl_for_cntlid (NvmeCtrl *n, +uint16_t cntlid) +{ +NvmeSecCtrlList *list = &n->sec_ctrl_list; +uint8_t i; + +for (i =0 ; i < list->numcntl; i++) { +if (le16_to_cpu (list->sec[i].scid) == cntlid) { +return &list->sec[i]; + } + } + +return NULL ; +} +void nvme_attach_ns (NvmeCtrl *n,NvmeNamespace *ns);uint16_t nvme_bounce_data (NvmeCtrl *n,void *ptr,uint32_t len,NvmeTxDirection dir,NvmeRequest *req);
hw/nvme/trace-events +3 -0
@@ -111,6 +111,7 @@ pci_nvme_clear_ns_close(uint32_t state, uint64_t slba) "zone state=%"PRIu32", sl pci_nvme_clear_ns_reset(uint32_t state, uint64_t slba) "zone state=%"PRIu32", slba=%"PRIu64" transitioned to Empty state" pci_nvme_zoned_zrwa_implicit_flush(uint64_t zslba, uint32_t nlb) "zslba 0x%"PRIx64" nlb %"PRIu32"" pci_nvme_pci_reset(void) "PCI Function Level Reset" +pci_nvme_virt_mngmt(uint16_t cid, uint16_t act, uint16_t cntlid, const char* rt, uint16_t nr) "cid %"PRIu16", act=0x%"PRIx16", ctrlid=%"PRIu16" %s nr=%"PRIu16"" # error conditions pci_nvme_err_mdts(size_t len) "len %zu"
@@ -180,7 +181,9 @@ pci_nvme_err_startfail_asqent_sz_zero(void) "nvme_start_ctrl failed because the pci_nvme_err_startfail_acqent_sz_zero(void) "nvme_start_ctrl failed because the admin completion queue size is zero" pci_nvme_err_startfail_zasl_too_small(uint32_t zasl, uint32_t pagesz) "nvme_start_ctrl failed because zone append size limit %"PRIu32" is too small, needs to be >= %"PRIu32"" pci_nvme_err_startfail(void) "setting controller enable bit failed" +pci_nvme_err_startfail_virt_state(uint16_t vq, uint16_t vi, const char *state) "nvme_start_ctrl failed due to ctrl state: vi=%u vq=%u %s" pci_nvme_err_invalid_mgmt_action(uint8_t action) "action=0x%"PRIx8"" +pci_nvme_err_ignored_mmio_vf_offline(uint64_t addr, unsigned size) "addr 0x%"PRIx64" size %d" # undefined behavior pci_nvme_ub_mmiowr_misaligned32(uint64_t offset) "MMIO write not 32-bit aligned, offset=0x%"PRIx64""
include/block/nvme.h +17 -0
@@ -595,6 +595,7 @@ enum NvmeAdminCommands {NVME_ADM_CMD_ACTIVATE_FW =0x10 ,NVME_ADM_CMD_DOWNLOAD_FW =0x11 ,NVME_ADM_CMD_NS_ATTACHMENT =0x15 , +NVME_ADM_CMD_VIRT_MNGMT =0x1c ,NVME_ADM_CMD_FORMAT_NVM =0x80 ,NVME_ADM_CMD_SECURITY_SEND =0x81 , NVME_ADM_CMD_SECURITY_RECV = 0x82,
@@ -899,6 +900,10 @@ enum NvmeStatusCodes {NVME_NS_PRIVATE =0x0119 ,NVME_NS_NOT_ATTACHED =0x011a ,NVME_NS_CTRL_LIST_INVALID =0x011c , +NVME_INVALID_CTRL_ID =0x011f , +NVME_INVALID_SEC_CTRL_STATE =0x0120 , +NVME_INVALID_NUM_RESOURCES =0x0121 , +NVME_INVALID_RESOURCE_ID =0x0122 ,NVME_CONFLICTING_ATTRS =0x0180 ,NVME_INVALID_PROT_INFO =0x0181 , NVME_WRITE_TO_RO = 0x0182,
@@ -1598,6 +1603,18 @@ typedef struct QEMU_PACKED NvmeSecCtrlList {NvmeSecCtrlEntry sec[127 ]; } NvmeSecCtrlList; +typedef enum NvmeVirtMngmtAction { +NVME_VIRT_MNGMT_ACTION_PRM_ALLOC =0x01 , +NVME_VIRT_MNGMT_ACTION_SEC_OFFLINE =0x07 , +NVME_VIRT_MNGMT_ACTION_SEC_ASSIGN =0x08 , +NVME_VIRT_MNGMT_ACTION_SEC_ONLINE =0x09 , +}NvmeVirtMngmtAction ; + +typedef enum NvmeVirtualResourceType { +NVME_VIRT_RES_QUEUE =0x00 , +NVME_VIRT_RES_INTERRUPT =0x01 , +}NvmeVirtualResourceType ; +static inline void _nvme_check_size (void ) {QEMU_BUILD_BUG_ON (sizeof (NvmeBar) !=4096 );
Signature · 1 line
2.25.1
PATCH v7 10/12 docs: Add documentation for SR-IOV and Virtualization Enhancements
In reply to Lukasz Maniak--- docs/system/devices/nvme.rst | 82 ++++++++++++++++++++++++++++++++++++ 1 file changed, 82 insertions(+)
docs/system/devices/nvme.rst +82 -0
@@ -239,3 +239,85 @@ The virtual namespace device supports DIF- and DIX-based protection information to ``1`` to transfer protection information as the first eight bytes of metadata. Otherwise, the protection information is transferred as the last eight bytes. + +Virtualization Enhancements and SR-IOV (Experimental Support) +------------------------------------------------------------- + +The ``nvme`` device supports Single Root I/O Virtualization and Sharing +along with Virtualization Enhancements. The controller has to be linked to +an NVM Subsystem device (``nvme-subsys``) for use with SR-IOV. + +A number of parameters are present (**please note, that they may be +subject to change**): + +``sriov_max_vfs`` (default: ``0``) + Indicates the maximum number of PCIe virtual functions supported + by the controller. Specifying a non-zero value enables reporting of both + SR-IOV and ARI (Alternative Routing-ID Interpretation) capabilities + by the NVMe device. Virtual function controllers will not report SR-IOV. + +``sriov_vq_flexible`` + Indicates the total number of flexible queue resources assignable to all + the secondary controllers. Implicitly sets the number of primary + controller's private resources to ``(max_ioqpairs - sriov_vq_flexible)``. + +``sriov_vi_flexible`` + Indicates the total number of flexible interrupt resources assignable to + all the secondary controllers. Implicitly sets the number of primary + controller's private resources to ``(msix_qsize - sriov_vi_flexible)``. + +``sriov_max_vi_per_vf`` (default: ``0``) + Indicates the maximum number of virtual interrupt resources assignable + to a secondary controller. The default ``0`` resolves to + ``(sriov_vi_flexible / sriov_max_vfs)`` + +``sriov_max_vq_per_vf`` (default: ``0``) + Indicates the maximum number of virtual queue resources assignable to + a secondary controller. The default ``0`` resolves to + ``(sriov_vq_flexible / sriov_max_vfs)`` + +The simplest possible invocation enables the capability to set up one VF +controller and assign an admin queue, an IO queue, and a MSI-X interrupt. + +.. code-block:: console + + -device nvme-subsys,id=subsys0 + -device nvme,serial=deadbeef,subsys=subsys0,sriov_max_vfs=1, + sriov_vq_flexible=2,sriov_vi_flexible=1 + +The minimum steps required to configure a functional NVMe secondary +controller are: + + * unbind flexible resources from the primary controller + +.. code-block:: console + + nvme virt-mgmt /dev/nvme0 -c 0 -r 1 -a 1 -n 0 + nvme virt-mgmt /dev/nvme0 -c 0 -r 0 -a 1 -n 0 + + * perform a Function Level Reset on the primary controller to actually + release the resources + +.. code-block:: console + + echo 1 > /sys/bus/pci/devices/0000:01:00.0/reset + + * enable VF + +.. code-block:: console + + echo 1 > /sys/bus/pci/devices/0000:01:00.0/sriov_numvfs + + * assign the flexible resources to the VF and set it ONLINE + +.. code-block:: console + + nvme virt-mgmt /dev/nvme0 -c 1 -r 1 -a 8 -n 1 + nvme virt-mgmt /dev/nvme0 -c 1 -r 0 -a 8 -n 2 + nvme virt-mgmt /dev/nvme0 -c 1 -r 0 -a 9 -n 0 + + * bind the NVMe driver to the VF + +.. code-block:: console + + echo 0000:01:00.1 > /sys/bus/pci/drivers/nvme/bind
Signature · 1 line
2.25.1
PATCH v7 11/12 hw/nvme: Update the initalization place for the AER queue
In reply to Lukasz ManiakFrom: Łukasz Gieryk <[email protected]>
This patch updates the initialization place for the AER queue, so it’s initialized once, at controller initialization, and not every time controller is enabled.
While the original version works for a non-SR-IOV device, as it’s hard to interact with the controller if it’s not enabled, the multiple reinitialization is not necessarily correct.
With the SR/IOV feature enabled a segfault can happen: a VF can have its controller disabled, while a namespace can still be attached to the controller through the parent PF. An event generated in such case ends up on an uninitialized queue.
While it’s an interesting question whether a VF should support AER in the first place, I don’t think it must be answered today.
--- hw/nvme/ctrl.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
hw/nvme/ctrl.c +1 -2
@@ -6326,8 +6326,6 @@ static int nvme_start_ctrl(NvmeCtrl *n)nvme_set_timestamp (n,0ULL ); -QTAILQ_INIT (&n->aer_queue); -nvme_select_iocs (n);return 0 ;
@@ -6987,6 +6985,7 @@ static void nvme_init_state(NvmeCtrl *n) n->features.temp_thresh_hi =NVME_TEMPERATURE_WARNING ; n->starttime_ms =qemu_clock_get_ms (QEMU_CLOCK_VIRTUAL ); n->aer_reqs = g_new0(NvmeRequest *, n->params.aerl + 1); +QTAILQ_INIT (&n->aer_queue); list->numcntl =cpu_to_le16 (max_vfs);for (i =0 ; i < max_vfs; i++) {
Signature · 1 line
2.25.1
PATCH v7 12/12 hw/acpi: Make the PCI hot-plug aware of SR-IOV
In reply to Lukasz ManiakFrom: Łukasz Gieryk <[email protected]>
PCI device capable of SR-IOV support is a new, still-experimental feature with only a single working example of the Nvme device.
This patch in an attempt to fix a double-free problem when a SR-IOV-capable Nvme device is hot-unplugged. The problem and the reproduction steps can be found in this thread:
https://patchew.org/QEMU/[email protected]/[email protected]/
Details of the proposed solution are, for convenience, included below.
1) The current SR-IOV implementation assumes it’s the PhysicalFunction that creates and deletes VirtualFunctions.
2) It’s a design decision (the Nvme device at least) for the VFs to be of the same class as PF. Effectively, they share the dc->hotpluggable value.
3) When a VF is created, it’s added as a child node to PF’s PCI bus slot.
4) Monitor/device_del triggers the ACPI mechanism. The implementation is not aware of SR/IOV and ejects PF’s PCI slot, directly unrealizing all hot-pluggable (!acpi_pcihp_pc_no_hotplug) children nodes.
5) VFs are unrealized directly, and it doesn’t work well with (1). SR/IOV structures are not updated, so when it’s PF’s turn to be unrealized, it works on stale pointers to already-deleted VFs.
--- hw/acpi/pcihp.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
hw/acpi/pcihp.c +5 -1
@@ -192,8 +192,12 @@ static bool acpi_pcihp_pc_no_hotplug(AcpiPciHpState *s, PCIDevice *dev)* ACPI doesn't allow hotplug of bridge devices. Don't allow * hot-unplug of bridge devices unless they were added by hotplug * (and so, not described by acpi). +* +* Don't allow hot-unplug of SR-IOV Virtual Functions, as they +* will be removed implicitly, when Physical Function is unplugged. */ -return (pc->is_bridge && !dev->qdev.hotplugged) || !dc->hotpluggable; +return (pc->is_bridge && !dev->qdev.hotplugged) || !dc->hotpluggable || +pci_is_vf (dev); }static void acpi_pcihp_eject_slot (AcpiPciHpState *s,unsigned bsel,unsigned slots)
Signature · 1 line
2.25.1
Re: [PATCH v7 12/12] hw/acpi: Make the PCI hot-plug aware of SR-IOV
Quoted 10 lines · On Fri, 18 Mar 2022 20:18:19 +0100 Lukasz Maniak…
From: Łukasz Gieryk <[email protected]>
PCI device capable of SR-IOV support is a new, still-experimental feature with only a single working example of the Nvme device.
This patch in an attempt to fix a double-free problem when a SR-IOV-capable Nvme device is hot-unplugged. The problem and the reproduction steps can be found in this thread:
https://patchew.org/QEMU/[email protected]/[email protected]/
pls include that in patch description.
Quoted 15 lines
Details of the proposed solution are, for convenience, included below.
1) The current SR-IOV implementation assumes it’s the PhysicalFunction that creates and deletes VirtualFunctions.
2) It’s a design decision (the Nvme device at least) for the VFs to be of the same class as PF. Effectively, they share thedc->hotpluggablevalue.
3) When a VF is created, it’s added as a child node to PF’s PCI bus slot.
4) Monitor/device_del triggers the ACPI mechanism. The implementation is not aware of SR/IOV and ejects PF’s PCI slot, directly unrealizing all hot-pluggable (!acpi_pcihp_pc_no_hotplug) children nodes.
5) VFs are unrealized directly, and it doesn’t work well with (1). SR/IOV structures are not updated, so when it’s PF’s turn to be unrealized, it works on stale pointers to already-deleted VFs.
it's unclear what's bing hotpluged and unplugged, it would be better if you included QEMU CLI and relevan qmp/monito commands to reproduce it.
Quoted 24 lines
Signed-off-by Łukasz Gieryk <[email protected]>--- hw/acpi/pcihp.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)hw/acpi/pcihp.c +5
-1@@ -192,8 +192,12 @@ static bool acpi_pcihp_pc_no_hotplug(AcpiPciHpState *s, PCIDevice *dev)* ACPI doesn't allow hotplug of bridge devices. Don't allow * hot-unplug of bridge devices unless they were added by hotplug * (and so, not described by acpi). +* +* Don't allow hot-unplug of SR-IOV Virtual Functions, as they +* will be removed implicitly, when Physical Function is unplugged. */ -return (pc->is_bridge && !dev->qdev.hotplugged) || !dc->hotpluggable; +return (pc->is_bridge && !dev->qdev.hotplugged) || !dc->hotpluggable || +pci_is_vf (dev); }static void acpi_pcihp_eject_slot (AcpiPciHpState *s,unsigned bsel,unsigned slots)
Re: [PATCH v7 12/12] hw/acpi: Make the PCI hot-plug aware of SR-IOV
Quoted 2 lines · Igor Mammedov
it's unclear what's bing hotpluged and unplugged, it would be better if you included QEMU CLI and relevan qmp/monito commands to reproduce it.
Qemu CLI:
---------
-device pcie-root-port,slot=0,id=rp0
-device nvme-subsys,id=subsys0
-device nvme,id=nvme0,bus=rp0,serial=deadbeef,subsys=subsys0,sriov_max_vfs=1,sriov_vq_flexible=2,sriov_vi_flexible=1
Guest OS:
---------
sudo nvme virt-mgmt /dev/nvme0 -c 0 -r 1 -a 1 -n 0 sudo nvme virt-mgmt /dev/nvme0 -c 0 -r 0 -a 1 -n 0 echo 1 > /sys/bus/pci/devices/0000:01:00.0/reset sleep 1
echo 1 > /sys/bus/pci/devices/0000:01:00.0/sriov_numvfs nvme virt-mgmt /dev/nvme0 -c 1 -r 1 -a 8 -n 1 nvme virt-mgmt /dev/nvme0 -c 1 -r 0 -a 8 -n 2 nvme virt-mgmt /dev/nvme0 -c 1 -r 0 -a 9 -n 0 sleep 2
echo 01:00.1 > /sys/bus/pci/drivers/nvme/bind
Qemu monitor:
-------------device_del nvme0
Re: [PATCH v7 12/12] hw/acpi: Make the PCI hot-plug aware of SR-IOV
Quoted 23 lines · Łukasz Gieryk
Quoted 2 lines · Igor Mammedov
it's unclear what's bing hotpluged and unplugged, it would be better if you included QEMU CLI and relevan qmp/monito commands to reproduce it.
Qemu CLI:
---------(quoted diff) +0
-3-device pcie-root-port,slot=0,id=rp0 -device nvme-subsys,id=subsys0 -device nvme,id=nvme0,bus=rp0,serial=deadbeef,subsys=subsys0,sriov_max_vfs=1,sriov_vq_flexible=2,sriov_vi_flexible=1Guest OS:
---------
sudo nvme virt-mgmt/dev/nvme0-c 0 -r 1 -a 1 -n 0 sudo nvme virt-mgmt/dev/nvme0-c 0 -r 0 -a 1 -n 0 echo 1 > /sys/bus/pci/devices/0000:01:00.0/reset sleep 1
echo 1 > /sys/bus/pci/devices/0000:01:00.0/sriov_numvfs nvme virt-mgmt/dev/nvme0-c 1 -r 1 -a 8 -n 1 nvme virt-mgmt/dev/nvme0-c 1 -r 0 -a 8 -n 2 nvme virt-mgmt/dev/nvme0-c 1 -r 0 -a 9 -n 0 sleep 2
echo 01:00.1 >/sys/bus/pci/drivers/nvme/bind
Quoted 4 lines
Qemu monitor:
-------------device_delnvme0
Hi Igor,
Do you need any more details on this?
Best regards,
Lukasz
Re: [PATCH v7 12/12] hw/acpi: Make the PCI hot-plug aware of SR-IOV
In reply to Lukasz ManiakQuoted 27 lines · Lukasz Maniak
From: Łukasz Gieryk <[email protected]>
PCI device capable of SR-IOV support is a new, still-experimental feature with only a single working example of the Nvme device.
This patch in an attempt to fix a double-free problem when a SR-IOV-capable Nvme device is hot-unplugged. The problem and the reproduction steps can be found in this thread:
https://patchew.org/QEMU/[email protected]/[email protected]/
Details of the proposed solution are, for convenience, included below.
1) The current SR-IOV implementation assumes it’s the PhysicalFunction that creates and deletes VirtualFunctions.
2) It’s a design decision (the Nvme device at least) for the VFs to be of the same class as PF. Effectively, they share thedc->hotpluggablevalue.
3) When a VF is created, it’s added as a child node to PF’s PCI bus slot.
4) Monitor/device_del triggers the ACPI mechanism. The implementation is not aware of SR/IOV and ejects PF’s PCI slot, directly unrealizing all hot-pluggable (!acpi_pcihp_pc_no_hotplug) children nodes.
5) VFs are unrealized directly, and it doesn’t work well with (1). SR/IOV structures are not updated, so when it’s PF’s turn to be unrealized, it works on stale pointers to already-deleted VFs.
Quoted 1 line
Signed-off-by Łukasz Gieryk <[email protected]>
feel free to include when merging the rest of the patchset.
Quoted 24 lines
--- hw/acpi/pcihp.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)hw/acpi/pcihp.c +5
-1@@ -192,8 +192,12 @@ static bool acpi_pcihp_pc_no_hotplug(AcpiPciHpState *s, PCIDevice *dev)* ACPI doesn't allow hotplug of bridge devices. Don't allow * hot-unplug of bridge devices unless they were added by hotplug * (and so, not described by acpi). +* +* Don't allow hot-unplug of SR-IOV Virtual Functions, as they +* will be removed implicitly, when Physical Function is unplugged. */ -return (pc->is_bridge && !dev->qdev.hotplugged) || !dc->hotpluggable; +return (pc->is_bridge && !dev->qdev.hotplugged) || !dc->hotpluggable || +pci_is_vf (dev); }static void acpi_pcihp_eject_slot (AcpiPciHpState *s,unsigned bsel,unsigned slots)Signature · 1 line
2.25.1
Quoted 15 lines · Lukasz Maniak
Resubmitting v6 as v7 since Patchew got lost with my sophisticated CC of all maintainers just for the cover letter.
Changes since v5:
- Fixed PCI hotplug issue related to deleting VF twice
- Corrected error messages for SR-IOV parameters
- Rebased on master, patches for PCI got pulled into the tree
- Added Reviewed-by labelsLukasz Maniak (4):
hw/nvme: Add support for SR-IOV
hw/nvme: Add support for Primary Controller Capabilities hw/nvme: Add support for Secondary Controller List
docs: Add documentation for SR-IOV and Virtualization Enhancements
Quoted 10 lines
Łukasz Gieryk (8):
hw/nvme: Implement the Function Level Reset
hw/nvme: Makemax_ioqpairsandmsix_qsizeconfigurable in runtime hw/nvme: Removereg_sizevariable and update BAR0 size calculation hw/nvme: Calculate BAR attributes in a function hw/nvme: Initialize capability structures for primary/secondary
controllers
hw/nvme: Add support for the Virtualization Management command hw/nvme: Update the initalization place for the AER queue hw/acpi: Make the PCI hot-plug aware of SR-IOV
the right people to review and merge this would be storage/nvme maintainers.
I did take a quick look though.
Quoted 13 lines
docs/system/devices/nvme.rst | 82 +++++ hw/acpi/pcihp.c | 6 +- hw/nvme/ctrl.c | 673 ++++++++++++++++++++++++++++++++--- hw/nvme/ns.c | 2 +- hw/nvme/nvme.h | 55 ++- hw/nvme/subsys.c | 75 +++- hw/nvme/trace-events | 6 + include/block/nvme.h | 65 ++++ include/hw/pci/pci_ids.h | 1 + 9 files changed, 909 insertions(+), 56 deletions(-)Signature · 1 line
2.25.1
Quoted 27 lines · Michael S. Tsirkin
Quoted 15 lines · Lukasz Maniak
Resubmitting v6 as v7 since Patchew got lost with my sophisticated CC of all maintainers just for the cover letter.
Changes since v5:
- Fixed PCI hotplug issue related to deleting VF twice
- Corrected error messages for SR-IOV parameters
- Rebased on master, patches for PCI got pulled into the tree
- Added Reviewed-by labelsLukasz Maniak (4):
hw/nvme: Add support for SR-IOV
hw/nvme: Add support for Primary Controller Capabilities hw/nvme: Add support for Secondary Controller List
docs: Add documentation for SR-IOV and Virtualization EnhancementsQuoted 10 lines
Łukasz Gieryk (8):
hw/nvme: Implement the Function Level Reset
hw/nvme: Makemax_ioqpairsandmsix_qsizeconfigurable in runtime hw/nvme: Removereg_sizevariable and update BAR0 size calculation hw/nvme: Calculate BAR attributes in a function hw/nvme: Initialize capability structures for primary/secondary
controllers
hw/nvme: Add support for the Virtualization Management command hw/nvme: Update the initalization place for the AER queue hw/acpi: Make the PCI hot-plug aware of SR-IOV
Quoted 6 lines
the right people to review and merge this would be storage/nvme maintainers.
I did take a quick look though.
Was waiting for a review on the acpi stuff. Thanks! :)
Quoted 28 lines · Klaus Jensen
Quoted 27 lines · Michael S. Tsirkin
Quoted 25 lines · Lukasz Maniak
Resubmitting v6 as v7 since Patchew got lost with my sophisticated CC of all maintainers just for the cover letter.
Changes since v5:
- Fixed PCI hotplug issue related to deleting VF twice
- Corrected error messages for SR-IOV parameters
- Rebased on master, patches for PCI got pulled into the tree
- Added Reviewed-by labelsLukasz Maniak (4):
hw/nvme: Add support for SR-IOV
hw/nvme: Add support for Primary Controller Capabilities hw/nvme: Add support for Secondary Controller List
docs: Add documentation for SR-IOV and Virtualization EnhancementsŁukasz Gieryk (8):
hw/nvme: Implement the Function Level Reset
hw/nvme: Makemax_ioqpairsandmsix_qsizeconfigurable in runtime hw/nvme: Removereg_sizevariable and update BAR0 size calculation hw/nvme: Calculate BAR attributes in a function hw/nvme: Initialize capability structures for primary/secondary
controllers
hw/nvme: Add support for the Virtualization Management command hw/nvme: Update the initalization place for the AER queue hw/acpi: Make the PCI hot-plug aware of SR-IOV
Quoted 8 lines
Quoted 6 lines
the right people to review and merge this would be storage/nvme maintainers.
I did take a quick look though.Was waiting for a review on the acpi stuff. Thanks! :)
Thank you for checking and acking Michael :)
Klaus, looking through the list of patches, we are still missing reviews for numbers 03, 08 and 09.
Do you want me to update to v8 or wait for a review first?
Thanks,
Lukasz
Quoted 26 lines · Lukasz Maniak
Resubmitting v6 as v7 since Patchew got lost with my sophisticated CC of all maintainers just for the cover letter.
Changes since v5:
- Fixed PCI hotplug issue related to deleting VF twice
- Corrected error messages for SR-IOV parameters
- Rebased on master, patches for PCI got pulled into the tree
- Added Reviewed-by labelsLukasz Maniak (4):
hw/nvme: Add support for SR-IOV
hw/nvme: Add support for Primary Controller Capabilities hw/nvme: Add support for Secondary Controller List
docs: Add documentation for SR-IOV and Virtualization EnhancementsŁukasz Gieryk (8):
hw/nvme: Implement the Function Level Reset
hw/nvme: Makemax_ioqpairsandmsix_qsizeconfigurable in runtime hw/nvme: Removereg_sizevariable and update BAR0 size calculation hw/nvme: Calculate BAR attributes in a function hw/nvme: Initialize capability structures for primary/secondary
controllers
hw/nvme: Add support for the Virtualization Management command hw/nvme: Update the initalization place for the AER queue hw/acpi: Make the PCI hot-plug aware of SR-IOV
Quoted 11 lines
docs/system/devices/nvme.rst | 82 +++++ hw/acpi/pcihp.c | 6 +- hw/nvme/ctrl.c | 673 ++++++++++++++++++++++++++++++++--- hw/nvme/ns.c | 2 +- hw/nvme/nvme.h | 55 ++- hw/nvme/subsys.c | 75 +++- hw/nvme/trace-events | 6 + include/block/nvme.h | 65 ++++ include/hw/pci/pci_ids.h | 1 + 9 files changed, 909 insertions(+), 56 deletions(-)
Series (hw/nvme parts) looks good.