Previously, detach port on secondary process will mess primary
process and cause same device can't be attached again, by take
advantage of rte_eth_release_port_private, we can support this
with minor change.

Signed-off-by: Qi Zhang <qi.z.zh...@intel.com>
---
 drivers/net/kni/rte_eth_kni.c | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/drivers/net/kni/rte_eth_kni.c b/drivers/net/kni/rte_eth_kni.c
index ab63ea427..e5679c76a 100644
--- a/drivers/net/kni/rte_eth_kni.c
+++ b/drivers/net/kni/rte_eth_kni.c
@@ -419,6 +419,7 @@ eth_kni_probe(struct rte_vdev_device *vdev)
                }
                /* TODO: request info from primary to set up Rx and Tx */
                eth_dev->dev_ops = &eth_kni_ops;
+               eth_dev->device = &vdev->device;
                rte_eth_dev_probing_finish(eth_dev);
                return 0;
        }
@@ -463,6 +464,16 @@ eth_kni_remove(struct rte_vdev_device *vdev)
        if (eth_dev == NULL)
                return -1;
 
+       if (rte_eal_process_type() != RTE_PROC_PRIMARY) {
+               /* detach device on local pprocess only */
+               if (strlen(rte_vdev_device_args(vdev)) == 0)
+                       return rte_eth_dev_release_port_private(eth_dev);
+               /**
+                * else this is a private device for current process
+                * so continue with normal detach scenario
+                */
+       }
+
        eth_kni_dev_stop(eth_dev);
 
        internals = eth_dev->data->dev_private;
-- 
2.13.6

Reply via email to