From: "Michael S. Tsirkin" <mst@redhat.com>
To: Yongji Xie <xieyongji@bytedance.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
virtualization <virtualization@lists.linux-foundation.org>,
"Zhu, Lingshan" <lingshan.zhu@intel.com>,
Eli Cohen <elic@nvidia.com>
Subject: Re: [PATCH v2 2/3] vdpa: Add a device object for vdpa management device
Date: Mon, 16 May 2022 05:54:23 -0400 [thread overview]
Message-ID: <20220516055356-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACycT3uoWjYjogi0H4yrA7GuKnY=djt6BmafoRB-rbmz+8Y4BA@mail.gmail.com>
On Mon, May 16, 2022 at 05:31:27PM +0800, Yongji Xie wrote:
> On Mon, May 16, 2022 at 5:14 PM Jason Wang <jasowang@redhat.com> wrote:
> >
> >
> > 在 2022/5/16 14:03, Xie Yongji 写道:
> > > Introduce a device object for vdpa management device to control
> > > its lifecycle. And the device name will be used to match
> > > VDPA_ATTR_MGMTDEV_DEV_NAME field of netlink message rather than
> > > using parent device name.
> > >
> > > With this patch applied, drivers should use vdpa_mgmtdev_alloc()
> > > or _vdpa_mgmtdev_alloc() to allocate a vDPA management device
> > > before calling vdpa_mgmtdev_register(). And some buggy empty
> > > release function can also be removed from the driver codes.
> > >
> > > Signed-off-by: Xie Yongji <xieyongji@bytedance.com>
> > > ---
> > > drivers/vdpa/ifcvf/ifcvf_main.c | 11 ++--
> > > drivers/vdpa/mlx5/net/mlx5_vnet.c | 11 ++--
> > > drivers/vdpa/vdpa.c | 92 ++++++++++++++++++++++++----
> > > drivers/vdpa/vdpa_sim/vdpa_sim_blk.c | 39 ++++--------
> > > drivers/vdpa/vdpa_sim/vdpa_sim_net.c | 46 +++++---------
> > > drivers/vdpa/vdpa_user/vduse_dev.c | 38 ++++--------
> > > include/linux/vdpa.h | 38 +++++++++++-
> > > 7 files changed, 168 insertions(+), 107 deletions(-)
> > >
> > > diff --git a/drivers/vdpa/ifcvf/ifcvf_main.c b/drivers/vdpa/ifcvf/ifcvf_main.c
> > > index 4366320fb68d..d4087c37cfdf 100644
> > > --- a/drivers/vdpa/ifcvf/ifcvf_main.c
> > > +++ b/drivers/vdpa/ifcvf/ifcvf_main.c
> > > @@ -821,10 +821,11 @@ static int ifcvf_probe(struct pci_dev *pdev, const struct pci_device_id *id)
> > > u32 dev_type;
> > > int ret;
> > >
> > > - ifcvf_mgmt_dev = kzalloc(sizeof(struct ifcvf_vdpa_mgmt_dev), GFP_KERNEL);
> > > - if (!ifcvf_mgmt_dev) {
> > > + ifcvf_mgmt_dev = vdpa_mgmtdev_alloc(struct ifcvf_vdpa_mgmt_dev,
> > > + mdev, dev_name(dev), dev);
> >
> >
> > Just wonder if it's better to make vDPA device a child of the mgmt
> > device instead of the PCI device?
> >
> > (Currently we use PCI device as the parent of the vDPA device, or at
> > least we can do this for the simulator which doesn't have a parent?)
> >
>
> Make sense. I think we can do it for all vDPA drivers. Make sure the
> parent of the vDPA device is the vDPA management device.
>
> Thanks,
> Yongji
that's an ABI change though isn't it? parent is exposed in sysfs,
right?
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-05-16 9:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220516060342.106-1-xieyongji@bytedance.com>
2022-05-16 6:13 ` [PATCH v2 1/3] vduse: Pass management device pointer to vduse_dev_init_vdpa() Greg KH
[not found] ` <20220516060342.106-3-xieyongji@bytedance.com>
2022-05-16 6:14 ` [PATCH v2 3/3] Docs/ABI/testing: Add VDUSE sysfs interface ABI document Greg KH
2022-05-16 8:33 ` [PATCH v2 1/3] vduse: Pass management device pointer to vduse_dev_init_vdpa() Michael S. Tsirkin
[not found] ` <20220516060342.106-2-xieyongji@bytedance.com>
2022-05-16 6:13 ` [PATCH v2 2/3] vdpa: Add a device object for vdpa management device Greg KH
2022-05-16 8:32 ` Michael S. Tsirkin
2022-05-16 9:14 ` Jason Wang
[not found] ` <CACycT3uoWjYjogi0H4yrA7GuKnY=djt6BmafoRB-rbmz+8Y4BA@mail.gmail.com>
2022-05-16 9:54 ` Michael S. Tsirkin [this message]
[not found] ` <CACycT3sqEJ7JSYV646m6CLVH5tKpfbTUV4Oz+XcfXTe4ApEE1w@mail.gmail.com>
2022-05-16 10:34 ` Michael S. Tsirkin
2022-05-16 11:54 ` Greg KH
2022-05-17 6:29 ` Jason Wang
2022-05-17 6:38 ` Greg KH
2022-05-16 20:06 ` Parav Pandit via Virtualization
[not found] ` <CACycT3sRc4bk+3oq7FLzpBMCG_XRN7tOaeEAtNg69o3h8c3=EA@mail.gmail.com>
2022-05-17 12:21 ` Parav Pandit via Virtualization
2022-05-17 13:54 ` gregkh
2022-05-17 23:03 ` Parav Pandit via Virtualization
2022-05-18 8:31 ` Jason Wang
2022-05-23 2:00 ` Parav Pandit via Virtualization
2022-05-23 3:41 ` Jason Wang
2022-05-24 1:07 ` Parav Pandit via Virtualization
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220516055356-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=elic@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=lingshan.zhu@intel.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xieyongji@bytedance.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).