All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marc-André Lureau" <marcandre.lureau@gmail.com>
To: "Boeuf, Sebastien" <sebastien.boeuf@intel.com>,
	Markus Armbruster <armbru@redhat.com>
Cc: "stefanha@gmail.com" <stefanha@gmail.com>,
	"berrange@redhat.com" <berrange@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"stefanha@redhat.com" <stefanha@redhat.com>,
	"mst@redhat.com" <mst@redhat.com>
Subject: Re: [PATCH v2] docs: Update vhost-user spec regarding backend program conventions
Date: Wed, 11 Mar 2020 16:02:28 +0100	[thread overview]
Message-ID: <CAJ+F1CJhxQ9Gk15QUhbGV+HGdjr2-9DaR4C0Namw9jcSKwX96A@mail.gmail.com> (raw)
In-Reply-To: <717f4005879504627a0bff4dd55ec0e166dfeb88.camel@intel.com>

Hi

On Wed, Mar 11, 2020 at 3:19 PM Boeuf, Sebastien
<sebastien.boeuf@intel.com> wrote:
>
> Hi!
>
> On Fri, 2020-03-06 at 13:52 +0100, Marc-André Lureau wrote:
> > Hi
> >
> > On Fri, Mar 6, 2020 at 1:35 PM Stefan Hajnoczi <stefanha@gmail.com>
> > wrote:
> > > On Mon, Feb 24, 2020 at 07:24:54PM +0100, Sebastien Boeuf wrote:
> > > > The vhost-user specification is not clearly stating the expected
> > > > behavior from a backend program whenever the client disconnects.
> > > >
> > > > This patch addresses the issue by defining the default behavior
> > > > and
> > > > proposing an alternative through a command line option.
> > > >
> > > > By default, a backend program will terminate whenever the client
> > > > disconnects, unless told otherwise through the newly introduced
> > > > option --keep-listening.
> > > >
> > > > Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
> > > > Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> > > > ---
> > > >  docs/interop/vhost-user.rst | 12 ++++++++++++
> > > >  1 file changed, 12 insertions(+)
> > >
> > > Perhaps --keep-listening should be optional?
> >
> > I think it should be optional, and flagged by a capability.
>
> Could you please elaborate on that? How can I do that?

Some backend options or behavior are optional, and advertised through
--print-capabilities.

Say --foo (optional),

--print-capabilities should have something like:

{ ...
  "features": [
     "foo",
     ...
   ]
}

The list of capabilities is documented in vhost-user.json,
VHostUserBackendCapabilities.

We lack common enum such as @VHostUserBackendCommonFeature at this
point, but it can be added.

Although we don't currently parse this file through qapi, I don't know
how to express that
VHostUserBackendGPUFeature/VHostUserBackendCapabilitiesInput inherits
from another enum. Markus, any idea?



>
> Thanks,
> Sebastien
> >
> > > If the maintainers are happy with the patch as is then so am I:
> > >
> > > Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> >
> >
> ---------------------------------------------------------------------
> Intel Corporation SAS (French simplified joint stock company)
> Registered headquarters: "Les Montalets"- 2, rue de Paris,
> 92196 Meudon Cedex, France
> Registration Number:  302 456 199 R.C.S. NANTERRE
> Capital: 4,572,000 Euros
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.



-- 
Marc-André Lureau


      reply	other threads:[~2020-03-11 15:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24 18:24 [PATCH v2] docs: Update vhost-user spec regarding backend program conventions Sebastien Boeuf
2020-03-06 12:34 ` Stefan Hajnoczi
2020-03-06 12:52   ` Marc-André Lureau
2020-03-11 14:19     ` Boeuf, Sebastien
2020-03-11 15:02       ` Marc-André Lureau [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=CAJ+F1CJhxQ9Gk15QUhbGV+HGdjr2-9DaR4C0Namw9jcSKwX96A@mail.gmail.com \
    --to=marcandre.lureau@gmail.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sebastien.boeuf@intel.com \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.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.