From: Stefan Hajnoczi <stefanha@gmail.com>
To: Felipe Franciosi <felipe@nutanix.com>
Cc: "benjamin.walker@intel.com" <benjamin.walker@intel.com>,
John G Johnson <john.g.johnson@oracle.com>,
Swapnil Ingle <swapnil.ingle@nutanix.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"tina.zhang@intel.com" <tina.zhang@intel.com>,
"jag.raman@oracle.com" <jag.raman@oracle.com>,
"james.r.harris@intel.com" <james.r.harris@intel.com>,
"elena.ufimtseva@oracle.com" <elena.ufimtseva@oracle.com>,
"Kanth.Ghatraju@oracle.com" <Kanth.Ghatraju@oracle.com>,
"marcandre.lureau@redhat.com" <marcandre.lureau@redhat.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"yuvalkashtan@gmail.com" <yuvalkashtan@gmail.com>,
"dgilbert@redhat.com" <dgilbert@redhat.com>,
"ismael@linux.com" <ismael@linux.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"changpeng.liu@intel.com" <changpeng.liu@intel.com>,
"tomassetti.andrea@gmail.com" <tomassetti.andrea@gmail.com>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
Raphael Norwitz <raphael.norwitz@nutanix.com>,
"xiuchun.lu@intel.com" <xiuchun.lu@intel.com>,
Thanos Makatos <thanos.makatos@nutanix.com>
Subject: Re: [PATCH v4] introduce vfio-user protocol specification
Date: Fri, 30 Oct 2020 19:14:02 +0000 [thread overview]
Message-ID: <CAJSP0QXx4iqKYTrFnjW=iTmfC=nQ6T6+dS69vwYi2zdW-4riag@mail.gmail.com> (raw)
In-Reply-To: <A375B06C-FA78-4392-A569-AE494EEF9870@nutanix.com>
On Thu, Oct 15, 2020 at 2:39 PM Felipe Franciosi <felipe@nutanix.com> wrote:
> > On Oct 13, 2020, at 10:30 AM, Stefan Hajnoczi <stefanha@redhat.com> wrote:> >
> > On Fri, Oct 02, 2020 at 10:14:23AM +0000, Felipe Franciosi wrote:
> >>> On Sep 30, 2020, at 3:24 PM, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> >>> On Tue, Sep 29, 2020 at 09:21:54AM -0700, John G Johnson wrote:
> >>>>> On Sep 29, 2020, at 3:37 AM, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> >>>>>
> >>>>> On Mon, Sep 28, 2020 at 09:58:37AM +0000, Thanos Makatos wrote:
> Per Daniel's response on the other fork of the thread, I think we can
> develop faster if we're not depending on qemu-devel. With the right
> set of maintainers on the project, there's arguably more flexibility
> in working at a restricted set of code. QEMU can then update the
> submodule when a "checkpoint" is ready.
Sure, if you are happy with the submodule approach that's great.
On the QEMU side the device name should have an "x-" prefix so it's
clear that the feature is experimental and subject to change. This way
there is no stability guarantee during development. Both the protocol
and command-line can be changed without introducing feature bits and
keeping backwards compatibility.
Stefan
next prev parent reply other threads:[~2020-10-30 19:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 11:20 [PATCH v3] introduce VFIO-over-socket protocol specificaion Thanos Makatos
2020-07-21 16:33 ` Nikos Dragazis
2020-07-22 11:43 ` Thanos Makatos
2020-09-15 14:29 ` [PATCH v4] introduce vfio-user protocol specification Thanos Makatos
2020-09-24 8:21 ` Stefan Hajnoczi
2020-09-24 9:24 ` Michael S. Tsirkin
2020-09-28 9:58 ` Thanos Makatos
2020-09-29 10:37 ` Stefan Hajnoczi
2020-09-29 16:21 ` John G Johnson
2020-09-30 14:24 ` Stefan Hajnoczi
2020-10-02 10:14 ` Felipe Franciosi
2020-10-13 9:30 ` Stefan Hajnoczi
2020-10-15 13:36 ` Felipe Franciosi
2020-10-30 19:14 ` Stefan Hajnoczi [this message]
2020-10-13 9:42 ` Daniel P. Berrangé
2020-09-29 10:41 ` Stefan Hajnoczi
2020-10-28 16:10 ` [PATCH v5] " Thanos Makatos
2020-10-28 16:41 ` Thanos Makatos
2020-10-30 17:03 ` John Levon
2020-11-02 11:29 ` Thanos Makatos
2020-11-02 11:41 ` John Levon
2020-11-02 11:51 ` Thanos Makatos
2020-11-06 1:50 ` John G Johnson
2020-11-07 12:26 ` John Levon
2020-11-09 12:07 ` Thanos Makatos
2020-11-09 9:20 ` Thanos Makatos
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='CAJSP0QXx4iqKYTrFnjW=iTmfC=nQ6T6+dS69vwYi2zdW-4riag@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=Kanth.Ghatraju@oracle.com \
--cc=alex.williamson@redhat.com \
--cc=benjamin.walker@intel.com \
--cc=changpeng.liu@intel.com \
--cc=dgilbert@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=felipe@nutanix.com \
--cc=ismael@linux.com \
--cc=jag.raman@oracle.com \
--cc=james.r.harris@intel.com \
--cc=john.g.johnson@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
--cc=stefanha@redhat.com \
--cc=swapnil.ingle@nutanix.com \
--cc=thanos.makatos@nutanix.com \
--cc=tina.zhang@intel.com \
--cc=tomassetti.andrea@gmail.com \
--cc=xiuchun.lu@intel.com \
--cc=yuvalkashtan@gmail.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.