From: Parav Pandit <parav@nvidia.com>
To: "lingshan.zhu@intel.com" <lingshan.zhu@intel.com>
Cc: "virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
"virtio@lists.oasis-open.org" <virtio@lists.oasis-open.org>
Subject: [virtio-comment] virtio member device provisioning get/set and virtio child device life cycle mixing not needed
Date: Wed, 28 Jun 2023 00:22:54 +0000 [thread overview]
Message-ID: <PH0PR12MB5481821452DA2A9572714BB9DC24A@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
Hi Lingshan Zhu,
I have reviewed v4 version transport VQ a while back that consist of two main pieces.
1. some virtio device creation/destroy commands
2. virtio device feature and config space provisioning commands.
Many of us are seeing the value of device provisioning commands with/without live migration.
New virtio devices do not need to follow any existing of config space etc per say for real hw.
There is some value in reusing software but it may not be the prime driving factor for brand new devices.
This needs more discussion and not as_is done in the v4.
So, if you are planning to revise your transport vq patches as admin commands, please split the series into two.
a. device and config space provisioning SET/GET part.
b. virtio child device creation aka SIOV/SF etc.
First #a, followed by #b.
Piece #a will be usable for SRIOV VFs + SF/SIOV devices and provides unified APIs across two different device group types.
Parav
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 reply other threads:[~2023-06-28 0:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 0:22 Parav Pandit [this message]
2023-06-28 7:30 ` [virtio-comment] Re: virtio member device provisioning get/set and virtio child device life cycle mixing not needed Zhu, Lingshan
2023-06-28 13:10 ` Parav Pandit
2023-06-29 2:18 ` Zhu, Lingshan
2023-06-29 2:23 ` Parav Pandit
2023-06-29 2:38 ` Zhu, Lingshan
2023-06-29 2:47 ` Parav Pandit
2023-06-29 4:01 ` Zhu, Lingshan
2023-06-29 4:11 ` Parav Pandit
2023-06-29 6:35 ` Zhu, Lingshan
2023-06-29 16:47 ` Parav Pandit
2023-06-30 3:09 ` Zhu, Lingshan
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=PH0PR12MB5481821452DA2A9572714BB9DC24A@PH0PR12MB5481.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=lingshan.zhu@intel.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).