From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "Zhu, Lingshan" <lingshan.zhu@intel.com>,
"virtio@lists.oasis-open.org" <virtio@lists.oasis-open.org>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
"hengqi@linux.alibaba.com" <hengqi@linux.alibaba.com>
Subject: [virtio-comment] Re: proposal: use admin command (and aq) of the device to query config space
Date: Wed, 2 Aug 2023 08:10:42 -0400 [thread overview]
Message-ID: <20230802080959-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <DM8PR12MB54800DA6273ABD4019720C79DC0BA@DM8PR12MB5480.namprd12.prod.outlook.com>
On Wed, Aug 02, 2023 at 11:58:31AM +0000, Parav Pandit wrote:
>
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Wednesday, August 2, 2023 5:24 PM
>
> > > 2. Build SIOV device ground up that does not need to have existing limitations
> > of 1.x.
> > >
> > > The transport VQ proposal 4 patches had heavy inclination for #1 without
> > mentioning the real objective in the cover letter.
> > > I was proposing that when virtio builds SIOV device it should start with #2.
> > > Because #1 is sort of handled with sr-iov or vdpa already.
> > >
> > > #2 is more critical to get it right, after SIOV R2 spec is defined.
> >
> >
> > Can't we address both? E.g. use a different group type.
>
> SIOV device is just one type, serving two kinds of commands one for supporting backward compat, second for newer interface.
Not sure about specifics but we can have two groups e.g. SIOV-compat and
SIOV-passthrough.
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2023-08-02 12:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 7:09 [virtio-comment] proposal: use admin command (and aq) of the device to query config space Parav Pandit
2023-08-02 4:20 ` [virtio-comment] " Michael S. Tsirkin
2023-08-02 4:33 ` [virtio-comment] " Parav Pandit
2023-08-02 8:45 ` [virtio-comment] " Zhu, Lingshan
2023-08-02 8:59 ` [virtio-comment] " Parav Pandit
2023-08-02 9:40 ` [virtio-comment] " Zhu, Lingshan
2023-08-02 10:00 ` [virtio-comment] " Parav Pandit
2023-08-02 11:35 ` [virtio-comment] " Michael S. Tsirkin
2023-08-02 11:51 ` [virtio-comment] " Parav Pandit
2023-08-02 11:53 ` [virtio-comment] " Michael S. Tsirkin
2023-08-02 11:58 ` [virtio-comment] " Parav Pandit
2023-08-02 12:10 ` Michael S. Tsirkin [this message]
2023-08-02 8:53 ` [virtio-comment] " Jason Wang
2023-08-02 9:07 ` Parav Pandit
2023-08-02 9:32 ` [virtio-comment] Re: [virtio] " Jason Wang
2023-08-02 9:57 ` [virtio-comment] " Parav Pandit
2023-08-02 11:25 ` [virtio-comment] " Michael S. Tsirkin
2023-08-02 11:29 ` [virtio-comment] " Parav Pandit
2023-08-02 11:39 ` [virtio-comment] " Michael S. Tsirkin
2023-08-02 11:44 ` Parav Pandit
2023-08-02 11:50 ` Michael S. Tsirkin
2023-08-02 11:56 ` Parav Pandit
2023-08-02 12:09 ` Michael S. Tsirkin
2023-08-03 2:55 ` Jason Wang
2023-08-03 10:13 ` [virtio-comment] " Parav Pandit
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=20230802080959-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=hengqi@linux.alibaba.com \
--cc=lingshan.zhu@intel.com \
--cc=parav@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio@lists.oasis-open.org \
--cc=xuanzhuo@linux.alibaba.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.