ifcvf/vDPA implement features provisioning
Subsystems (4)
v2 cover ifcvf/vDPA implement features provisioning
This series implements features provisioning for ifcvf. By applying this series, we allow userspace to create a vDPA device with selected (management device supported) feature bits and mask out others.
Examples:
a)The management device supported features:
$ vdpa mgmtdev show pci/0000:01:00.5 pci/0000:01:00.5: supported_classes net max_supported_vqs 9 dev_features MTU MAC MRG_RXBUF CTRL_VQ MQ ANY_LAYOUT VERSION_1 ACCESS_PLATFORM
b)Provision a vDPA device with all supported features:
$ vdpa dev add name vdpa0 mgmtdev pci/0000:01:00.5 $ vdpa/vdpa dev config show vdpa0 vdpa0: mac 00:e8:ca:11:be:05 link up link_announce false max_vq_pairs 4 mtu 1500 negotiated_features MRG_RXBUF CTRL_VQ MQ VERSION_1 ACCESS_PLATFORM
c)Provision a vDPA device with a subset of the supported features:
$ vdpa dev add name vdpa0 mgmtdev pci/0000:01:00.5 device_features 0x300020020 $ vdpa dev config show vdpa0 mac 00:e8:ca:11:be:05 link up link_announce false negotiated_features CTRL_VQ VERSION_1 ACCESS_PLATFORM
Please help review
Thanks
Changes from V1:
split original patch 1 ~ patch 3 to small patches that are less than 100 lines, so they can be applied to stalbe kernel(Jason)
Zhu Lingshan (12):
vDPA/ifcvf: decouple hw features manipulators from the adapter vDPA/ifcvf: decouple config space ops from the adapter vDPA/ifcvf: alloc the mgmt_dev before the adapter vDPA/ifcvf: decouple vq IRQ releasers from the adapter vDPA/ifcvf: decouple config IRQ releaser from the adapter vDPA/ifcvf: decouple vq irq requester from the adapter vDPA/ifcvf: decouple config/dev IRQ requester and vectors allocator
from the adapter
vDPA/ifcvf: ifcvf_request_irq works on ifcvf_hw vDPA/ifcvf: manage ifcvf_hw in the mgmt_dev
vDPA/ifcvf: allocate the adapter in dev_add() vDPA/ifcvf: retire ifcvf_private_to_vf
vDPA/ifcvf: implement features provisioning
drivers/vdpa/ifcvf/ifcvf_base.c | 32 ++----- drivers/vdpa/ifcvf/ifcvf_base.h | 10 +- drivers/vdpa/ifcvf/ifcvf_main.c | 162 +++++++++++++++----------------- 3 files changed, 91 insertions(+), 113 deletions(-)
Signature · 1 line
2.31.1
PATCH v2 1/12 vDPA/ifcvf: decouple hw features manipulators from the adapter
This commit gets rid of ifcvf_adapter in hw features related functions in ifcvf_base. Then these functions are more rubust and de-coupling from the ifcvf_adapter layer. So these functions could be invoded once the device is probed, even before the adapter is allocaed.
--- drivers/vdpa/ifcvf/ifcvf_base.c | 9 ++------- drivers/vdpa/ifcvf/ifcvf_base.h | 1 + drivers/vdpa/ifcvf/ifcvf_main.c | 1 + 3 files changed, 4 insertions(+), 7 deletions(-)
drivers/vdpa/ifcvf/ifcvf_base.c +2 -7
@@ -220,10 +220,8 @@ u64 ifcvf_get_features(struct ifcvf_hw *hw)int ifcvf_verify_min_features (struct ifcvf_hw *hw,u64 features) { -struct ifcvf_adapter *ifcvf =vf_to_adapter (hw); -if (!(features &BIT_ULL (VIRTIO_F_ACCESS_PLATFORM )) && features) { -IFCVF_ERR (ifcvf->pdev,"VIRTIO_F_ACCESS_PLATFORM is not negotiated\n" ); +IFCVF_ERR (hw->pdev,"VIRTIO_F_ACCESS_PLATFORM is not negotiated\n" );return -EINVAL ; }
@@ -301,14 +299,11 @@ static void ifcvf_set_features(struct ifcvf_hw *hw, u64 features)static int ifcvf_config_features (struct ifcvf_hw *hw) { -struct ifcvf_adapter *ifcvf; - - ifcvf =vf_to_adapter (hw);ifcvf_set_features (hw, hw->req_features);ifcvf_add_status (hw,VIRTIO_CONFIG_S_FEATURES_OK );if (!(ifcvf_get_status (hw) &VIRTIO_CONFIG_S_FEATURES_OK )) { -IFCVF_ERR (ifcvf->pdev,"Failed to set FEATURES_OK status\n" ); +IFCVF_ERR (hw->pdev,"Failed to set FEATURES_OK status\n" );return -EIO ; }
drivers/vdpa/ifcvf/ifcvf_base.h +1 -0
@@ -89,6 +89,7 @@ struct ifcvf_hw {u16 nr_vring;/* VIRTIO_PCI_CAP_DEVICE_CFG size */ u32 cap_dev_config_size; +struct pci_dev *pdev; };struct ifcvf_adapter {
drivers/vdpa/ifcvf/ifcvf_main.c +1 -0
@@ -842,6 +842,7 @@ static int ifcvf_probe(struct pci_dev *pdev, const struct pci_device_id *id) vf = &adapter->vf; vf->dev_type =get_dev_type (pdev); vf->base =pcim_iomap_table (pdev); + vf->pdev = pdev; adapter->pdev = pdev; adapter->vdpa.dma_dev = &pdev->dev;
Signature · 1 line
2.31.1
PATCH v2 2/12 vDPA/ifcvf: decouple config space ops from the adapter
In reply to Zhu LingshanThis commit decopules the config space ops from the adapter layer, so these functions can be invoked once the device is probed.
--- drivers/vdpa/ifcvf/ifcvf_base.c | 21 +++++---------------- 1 file changed, 5 insertions(+), 16 deletions(-)
drivers/vdpa/ifcvf/ifcvf_base.c +5 -16
@@ -10,11 +10,6 @@#include "ifcvf_base.h" -struct ifcvf_adapter *vf_to_adapter (struct ifcvf_hw *hw) -{ - return container_of(hw, struct ifcvf_adapter, vf); -} -u16 ifcvf_set_vq_vector (struct ifcvf_hw *hw,u16 qid,int vector) {struct virtio_pci_common_cfg __iomem *cfg = hw->common_cfg;
@@ -37,8 +32,6 @@ u16 ifcvf_set_config_vector(struct ifcvf_hw *hw, int vector)static void __iomem *get_cap_addr (struct ifcvf_hw *hw,struct virtio_pci_cap *cap) { -struct ifcvf_adapter *ifcvf; -struct pci_dev *pdev;u32 length, offset;u8 bar;
@@ -46,17 +39,14 @@ static void __iomem *get_cap_addr(struct ifcvf_hw *hw, offset =le32_to_cpu (cap->offset); bar = cap->bar; - ifcvf=vf_to_adapter (hw); - pdev = ifcvf->pdev; -if (bar >=IFCVF_PCI_MAX_RESOURCE ) { -IFCVF_DBG (pdev, +IFCVF_DBG (hw->pdev,"Invalid bar number %u to get capabilities\n" , bar);return NULL ; } -if (offset + length >pci_resource_len (pdev, bar)) { -IFCVF_DBG (pdev, +if (offset + length >pci_resource_len (hw->pdev, bar)) { +IFCVF_DBG (hw->pdev,"offset(%u) + len(%u) overflows bar%u's capability\n" , offset, length, bar);return NULL ;
@@ -92,6 +82,7 @@ int ifcvf_init_hw(struct ifcvf_hw *hw, struct pci_dev *pdev)IFCVF_ERR (pdev,"Failed to read PCI capability list\n" );return -EIO ; } + hw->pdev = pdev;while (pos) { ret = ifcvf_read_config_range(pdev, (u32 *)&cap,
@@ -230,13 +221,11 @@ int ifcvf_verify_min_features(struct ifcvf_hw *hw, u64 features)u32 ifcvf_get_config_size (struct ifcvf_hw *hw) { -struct ifcvf_adapter *adapter;u32 net_config_size =sizeof (struct virtio_net_config );u32 blk_config_size =sizeof (struct virtio_blk_config );u32 cap_size = hw->cap_dev_config_size;u32 config_size; - adapter =vf_to_adapter (hw);/* If the onboard device config space size is greater than * the size of struct virtio_net/blk_config, only the spec * implementing contents size is returned, this is very
@@ -251,7 +240,7 @@ u32 ifcvf_get_config_size(struct ifcvf_hw *hw)break ;default : config_size =0 ; -IFCVF_ERR (adapter->pdev,"VIRTIO ID %u not supported\n" , hw->dev_type); +IFCVF_ERR (hw->pdev,"VIRTIO ID %u not supported\n" , hw->dev_type); }return config_size;
Signature · 1 line
2.31.1
PATCH v2 3/12 vDPA/ifcvf: alloc the mgmt_dev before the adapter
In reply to Zhu LingshanThis commit reverses the order of allocating the management device and the adapter. So that it would be possible to move the allocation of the adapter to dev_add().
--- drivers/vdpa/ifcvf/ifcvf_main.c | 31 ++++++++++++++----------------- 1 file changed, 14 insertions(+), 17 deletions(-)
drivers/vdpa/ifcvf/ifcvf_main.c +14 -17
@@ -831,22 +831,30 @@ static int ifcvf_probe(struct pci_dev *pdev, const struct pci_device_id *id) }pci_set_master (pdev); + ifcvf_mgmt_dev =kzalloc (sizeof (struct ifcvf_vdpa_mgmt_dev ),GFP_KERNEL ); +if (!ifcvf_mgmt_dev) { +IFCVF_ERR (pdev,"Failed to alloc memory for the vDPA management device\n" ); +return -ENOMEM ; + } adapter = vdpa_alloc_device(struct ifcvf_adapter, vdpa, dev, &ifc_vdpa_ops,1 ,1 ,NULL , false);if (IS_ERR (adapter)) {IFCVF_ERR (pdev,"Failed to allocate vDPA structure" ); -return PTR_ERR (adapter); + ret =PTR_ERR (adapter); + goto err; } + adapter->pdev = pdev; + adapter->vdpa.dma_dev = &pdev->dev; + adapter->vdpa.mdev = &ifcvf_mgmt_dev->mdev; + ifcvf_mgmt_dev->adapter = adapter; + vf = &adapter->vf; vf->dev_type =get_dev_type (pdev); vf->base =pcim_iomap_table (pdev); vf->pdev = pdev; - adapter->pdev = pdev; - adapter->vdpa.dma_dev = &pdev->dev; - ret =ifcvf_init_hw (vf, pdev);if (ret) {IFCVF_ERR (pdev,"Failed to init IFCVF hw\n" );
@@ -859,16 +867,6 @@ static int ifcvf_probe(struct pci_dev *pdev, const struct pci_device_id *id) vf->hw_features =ifcvf_get_hw_features (vf); vf->config_size =ifcvf_get_config_size (vf); - ifcvf_mgmt_dev =kzalloc (sizeof (struct ifcvf_vdpa_mgmt_dev ),GFP_KERNEL ); -if (!ifcvf_mgmt_dev) { -IFCVF_ERR (pdev,"Failed to alloc memory for the vDPA management device\n" ); -return -ENOMEM ; - } - - ifcvf_mgmt_dev->mdev.ops = &ifcvf_vdpa_mgmt_dev_ops; - ifcvf_mgmt_dev->mdev.device = dev; - ifcvf_mgmt_dev->adapter = adapter; - dev_type =get_dev_type (pdev);switch (dev_type) {case VIRTIO_ID_NET :
@@ -883,12 +881,11 @@ static int ifcvf_probe(struct pci_dev *pdev, const struct pci_device_id *id) goto err; } + ifcvf_mgmt_dev->mdev.ops = &ifcvf_vdpa_mgmt_dev_ops; + ifcvf_mgmt_dev->mdev.device = dev; ifcvf_mgmt_dev->mdev.max_supported_vqs = vf->nr_vring; ifcvf_mgmt_dev->mdev.supported_features = vf->hw_features; - adapter->vdpa.mdev = &ifcvf_mgmt_dev->mdev; - - ret =vdpa_mgmtdev_register (&ifcvf_mgmt_dev->mdev);if (ret) { IFCVF_ERR(pdev,
Signature · 1 line
2.31.1
PATCH v2 4/12 vDPA/ifcvf: decouple vq IRQ releasers from the adapter
In reply to Zhu LingshanThis commit decouples the IRQ releasers from the
adapter, so that these functions could be
safely invoked once probe
--- drivers/vdpa/ifcvf/ifcvf_main.c | 21 +++++++++------------ 1 file changed, 9 insertions(+), 12 deletions(-)
drivers/vdpa/ifcvf/ifcvf_main.c +9 -12
@@ -69,10 +69,9 @@ static void ifcvf_free_irq_vectors(void *data)pci_free_irq_vectors (data); } -static void ifcvf_free_per_vq_irq (struct ifcvf_adapter *adapter) +static void ifcvf_free_per_vq_irq (struct ifcvf_hw *vf) { -struct pci_dev *pdev = adapter->pdev; -struct ifcvf_hw *vf = &adapter->vf; +struct pci_dev *pdev = vf->pdev;int i;for (i =0 ; i < vf->nr_vring; i++) {
@@ -83,10 +82,9 @@ static void ifcvf_free_per_vq_irq(struct ifcvf_adapter *adapter) } } -static void ifcvf_free_vqs_reused_irq (struct ifcvf_adapter *adapter) +static void ifcvf_free_vqs_reused_irq (struct ifcvf_hw *vf) { -struct pci_dev *pdev = adapter->pdev; -struct ifcvf_hw *vf = &adapter->vf; +struct pci_dev *pdev = vf->pdev;if (vf->vqs_reused_irq != -EINVAL ) {devm_free_irq (&pdev->dev, vf->vqs_reused_irq, vf);
@@ -95,14 +93,12 @@ static void ifcvf_free_vqs_reused_irq(struct ifcvf_adapter *adapter) } -static void ifcvf_free_vq_irq (struct ifcvf_adapter *adapter) +static void ifcvf_free_vq_irq (struct ifcvf_hw *vf) { -struct ifcvf_hw *vf = &adapter->vf; -if (vf->msix_vector_status ==MSIX_VECTOR_PER_VQ_AND_CONFIG ) -ifcvf_free_per_vq_irq (adapter); +ifcvf_free_per_vq_irq (vf);else -ifcvf_free_vqs_reused_irq (adapter); +ifcvf_free_vqs_reused_irq (vf); }static void ifcvf_free_config_irq (struct ifcvf_adapter *adapter)
@@ -126,8 +122,9 @@ static void ifcvf_free_config_irq(struct ifcvf_adapter *adapter)static void ifcvf_free_irq (struct ifcvf_adapter *adapter) {struct pci_dev *pdev = adapter->pdev; +struct ifcvf_hw *vf = &adapter->vf; -ifcvf_free_vq_irq (adapter); +ifcvf_free_vq_irq (vf);ifcvf_free_config_irq (adapter);ifcvf_free_irq_vectors (pdev); }
Signature · 1 line
2.31.1
PATCH v2 5/12 vDPA/ifcvf: decouple config IRQ releaser from the adapter
In reply to Zhu LingshanThis commit decouples config IRQ releaser from the adapter, so that it could be invoked once probe or in err handlers. ifcvf_free_irq() works on ifcvf_hw in this commit
--- drivers/vdpa/ifcvf/ifcvf_main.c | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-)
drivers/vdpa/ifcvf/ifcvf_main.c +10 -12
@@ -101,10 +101,9 @@ static void ifcvf_free_vq_irq(struct ifcvf_hw *vf)ifcvf_free_vqs_reused_irq (vf); } -static void ifcvf_free_config_irq (struct ifcvf_adapter *adapter) +static void ifcvf_free_config_irq (struct ifcvf_hw *vf) { -struct pci_dev *pdev = adapter->pdev; -struct ifcvf_hw *vf = &adapter->vf; +struct pci_dev *pdev = vf->pdev;if (vf->config_irq == -EINVAL )return ;
@@ -119,13 +118,12 @@ static void ifcvf_free_config_irq(struct ifcvf_adapter *adapter) } } -static void ifcvf_free_irq (struct ifcvf_adapter *adapter) +static void ifcvf_free_irq (struct ifcvf_hw *vf) { -struct pci_dev *pdev = adapter->pdev; -struct ifcvf_hw *vf = &adapter->vf; +struct pci_dev *pdev = vf->pdev;ifcvf_free_vq_irq (vf); -ifcvf_free_config_irq (adapter); +ifcvf_free_config_irq (vf);ifcvf_free_irq_vectors (pdev); }
@@ -187,7 +185,7 @@ static int ifcvf_request_per_vq_irq(struct ifcvf_adapter *adapter)return 0 ; err: -ifcvf_free_irq (adapter); +ifcvf_free_irq (vf);return -EFAULT ; }
@@ -221,7 +219,7 @@ static int ifcvf_request_vqs_reused_irq(struct ifcvf_adapter *adapter)return 0 ; err: -ifcvf_free_irq (adapter); +ifcvf_free_irq (vf);return -EFAULT ; }
@@ -262,7 +260,7 @@ static int ifcvf_request_dev_irq(struct ifcvf_adapter *adapter)return 0 ; err: -ifcvf_free_irq (adapter); +ifcvf_free_irq (vf);return -EFAULT ;
@@ -317,7 +315,7 @@ static int ifcvf_request_config_irq(struct ifcvf_adapter *adapter)return 0 ; err: -ifcvf_free_irq (adapter); +ifcvf_free_irq (vf);return -EFAULT ; }
@@ -508,7 +506,7 @@ static int ifcvf_vdpa_reset(struct vdpa_device *vdpa_dev)if (status_old &VIRTIO_CONFIG_S_DRIVER_OK ) {ifcvf_stop_datapath (adapter); -ifcvf_free_irq (adapter); +ifcvf_free_irq (vf); }ifcvf_reset_vring (adapter);
Signature · 1 line
2.31.1
PATCH v2 6/12 vDPA/ifcvf: decouple vq irq requester from the adapter
In reply to Zhu LingshanThis commit decouples the vq irq requester from the adapter, so that these functions can be invoked since probe.
--- drivers/vdpa/ifcvf/ifcvf_main.c | 19 ++++++++----------- 1 file changed, 8 insertions(+), 11 deletions(-)
drivers/vdpa/ifcvf/ifcvf_main.c +8 -11
@@ -155,10 +155,9 @@ static int ifcvf_alloc_vectors(struct ifcvf_adapter *adapter)return ret; } -static int ifcvf_request_per_vq_irq (struct ifcvf_adapter *adapter) +static int ifcvf_request_per_vq_irq (struct ifcvf_hw *vf) { -struct pci_dev *pdev = adapter->pdev; -struct ifcvf_hw *vf = &adapter->vf; +struct pci_dev *pdev = vf->pdev;int i, vector, ret, irq; vf->vqs_reused_irq = -EINVAL ;
@@ -190,10 +189,9 @@ static int ifcvf_request_per_vq_irq(struct ifcvf_adapter *adapter)return -EFAULT ; } -static int ifcvf_request_vqs_reused_irq (struct ifcvf_adapter *adapter) +static int ifcvf_request_vqs_reused_irq (struct ifcvf_hw *vf) { -struct pci_dev *pdev = adapter->pdev; -struct ifcvf_hw *vf = &adapter->vf; +struct pci_dev *pdev = vf->pdev;int i, vector, ret, irq; vector =0 ;
@@ -266,15 +264,14 @@ static int ifcvf_request_dev_irq(struct ifcvf_adapter *adapter) } -static int ifcvf_request_vq_irq (struct ifcvf_adapter *adapter) +static int ifcvf_request_vq_irq (struct ifcvf_hw *vf) { -struct ifcvf_hw *vf = &adapter->vf;int ret;if (vf->msix_vector_status ==MSIX_VECTOR_PER_VQ_AND_CONFIG ) - ret =ifcvf_request_per_vq_irq (adapter); + ret =ifcvf_request_per_vq_irq (vf);else - ret =ifcvf_request_vqs_reused_irq (adapter); + ret =ifcvf_request_vqs_reused_irq (vf);return ret; }
@@ -341,7 +338,7 @@ static int ifcvf_request_irq(struct ifcvf_adapter *adapter)return ret; } - ret =ifcvf_request_vq_irq (adapter); + ret =ifcvf_request_vq_irq (vf);if (ret)return ret;
Signature · 1 line
2.31.1
PATCH v2 7/12 vDPA/ifcvf: decouple config/dev IRQ requester and vectors allocator from the adapter
In reply to Zhu LingshanThis commit decouples the config irq requester, the device shared irq requester and the MSI vectors allocator from the adapter. So they can be safely invoked since probe before the adapter is allocated.
--- drivers/vdpa/ifcvf/ifcvf_main.c | 21 +++++++++------------ 1 file changed, 9 insertions(+), 12 deletions(-)
drivers/vdpa/ifcvf/ifcvf_main.c +9 -12
@@ -132,10 +132,9 @@ static void ifcvf_free_irq(struct ifcvf_hw *vf)* It returns the number of allocated vectors, negative * return value when fails. */ -static int ifcvf_alloc_vectors (struct ifcvf_adapter *adapter) +static int ifcvf_alloc_vectors (struct ifcvf_hw *vf) { -struct pci_dev *pdev = adapter->pdev; -struct ifcvf_hw *vf = &adapter->vf; +struct pci_dev *pdev = vf->pdev;int max_intr, ret;/* all queues and config interrupt */
@@ -222,10 +221,9 @@ static int ifcvf_request_vqs_reused_irq(struct ifcvf_hw *vf)return -EFAULT ; } -static int ifcvf_request_dev_irq (struct ifcvf_adapter *adapter) +static int ifcvf_request_dev_irq (struct ifcvf_hw *vf) { -struct pci_dev *pdev = adapter->pdev; -struct ifcvf_hw *vf = &adapter->vf; +struct pci_dev *pdev = vf->pdev;int i, vector, ret, irq; vector =0 ;
@@ -276,10 +274,9 @@ static int ifcvf_request_vq_irq(struct ifcvf_hw *vf)return ret; } -static int ifcvf_request_config_irq (struct ifcvf_adapter *adapter) +static int ifcvf_request_config_irq (struct ifcvf_hw *vf) { -struct pci_dev *pdev = adapter->pdev; -struct ifcvf_hw *vf = &adapter->vf; +struct pci_dev *pdev = vf->pdev;int config_vector, ret;if (vf->msix_vector_status ==MSIX_VECTOR_PER_VQ_AND_CONFIG )
@@ -322,7 +319,7 @@ static int ifcvf_request_irq(struct ifcvf_adapter *adapter)struct ifcvf_hw *vf = &adapter->vf;int nvectors, ret, max_intr; - nvectors =ifcvf_alloc_vectors (adapter); + nvectors =ifcvf_alloc_vectors (vf);if (nvectors <=0 )return -EFAULT ;
@@ -333,7 +330,7 @@ static int ifcvf_request_irq(struct ifcvf_adapter *adapter)if (nvectors ==1 ) { vf->msix_vector_status =MSIX_VECTOR_DEV_SHARED ; - ret =ifcvf_request_dev_irq (adapter); + ret =ifcvf_request_dev_irq (vf);return ret; }
@@ -342,7 +339,7 @@ static int ifcvf_request_irq(struct ifcvf_adapter *adapter)if (ret)return ret; - ret =ifcvf_request_config_irq (adapter); + ret =ifcvf_request_config_irq (vf);if (ret)return ret;
Signature · 6 lines
2.31.1 _______________________________________________ Virtualization mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/virtualization
PATCH v2 8/12 vDPA/ifcvf: ifcvf_request_irq works on ifcvf_hw
In reply to Zhu LingshanAll ifcvf_request_irq's callees are refactored
to work on ifcvf_hw, so it should be decoupled
from the adapter as well
--- drivers/vdpa/ifcvf/ifcvf_main.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
drivers/vdpa/ifcvf/ifcvf_main.c +2 -3
@@ -314,9 +314,8 @@ static int ifcvf_request_config_irq(struct ifcvf_hw *vf)return -EFAULT ; } -static int ifcvf_request_irq (struct ifcvf_adapter *adapter) +static int ifcvf_request_irq (struct ifcvf_hw *vf) { -struct ifcvf_hw *vf = &adapter->vf;int nvectors, ret, max_intr; nvectors =ifcvf_alloc_vectors (vf);
@@ -468,7 +467,7 @@ static void ifcvf_vdpa_set_status(struct vdpa_device *vdpa_dev, u8 status)if ((status &VIRTIO_CONFIG_S_DRIVER_OK ) && !(status_old &VIRTIO_CONFIG_S_DRIVER_OK )) { - ret =ifcvf_request_irq (adapter); + ret =ifcvf_request_irq (vf);if (ret) { status =ifcvf_get_status (vf); status |=VIRTIO_CONFIG_S_FAILED ;
Signature · 6 lines
2.31.1 _______________________________________________ Virtualization mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/virtualization
PATCH v2 9/12 vDPA/ifcvf: manage ifcvf_hw in the mgmt_dev
In reply to Zhu LingshanThis commit allocates the hw structure in the management device structure. So the hardware can be initialized once the management device is allocated in probe.
--- drivers/vdpa/ifcvf/ifcvf_base.h | 5 +++-- drivers/vdpa/ifcvf/ifcvf_main.c | 7 ++++--- 2 files changed, 7 insertions(+), 5 deletions(-)
drivers/vdpa/ifcvf/ifcvf_base.h +3 -2
@@ -39,7 +39,7 @@#define IFCVF_INFO (pdev, fmt, ...) dev_info(&pdev->dev, fmt, ##__VA_ARGS__)#define ifcvf_private_to_vf (adapter) \ - (&((struct ifcvf_adapter *)adapter)->vf) + (((struct ifcvf_adapter *)adapter)->vf)/* all vqs and config interrupt has its own vector */ #define MSIX_VECTOR_PER_VQ_AND_CONFIG 1
@@ -95,7 +95,7 @@ struct ifcvf_hw {struct ifcvf_adapter {struct vdpa_device vdpa;struct pci_dev *pdev; -struct ifcvf_hw vf; +struct ifcvf_hw *vf; };struct ifcvf_vring_lm_cfg {
@@ -110,6 +110,7 @@ struct ifcvf_lm_cfg {struct ifcvf_vdpa_mgmt_dev {struct vdpa_mgmt_dev mdev; +struct ifcvf_hw vf;struct ifcvf_adapter *adapter;struct pci_dev *pdev; };
drivers/vdpa/ifcvf/ifcvf_main.c +4 -3
@@ -402,7 +402,7 @@ static struct ifcvf_hw *vdpa_to_vf(struct vdpa_device *vdpa_dev) {struct ifcvf_adapter *adapter =vdpa_to_adapter (vdpa_dev); -return &adapter->vf; +return adapter->vf; }static u64 ifcvf_vdpa_get_device_features (struct vdpa_device *vdpa_dev)
@@ -750,7 +750,7 @@ static int ifcvf_vdpa_dev_add(struct vdpa_mgmt_dev *mdev, const char *name,return -EOPNOTSUPP ; adapter = ifcvf_mgmt_dev->adapter; - vf = &adapter->vf; + vf = adapter->vf; pdev = adapter->pdev; vdpa_dev = &adapter->vdpa;
@@ -838,10 +838,11 @@ static int ifcvf_probe(struct pci_dev *pdev, const struct pci_device_id *id) adapter->vdpa.mdev = &ifcvf_mgmt_dev->mdev; ifcvf_mgmt_dev->adapter = adapter; - vf = &adapter->vf; + vf = &ifcvf_mgmt_dev->vf; vf->dev_type =get_dev_type (pdev); vf->base =pcim_iomap_table (pdev); vf->pdev = pdev; + adapter->vf = vf; ret =ifcvf_init_hw (vf, pdev);if (ret) {
Signature · 6 lines
2.31.1 _______________________________________________ Virtualization mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/virtualization
PATCH v2 10/12 vDPA/ifcvf: allocate the adapter in dev_add()
In reply to Zhu LingshanThe adapter is the container of the vdpa_device, this commits allocate the adapter in dev_add() rather than in probe(). So that the vdpa_device() could be re-created when the userspace creates the vdpa device, and free-ed in dev_del()
--- drivers/vdpa/ifcvf/ifcvf_main.c | 34 +++++++++++++-------------------- 1 file changed, 13 insertions(+), 21 deletions(-)
drivers/vdpa/ifcvf/ifcvf_main.c +13 -21
@@ -746,12 +746,20 @@ static int ifcvf_vdpa_dev_add(struct vdpa_mgmt_dev *mdev, const char *name,int ret; ifcvf_mgmt_dev = container_of(mdev, struct ifcvf_vdpa_mgmt_dev, mdev); -if (!ifcvf_mgmt_dev->adapter) -return -EOPNOTSUPP ; + vf = &ifcvf_mgmt_dev->vf; + pdev = vf->pdev; + adapter = vdpa_alloc_device(struct ifcvf_adapter, vdpa, + &pdev->dev, &ifc_vdpa_ops,1 ,1 ,NULL , false); +if (IS_ERR (adapter)) { +IFCVF_ERR (pdev,"Failed to allocate vDPA structure" ); +return PTR_ERR (adapter); + } - adapter = ifcvf_mgmt_dev->adapter; - vf = adapter->vf; - pdev = adapter->pdev; + ifcvf_mgmt_dev->adapter = adapter; + adapter->pdev = pdev; + adapter->vdpa.dma_dev = &pdev->dev; + adapter->vdpa.mdev = mdev; + adapter->vf = vf; vdpa_dev = &adapter->vdpa;if (name)
@@ -769,7 +777,6 @@ static int ifcvf_vdpa_dev_add(struct vdpa_mgmt_dev *mdev, const char *name,return 0 ; } -static void ifcvf_vdpa_dev_del (struct vdpa_mgmt_dev *mdev,struct vdpa_device *dev) {struct ifcvf_vdpa_mgmt_dev *ifcvf_mgmt_dev;
@@ -788,7 +795,6 @@ static int ifcvf_probe(struct pci_dev *pdev, const struct pci_device_id *id) {struct ifcvf_vdpa_mgmt_dev *ifcvf_mgmt_dev;struct device *dev = &pdev->dev; -struct ifcvf_adapter *adapter;struct ifcvf_hw *vf;u32 dev_type;int ret, i;
@@ -825,24 +831,10 @@ static int ifcvf_probe(struct pci_dev *pdev, const struct pci_device_id *id)return -ENOMEM ; } - adapter = vdpa_alloc_device(struct ifcvf_adapter, vdpa, - dev, &ifc_vdpa_ops,1 ,1 ,NULL , false); -if (IS_ERR (adapter)) { -IFCVF_ERR (pdev,"Failed to allocate vDPA structure" ); - ret =PTR_ERR (adapter); - goto err; - } - - adapter->pdev = pdev; - adapter->vdpa.dma_dev = &pdev->dev; - adapter->vdpa.mdev = &ifcvf_mgmt_dev->mdev; - ifcvf_mgmt_dev->adapter = adapter; - vf = &ifcvf_mgmt_dev->vf; vf->dev_type =get_dev_type (pdev); vf->base =pcim_iomap_table (pdev); vf->pdev = pdev; - adapter->vf = vf; ret =ifcvf_init_hw (vf, pdev);if (ret) {
Signature · 6 lines
2.31.1 _______________________________________________ Virtualization mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/virtualization
PATCH v2 11/12 vDPA/ifcvf: retire ifcvf_private_to_vf
In reply to Zhu LingshanThis commit retires ifcvf_private_to_vf, because
the vf is already a member of the adapter,
so it could be easily addressed by adapter->vf.
--- drivers/vdpa/ifcvf/ifcvf_base.h | 3 --- drivers/vdpa/ifcvf/ifcvf_main.c | 10 +++++----- 2 files changed, 5 insertions(+), 8 deletions(-)
drivers/vdpa/ifcvf/ifcvf_base.h +0 -3
@@ -38,9 +38,6 @@#define IFCVF_DBG (pdev, fmt, ...) dev_dbg(&pdev->dev, fmt, ##__VA_ARGS__)#define IFCVF_INFO (pdev, fmt, ...) dev_info(&pdev->dev, fmt, ##__VA_ARGS__) -#define ifcvf_private_to_vf (adapter) \ - (((struct ifcvf_adapter *)adapter)->vf) -/* all vqs and config interrupt has its own vector */ #define MSIX_VECTOR_PER_VQ_AND_CONFIG 1/* all vqs share a vector, and config interrupt has a separate vector */
drivers/vdpa/ifcvf/ifcvf_main.c +5 -5
@@ -346,9 +346,9 @@ static int ifcvf_request_irq(struct ifcvf_hw *vf)return 0 ; } -static int ifcvf_start_datapath (void *private) +static int ifcvf_start_datapath (struct ifcvf_adapter *adapter) { -struct ifcvf_hw *vf =ifcvf_private_to_vf (private); +struct ifcvf_hw *vf = adapter->vf;u8 status;int ret;
@@ -362,9 +362,9 @@ static int ifcvf_start_datapath(void *private)return ret; } -static int ifcvf_stop_datapath (void *private) +static int ifcvf_stop_datapath (struct ifcvf_adapter *adapter) { -struct ifcvf_hw *vf =ifcvf_private_to_vf (private); +struct ifcvf_hw *vf = adapter->vf;int i;for (i =0 ; i < vf->nr_vring; i++)
@@ -377,7 +377,7 @@ static int ifcvf_stop_datapath(void *private)static void ifcvf_reset_vring (struct ifcvf_adapter *adapter) { -struct ifcvf_hw *vf =ifcvf_private_to_vf (adapter); +struct ifcvf_hw *vf = adapter->vf;int i;for (i =0 ; i < vf->nr_vring; i++) {
Signature · 6 lines
2.31.1 _______________________________________________ Virtualization mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/virtualization
PATCH v2 12/12 vDPA/ifcvf: implement features provisioning
In reply to Zhu LingshanThis commit implements features provisioning for ifcvf, that means:
1)checkk whether the provisioned features are supported by the management device
2)vDPA device only presents selected feature bits
Examples:
a)The management device supported features:
$ vdpa mgmtdev show pci/0000:01:00.5 pci/0000:01:00.5: supported_classes net max_supported_vqs 9 dev_features MTU MAC MRG_RXBUF CTRL_VQ MQ ANY_LAYOUT VERSION_1 ACCESS_PLATFORM
b)Provision a vDPA device with all supported features:
$ vdpa dev add name vdpa0 mgmtdev pci/0000:01:00.5 $ vdpa/vdpa dev config show vdpa0 vdpa0: mac 00:e8:ca:11:be:05 link up link_announce false max_vq_pairs 4 mtu 1500 negotiated_features MRG_RXBUF CTRL_VQ MQ VERSION_1 ACCESS_PLATFORM
c)Provision a vDPA device with a subset of the supported features:
$ vdpa dev add name vdpa0 mgmtdev pci/0000:01:00.5 device_features 0x300020020 $ vdpa dev config show vdpa0 mac 00:e8:ca:11:be:05 link up link_announce false negotiated_features CTRL_VQ VERSION_1 ACCESS_PLATFORM
--- drivers/vdpa/ifcvf/ifcvf_base.c | 2 +- drivers/vdpa/ifcvf/ifcvf_base.h | 3 +++ drivers/vdpa/ifcvf/ifcvf_main.c | 13 +++++++++++++ 3 files changed, 17 insertions(+), 1 deletion(-)
drivers/vdpa/ifcvf/ifcvf_base.c +1 -1
@@ -206,7 +206,7 @@ u64 ifcvf_get_hw_features(struct ifcvf_hw *hw)u64 ifcvf_get_features (struct ifcvf_hw *hw) { -return hw->hw_features; +return hw->dev_features; }int ifcvf_verify_min_features (struct ifcvf_hw *hw,u64 features)
drivers/vdpa/ifcvf/ifcvf_base.h +3 -0
@@ -19,6 +19,7 @@#include <uapi/linux/virtio_blk.h> #include <uapi/linux/virtio_config.h> #include <uapi/linux/virtio_pci.h> +#include <uapi/linux/vdpa.h> #define N3000_DEVICE_ID 0x1041#define N3000_SUBSYS_DEVICE_ID 0x001A
@@ -75,6 +76,8 @@ struct ifcvf_hw {u32 dev_type;u64 req_features;u64 hw_features; +/* provisioned device features */ +u64 dev_features;struct virtio_pci_common_cfg __iomem *common_cfg;void __iomem *dev_cfg;struct vring_info vring[IFCVF_MAX_QUEUES ];
drivers/vdpa/ifcvf/ifcvf_main.c +13 -0
@@ -743,6 +743,7 @@ static int ifcvf_vdpa_dev_add(struct vdpa_mgmt_dev *mdev, const char *name,struct vdpa_device *vdpa_dev;struct pci_dev *pdev;struct ifcvf_hw *vf; +u64 device_features;int ret; ifcvf_mgmt_dev = container_of(mdev, struct ifcvf_vdpa_mgmt_dev, mdev);
@@ -762,6 +763,17 @@ static int ifcvf_vdpa_dev_add(struct vdpa_mgmt_dev *mdev, const char *name, adapter->vf = vf; vdpa_dev = &adapter->vdpa; + device_features = vf->hw_features; +if (config->mask &BIT_ULL (VDPA_ATTR_DEV_FEATURES )) { +if (config->device_features & ~device_features) { +IFCVF_ERR (pdev,"The provisioned features 0x%llx are not supported by this device with features 0x%llx\n" , + config->device_features, device_features); +return -EINVAL ; + } + device_features &= config->device_features; + } + vf->dev_features = device_features; +if (name) ret =dev_set_name (&vdpa_dev->dev,"%s" , name);else
@@ -866,6 +878,7 @@ static int ifcvf_probe(struct pci_dev *pdev, const struct pci_device_id *id) ifcvf_mgmt_dev->mdev.device = dev; ifcvf_mgmt_dev->mdev.max_supported_vqs = vf->nr_vring; ifcvf_mgmt_dev->mdev.supported_features = vf->hw_features; + ifcvf_mgmt_dev->mdev.config_attr_mask = (1 <<VDPA_ATTR_DEV_FEATURES ); ret =vdpa_mgmtdev_register (&ifcvf_mgmt_dev->mdev);if (ret) {
Signature · 6 lines
2.31.1 _______________________________________________ Virtualization mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/virtualization
Quoted 26 lines · Zhu Lingshan
This series implements features provisioning for ifcvf. By applying this series, we allow userspace to create a vDPA device with selected (management device supported) feature bits and mask out others.
Examples:
a)The management device supported features:$ vdpa mgmtdev show pci/0000:01:00.5 pci/0000:01:00.5: supported_classes net max_supported_vqs 9 dev_features MTU MAC MRG_RXBUF CTRL_VQ MQ ANY_LAYOUT VERSION_1 ACCESS_PLATFORMb)Provision a vDPA device with all supported features:
$ vdpa dev add name vdpa0 mgmtdev pci/0000:01:00.5 $ vdpa/vdpa dev config show vdpa0 vdpa0: mac 00:e8:ca:11:be:05 link up link_announce false max_vq_pairs 4 mtu 1500 negotiated_features MRG_RXBUF CTRL_VQ MQ VERSION_1 ACCESS_PLATFORMc)Provision a vDPA device with a subset of the supported features:
$ vdpa dev add name vdpa0 mgmtdev pci/0000:01:00.5 device_features 0x300020020 $ vdpa dev config show vdpa0 mac 00:e8:ca:11:be:05 link up link_announce false negotiated_features CTRL_VQ VERSION_1 ACCESS_PLATFORM
Quoted 7 lines
Please help review
Thanks
Changes from V1:
split original patch 1 ~ patch 3 to small patches that are less than 100 lines,
True but.
Quoted 2 lines
so they can be applied to stalbe kernel(Jason)
It requires each patch fixes a real issue so I think those can not go to -stable.
Btw, looking at git history what you want to decouple is basically functional equivalent to a partial revert of this commit:
commit 378b2e956820ff5c082d05f42828badcfbabb614
Author: Zhu Lingshan <[email protected]> Date: Fri Jul 22 19:53:05 2022 +0800
vDPA/ifcvf: support userspace to query features and MQ of a
management device
Adapting to current netlink interfaces, this commit allows userspace to query feature bits and MQ capability of a management device.
Currently both the vDPA device and the management device are the VF itself, thus this ifcvf should initialize the virtio capabilities in probe() before setting up the struct vdpa_mgmt_dev.
Message-Id: <[email protected]>
Before this commit. adapter was allocated/freed in device_add/del which should be fine.
Can we go back to doing things that way?
Thanks
Quoted 15 lines
Zhu Lingshan (12):
vDPA/ifcvf: decouple hw features manipulators from the adapter vDPA/ifcvf: decouple config space ops from the adapter vDPA/ifcvf: alloc themgmt_devbefore the adapter vDPA/ifcvf: decouple vq IRQ releasers from the adapter vDPA/ifcvf: decouple config IRQ releaser from the adapter vDPA/ifcvf: decouple vq irq requester from the adapter vDPA/ifcvf: decouple config/dev IRQ requester and vectors allocator
from the adapter
vDPA/ifcvf:ifcvf_request_irqworks onifcvf_hwvDPA/ifcvf: manageifcvf_hwin themgmt_dev
vDPA/ifcvf: allocate the adapter indev_add()vDPA/ifcvf: retireifcvf_private_to_vf
vDPA/ifcvf: implement features provisioning
Quoted 8 lines
drivers/vdpa/ifcvf/ifcvf_base.c | 32 ++----- drivers/vdpa/ifcvf/ifcvf_base.h | 10 +- drivers/vdpa/ifcvf/ifcvf_main.c | 162 +++++++++++++++----------------- 3 files changed, 91 insertions(+), 113 deletions(-)--
2.31.1
_______________________________________________
Virtualization mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
Quoted 57 lines · Jason Wang
Quoted 25 lines · Zhu Lingshan
This series implements features provisioning for ifcvf. By applying this series, we allow userspace to create a vDPA device with selected (management device supported) feature bits and mask out others.
Examples:
a)The management device supported features:$ vdpa mgmtdev show pci/0000:01:00.5 pci/0000:01:00.5: supported_classes net max_supported_vqs 9 dev_features MTU MAC MRG_RXBUF CTRL_VQ MQ ANY_LAYOUT VERSION_1 ACCESS_PLATFORMb)Provision a vDPA device with all supported features:
$ vdpa dev add name vdpa0 mgmtdev pci/0000:01:00.5 $ vdpa/vdpa dev config show vdpa0 vdpa0: mac 00:e8:ca:11:be:05 link up link_announce false max_vq_pairs 4 mtu 1500 negotiated_features MRG_RXBUF CTRL_VQ MQ VERSION_1 ACCESS_PLATFORMc)Provision a vDPA device with a subset of the supported features:
$ vdpa dev add name vdpa0 mgmtdev pci/0000:01:00.5 device_features 0x300020020 $ vdpa dev config show vdpa0 mac 00:e8:ca:11:be:05 link up link_announce false negotiated_features CTRL_VQ VERSION_1 ACCESS_PLATFORMQuoted 7 lines
Please help review
Thanks
Changes from V1:
split original patch 1 ~ patch 3 to small patches that are less than 100 lines,True but.
Quoted 2 lines
so they can be applied to stalbe kernel(Jason)
It requires each patch fixes a real issue so I think those can not go to -stable.
Btw, looking at git history what you want to decouple is basically functional equivalent to a partial revert of this commit:
commit
378b2e956820ff5c082d05f42828badcfbabb614Author: Zhu Lingshan <[email protected]> Date: Fri Jul 22 19:53:05 2022 +0800vDPA/ifcvf: support userspace to query features and MQ of a
management deviceAdapting to current netlink interfaces, this commit allows userspace to query feature bits and MQ capability of a management device.
Currently both the vDPA device and the management device are the VF itself, thus this ifcvf should initialize the virtio capabilities in
probe()before setting up the structvdpa_mgmt_dev.
Quoted 8 lines
Signed-off-by Zhu Lingshan <[email protected]>Message-Id: <[email protected]>
Signed-off-by Michael S. Tsirkin <[email protected]>Before this commit. adapter was allocated/freed in device_add/del which should be fine.
Can we go back to doing things that way?
Hi Jason
Thanks for your advice, my concern is, even revert this commit 378b2e95,
we still need to re-implement the feature "support userspace to query features and MQ of a management device" in stable kernel(still not a patch fix something but implement something), or we remove a feature in the stable kernel. And there may still need to split patches to meet the <100 lines requirement
The reason why I place the adapter allocation in probe is that currently the management device is the VF itself, move it from dev_add to probe can lighten the organization of data structures, it is not a good design anyway, so this series tries to fix them as well.
Maybe not to to sable
Thanks
Quoted 26 lines
Thanks
Quoted 23 lines
Zhu Lingshan (12):
vDPA/ifcvf: decouple hw features manipulators from the adapter vDPA/ifcvf: decouple config space ops from the adapter vDPA/ifcvf: alloc themgmt_devbefore the adapter vDPA/ifcvf: decouple vq IRQ releasers from the adapter vDPA/ifcvf: decouple config IRQ releaser from the adapter vDPA/ifcvf: decouple vq irq requester from the adapter vDPA/ifcvf: decouple config/dev IRQ requester and vectors allocator
from the adapter
vDPA/ifcvf:ifcvf_request_irqworks onifcvf_hwvDPA/ifcvf: manageifcvf_hwin themgmt_dev
vDPA/ifcvf: allocate the adapter indev_add()vDPA/ifcvf: retireifcvf_private_to_vf
vDPA/ifcvf: implement features provisioningdrivers/vdpa/ifcvf/ifcvf_base.c | 32 ++----- drivers/vdpa/ifcvf/ifcvf_base.h | 10 +- drivers/vdpa/ifcvf/ifcvf_main.c | 162 +++++++++++++++----------------- 3 files changed, 91 insertions(+), 113 deletions(-)--
2.31.1
Quoted 75 lines · Lingshan
Quoted 57 lines · Jason Wang
Quoted 25 lines · Zhu Lingshan
This series implements features provisioning for ifcvf. By applying this series, we allow userspace to create a vDPA device with selected (management device supported) feature bits and mask out others.
Examples:
a)The management device supported features:$ vdpa mgmtdev show pci/0000:01:00.5 pci/0000:01:00.5: supported_classes net max_supported_vqs 9 dev_features MTU MAC MRG_RXBUF CTRL_VQ MQ ANY_LAYOUT VERSION_1 ACCESS_PLATFORMb)Provision a vDPA device with all supported features:
$ vdpa dev add name vdpa0 mgmtdev pci/0000:01:00.5 $ vdpa/vdpa dev config show vdpa0 vdpa0: mac 00:e8:ca:11:be:05 link up link_announce false max_vq_pairs 4 mtu 1500 negotiated_features MRG_RXBUF CTRL_VQ MQ VERSION_1 ACCESS_PLATFORMc)Provision a vDPA device with a subset of the supported features:
$ vdpa dev add name vdpa0 mgmtdev pci/0000:01:00.5 device_features 0x300020020 $ vdpa dev config show vdpa0 mac 00:e8:ca:11:be:05 link up link_announce false negotiated_features CTRL_VQ VERSION_1 ACCESS_PLATFORMQuoted 7 lines
Please help review
Thanks
Changes from V1:
split original patch 1 ~ patch 3 to small patches that are less than 100 lines,True but.
Quoted 2 lines
so they can be applied to stalbe kernel(Jason)
It requires each patch fixes a real issue so I think those can not go to -stable.
Btw, looking at git history what you want to decouple is basically functional equivalent to a partial revert of this commit:
commit
378b2e956820ff5c082d05f42828badcfbabb614
Author: Zhu Lingshan <[email protected]>
Date: Fri Jul 22 19:53:05 2022 +0800vDPA/ifcvf: support userspace to query features and MQ of a management device
Adapting to current netlink interfaces, this commit allows userspace to query feature bits and MQ capability of a management device.
Currently both the vDPA device and the management device are the VF itself, thus this ifcvf should initialize the virtio capabilities in
probe()before setting up the structvdpa_mgmt_dev.Quoted 8 lines
Signed-off-by Zhu Lingshan <[email protected]>Message-Id: <[email protected]>
Signed-off-by Michael S. Tsirkin <[email protected]>Before this commit. adapter was allocated/freed in device_add/del which should be fine.
Can we go back to doing things that way?
Hi Jason
Thanks for your advice, my concern is, even revert this commit
378b2e95,
we still need to re-implement the feature "support userspace to query features and MQ of a management device" in stable kernel(still not a patch fix something but implement something), or we remove a feature in the stable kernel. And there may still need to split patches to meet the <100 lines requirement
Quoted 7 lines
The reason why I place the adapter allocation in probe is that currently the management device is the VF itself, move it from
dev_addto probe can lighten the organization of data structures, it is not a good design anyway, so this series tries to fix them as well.Maybe not to to sable
Thanks
Hi Jason,
Ping,
shall I drop the "cc stable" tag and resend?
Maybe squash the patches because they are not going to stable tree?
Thanks
Quoted 24 lines
Quoted 24 lines
Thanks
Quoted 21 lines
Zhu Lingshan (12):
vDPA/ifcvf: decouple hw features manipulators from the adapter vDPA/ifcvf: decouple config space ops from the adapter vDPA/ifcvf: alloc themgmt_devbefore the adapter vDPA/ifcvf: decouple vq IRQ releasers from the adapter vDPA/ifcvf: decouple config IRQ releaser from the adapter vDPA/ifcvf: decouple vq irq requester from the adapter vDPA/ifcvf: decouple config/dev IRQ requester and vectors allocator from the adapter
vDPA/ifcvf:ifcvf_request_irqworks onifcvf_hwvDPA/ifcvf: manageifcvf_hwin themgmt_dev
vDPA/ifcvf: allocate the adapter indev_add()vDPA/ifcvf: retireifcvf_private_to_vf
vDPA/ifcvf: implement features provisioningdrivers/vdpa/ifcvf/ifcvf_base.c | 32 ++----- drivers/vdpa/ifcvf/ifcvf_base.h | 10 +- drivers/vdpa/ifcvf/ifcvf_main.c | 162 +++++++++++++++----------------- 3 files changed, 91 insertions(+), 113 deletions(-)
Quoted 4 lines
Quoted 3 lines
Quoted 3 lines
Signature · 1 line
2.31.1
_______________________________________________
Virtualization mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/virtualization