From: Markus Armbruster <armbru@redhat.com>
To: Jagannathan Raman <jag.raman@oracle.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com, elena.ufimtseva@oracle.com
Subject: Re: [PATCH v1 1/2] vfio-user: update comments
Date: Thu, 25 May 2023 17:02:03 +0200 [thread overview]
Message-ID: <87fs7ko3o4.fsf@pond.sub.org> (raw)
In-Reply-To: <7340a298bcda0268b3decdd772ebce84bfcedcd5.1684338236.git.jag.raman@oracle.com> (Jagannathan Raman's message of "Wed, 17 May 2023 16:43:56 +0000")
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
Reviewed-by: Markus Armbruster <armbru@redhat.com>
next prev parent reply other threads:[~2023-05-25 15:03 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 [this message]
2023-05-25 17:59 ` Stefan Hajnoczi
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=87fs7ko3o4.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.com \
--cc=qemu-devel@nongnu.org \
--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 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).