From: Stefan Hajnoczi <stefanha@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Jagannathan Raman <jag.raman@oracle.com>,
qemu-devel@nongnu.org, elena.ufimtseva@oracle.com
Subject: Re: [PATCH v1 1/2] vfio-user: update comments
Date: Thu, 25 May 2023 13:59:07 -0400 [thread overview]
Message-ID: <20230525175907.GA132697@fedora> (raw)
In-Reply-To: <87fs7ko3o4.fsf@pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 2390 bytes --]
On Thu, May 25, 2023 at 05:02:03PM +0200, Markus Armbruster wrote:
> Jagannathan Raman <jag.raman@oracle.com> writes:
>
> > Clarify the behavior of TYPE_VFU_OBJECT when TYPE_REMOTE_MACHINE enables
> > the auto-shutdown property. Also, add notes to VFU_OBJECT_ERROR.
> >
> > Signed-off-by: Jagannathan Raman <jag.raman@oracle.com>
> > ---
> > hw/remote/vfio-user-obj.c | 14 +++++++++++---
> > 1 file changed, 11 insertions(+), 3 deletions(-)
> >
> > diff --git a/hw/remote/vfio-user-obj.c b/hw/remote/vfio-user-obj.c
> > index 88ffafc73e..8b10c32a3c 100644
> > --- a/hw/remote/vfio-user-obj.c
> > +++ b/hw/remote/vfio-user-obj.c
> > @@ -30,6 +30,11 @@
> > *
> > * notes - x-vfio-user-server could block IO and monitor during the
> > * initialization phase.
> > + *
> > + * When x-remote machine has the auto-shutdown property
> > + * enabled (default), x-vfio-user-server terminates after the last
> > + * client disconnects. Otherwise, it will continue running until
> > + * explicitly killed.
> > */
> >
> > #include "qemu/osdep.h"
> > @@ -61,9 +66,12 @@
> > OBJECT_DECLARE_TYPE(VfuObject, VfuObjectClass, VFU_OBJECT)
> >
> > /**
> > - * VFU_OBJECT_ERROR - reports an error message. If auto_shutdown
> > - * is set, it aborts the machine on error. Otherwise, it logs an
> > - * error message without aborting.
> > + * VFU_OBJECT_ERROR - reports an error message.
> > + *
> > + * If auto_shutdown is set, it aborts the machine on error. Otherwise,
> > + * it logs an error message without aborting. auto_shutdown is disabled
> > + * when the server serves clients from multiple VMs; as such, an error
> > + * from one VM shouldn't be able to disrupt other VM's services.
> > */
> > #define VFU_OBJECT_ERROR(o, fmt, ...) \
> > { \
>
> I still very much doubt an error can be severe enough to justify abort()
> in one configuration, yet harmless enough to permit carrying on in
> another configuration. But this patch merely documents what the code
> does, so
In both cases this vfio-user device is broken after the error occurs.
The difference in behavior is that in a multi-device server the other
devices should not be disrupted when one of them breaks.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-05-25 18:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 16:43 [PATCH v1 0/2] Fix the documentation for vfio-user and multi-process QEMU Jagannathan Raman
2023-05-17 16:43 ` [PATCH v1 1/2] vfio-user: update comments Jagannathan Raman
2023-05-25 15:02 ` Markus Armbruster
2023-05-25 17:59 ` Stefan Hajnoczi [this message]
2023-05-17 16:43 ` [PATCH v1 2/2] docs: fix multi-process QEMU documentation Jagannathan Raman
2023-05-25 15:02 ` Markus Armbruster
2023-05-25 17:59 ` [PATCH v1 0/2] Fix the documentation for vfio-user and multi-process QEMU Stefan Hajnoczi
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=20230525175907.GA132697@fedora \
--to=stefanha@redhat.com \
--cc=armbru@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.com \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).