All of lore.kernel.org
 help / color / mirror / Atom feed
From: Parav Pandit via Virtualization <virtualization@lists.linux-foundation.org>
To: Xie Yongji <xieyongji@bytedance.com>,
	"mst@redhat.com" <mst@redhat.com>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"lingshan.zhu@intel.com" <lingshan.zhu@intel.com>,
	Eli Cohen <elic@nvidia.com>
Cc: "virtualization@lists.linux-foundation.org"
	<virtualization@lists.linux-foundation.org>
Subject: RE: [PATCH v2 2/3] vdpa: Add a device object for vdpa management device
Date: Mon, 16 May 2022 20:06:23 +0000	[thread overview]
Message-ID: <PH0PR12MB54813F96E346D591FBE238C1DCCF9@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220516060342.106-2-xieyongji@bytedance.com>



> From: Xie Yongji <xieyongji@bytedance.com>
> Sent: Monday, May 16, 2022 2:04 AM
> 
> Introduce a device object for vdpa management device to control its
> lifecycle. 
Why is this needed?
What is the limitation of current approach that requires new device for mgmtdev?
The primary motivation is missing in the commit log here.

> 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.
What is the bug, can you please explain?
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  parent reply	other threads:[~2022-05-16 20:06 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-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
     [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 [this message]
     [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
     [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

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=PH0PR12MB54813F96E346D591FBE238C1DCCF9@PH0PR12MB5481.namprd12.prod.outlook.com \
    --to=virtualization@lists.linux-foundation.org \
    --cc=elic@nvidia.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jasowang@redhat.com \
    --cc=lingshan.zhu@intel.com \
    --cc=mst@redhat.com \
    --cc=parav@nvidia.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.