From: Cornelia Huck <cohuck@redhat.com>
To: Jason Gunthorpe <jgg@nvidia.com>,
Alex Williamson <alex.williamson@redhat.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, kvm@vger.kernel.org,
Kirti Wankhede <kwankhede@nvidia.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>,
Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
Yishai Hadas <yishaih@nvidia.com>
Subject: Re: [PATCH RFC v2] vfio: Documentation for the migration region
Date: Thu, 02 Dec 2021 18:05:36 +0100 [thread overview]
Message-ID: <87tufrgcnz.fsf@redhat.com> (raw)
In-Reply-To: <20211201232502.GO4670@nvidia.com>
On Wed, Dec 01 2021, Jason Gunthorpe <jgg@nvidia.com> wrote:
> On Wed, Dec 01, 2021 at 01:03:14PM -0700, Alex Williamson wrote:
>> But if this document is suggesting the mlx5/QEMU interpretation is the
>> only valid interpretations for driver authors, those clarifications
>> should be pushed back into the uAPI header.
>
> Can we go the other way and move more of the uAPI header text here?
Where should a userspace author look when they try to implement support
for vfio migration? I think we need to answer that question first.
Maybe we should separate "these are the rules that an implementation
must obey" from "here's a more verbose description of how things work,
and how you can arrive at a working implementation". The former would go
into the header, while the latter can go into this document. (The
generated documentation can be linked from the header file.)
next prev parent reply other threads:[~2021-12-02 17:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 14:45 [PATCH RFC v2] vfio: Documentation for the migration region Jason Gunthorpe
2021-11-30 17:26 ` Alex Williamson
2021-11-30 18:59 ` Jason Gunthorpe
2021-11-30 22:35 ` Alex Williamson
2021-12-01 3:14 ` Jason Gunthorpe
2021-12-01 9:54 ` Shameerali Kolothum Thodi
2021-12-01 13:49 ` Jason Gunthorpe
2021-12-01 20:03 ` Alex Williamson
2021-12-01 23:25 ` Jason Gunthorpe
2021-12-02 17:05 ` Cornelia Huck [this message]
2021-12-02 17:41 ` Jason Gunthorpe
2021-12-02 17:46 ` Cornelia Huck
2021-12-03 18:06 ` Alex Williamson
2021-12-06 16:03 ` Cornelia Huck
2021-12-06 17:34 ` Jason Gunthorpe
2021-12-06 18:06 ` Cornelia Huck
2021-12-06 19:19 ` Jason Gunthorpe
2021-12-07 11:16 ` Cornelia Huck
2021-12-07 15:51 ` Jason Gunthorpe
2021-12-07 16:30 ` Cornelia Huck
2021-12-07 17:00 ` Jason Gunthorpe
2021-12-08 16:06 ` Alex Williamson
2021-12-08 20:27 ` Jason Gunthorpe
2021-12-06 19:15 ` Jason Gunthorpe
2021-12-07 10:50 ` Cornelia Huck
2021-12-07 15:37 ` Jason Gunthorpe
2021-12-07 15:56 ` Cornelia Huck
2021-12-07 16:13 ` Jason Gunthorpe
2021-12-07 16:22 ` Alex Williamson
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=87tufrgcnz.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=corbet@lwn.net \
--cc=jgg@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--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 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.