On Tue, Oct 17, 2023 at 9:32 PM Bruce Richardson
<bruce.richard...@intel.com> wrote:
>
> After calling rte_event_dev_info_get() the ".dev" field of the info
> structure should have a pointer to the underlying device, allowing the
> user to e.g. get the device name using using rte_dev_name(info.dev).
>
> The distributed software eventdev info structure did not return a
> correct device pointer, though, instead returning NULL, which caused
> crashes getting "rte_dev_name". Initializing the dev pointer inside the
> "eventdev" struct in the device probe function fixes this by ensuring we
> have a valid pointer to return in info_get calls.
>
> Fixes: 46a186b1f0c5 ("event/dsw: add device registration and build system")
> Cc: mattias.ronnb...@ericsson.com
>
> Signed-off-by: Bruce Richardson <bruce.richard...@intel.com>Is this issue for all "vdev" devices? if so, Please check for drivers/event/skeleton too. > --- > drivers/event/dsw/dsw_evdev.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/event/dsw/dsw_evdev.c b/drivers/event/dsw/dsw_evdev.c > index 785c12f61f..44da3c60d1 100644 > --- a/drivers/event/dsw/dsw_evdev.c > +++ b/drivers/event/dsw/dsw_evdev.c > @@ -440,6 +440,7 @@ dsw_probe(struct rte_vdev_device *vdev) > return -EFAULT; > > dev->dev_ops = &dsw_evdev_ops; > + dev->dev = &vdev->device; > dev->enqueue = dsw_event_enqueue; > dev->enqueue_burst = dsw_event_enqueue_burst; > dev->enqueue_new_burst = dsw_event_enqueue_new_burst; > -- > 2.39.2 >
