From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "Zhu, Lingshan" <lingshan.zhu@intel.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"sburla@marvell.com" <sburla@marvell.com>,
Shahaf Shuler <shahafs@nvidia.com>,
Maor Gottlieb <maorg@nvidia.com>,
Yishai Hadas <yishaih@nvidia.com>,
"jasowang@redhat.com" <jasowang@redhat.com>
Subject: Re: [virtio-comment] [PATCH v2 0/8] Introduce device migration support commands
Date: Wed, 18 Oct 2023 02:04:18 -0400 [thread overview]
Message-ID: <20231018020403-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB54818B90249B51BC2803BB9DDCD5A@PH0PR12MB5481.namprd12.prod.outlook.com>
On Wed, Oct 18, 2023 at 04:04:15AM +0000, Parav Pandit wrote:
>
>
> > From: Zhu, Lingshan <lingshan.zhu@intel.com>
> > Sent: Wednesday, October 18, 2023 7:27 AM
> >
> > > Changelog:
> > > ==========
> > > v1->v2:
> > > - Addressed comments from Michael and Jason
> > > - replaced iova to page/physical address range in write recording
> > > commands
> > > - several device specific requirements added to clarify, interaction of
> > > device reset, FLR, PCI PM and admin commands
> > > - added device context fields query command to learn compatibility
> > > - split device context field type range into generic and device
> > > specific
> > > - added device context extension section to maintain backward and future
> > > compatibility
> > > - several rewording in theory of operation
> > > - added requirements to cover config space read/write interaction with
> > > device context commands
> > > - added assumption about pci config space and msix table not present in
> > > device context, which can be added when hypervisor need them
>
> > We also didn't see these issues addressed in your V2. So, what's the purpose of
> > releasing this V2?
> The purpose to cover comments and improvements from Michael and Jason as listed above.
> Only questions from 10/16 and 10/17 are yet to cover.
> I will answer them this week.
Maybe mention this in the cover letter next time. Thanks!
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/
prev parent reply other threads:[~2023-10-18 6:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 20:06 [virtio-comment] [PATCH v2 0/8] Introduce device migration support commands Parav Pandit
2023-10-17 20:06 ` [virtio-comment] [PATCH v2 1/8] admin: Add theory of operation for device migration Parav Pandit
2023-10-17 20:06 ` [virtio-comment] [PATCH v2 2/8] admin: Redefine reserved2 as command specific output Parav Pandit
2023-10-17 20:06 ` [virtio-comment] [PATCH v2 3/8] device-context: Define the device context fields for device migration Parav Pandit
2023-10-17 20:06 ` [virtio-comment] [PATCH v2 4/8] admin: Add device migration admin commands Parav Pandit
2023-10-17 20:06 ` [virtio-comment] [PATCH v2 5/8] admin: Add requirements of device migration commands Parav Pandit
2023-10-17 20:06 ` [virtio-comment] [PATCH v2 6/8] admin: Add theory of operation for write recording commands Parav Pandit
2023-10-17 20:06 ` [virtio-comment] [PATCH v2 7/8] admin: Add " Parav Pandit
2023-10-17 20:06 ` [virtio-comment] [PATCH v2 8/8] admin: Add requirements of write reporting commands Parav Pandit
2023-10-18 0:53 ` [virtio-comment] [PATCH v2 0/8] Introduce device migration support commands Jason Wang
2023-10-18 4:02 ` Parav Pandit
2023-10-18 1:56 ` Zhu, Lingshan
2023-10-18 4:04 ` Parav Pandit
2023-10-18 6:04 ` Michael S. Tsirkin [this message]
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=20231018020403-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=maorg@nvidia.com \
--cc=parav@nvidia.com \
--cc=sburla@marvell.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=yishaih@nvidia.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