vduse: Tie vduse mgmtdev and its device
authorParav Pandit <parav@nvidia.com>
Mon, 13 Jun 2022 19:52:23 +0000 (22:52 +0300)
committerMichael S. Tsirkin <mst@redhat.com>
Fri, 24 Jun 2022 06:49:48 +0000 (02:49 -0400)
commit0e0348ac3f0a6e6606f1aa5acb1803ada913aa3d
treea83a2d6b44c73b0dcd5371b2c81a4387bf9f0049
parentace9252446ec615cd79a5f77d90edb25c0b9d024
vduse: Tie vduse mgmtdev and its device

vduse devices are not backed by any real devices such as PCI. Hence it
doesn't have any parent device linked to it.

Kernel driver model in [1] suggests to avoid an empty device
release callback.

Hence tie the mgmtdevice object's life cycle to an allocate dummy struct
device instead of static one.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/core-api/kobject.rst?h=v5.18-rc7#n284

Signed-off-by: Parav Pandit <parav@nvidia.com>
Message-Id: <20220613195223.473966-1-parav@nvidia.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Xie Yongji <xieyongji@bytedance.com>
Acked-by: Jason Wang <jasowang@redhat.com>
drivers/vdpa/vdpa_user/vduse_dev.c