All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: michael.roth@amd.com,  kkostiuk@redhat.com,  berrange@redhat.com,
	qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] qapi: qga: Clarify when out-data and err-data are populated
Date: Fri, 13 Oct 2023 15:26:31 +0200	[thread overview]
Message-ID: <87fs2efybc.fsf@pond.sub.org> (raw)
In-Reply-To: <935735389830bbe8407d95ebf89632792bf11a30.1696185261.git.dxu@dxuuu.xyz> (Daniel Xu's message of "Sun, 1 Oct 2023 12:38:26 -0600")

Daniel Xu <dxu@dxuuu.xyz> writes:

> If output is being captured for a guest-exec invocation, the out-data
> and err-data fields of guest-exec-status are only populated after the
> process is reaped. This is somewhat counter intuitive and too late to
> change. Thus, it would be good to document the behavior.
>
> Signed-off-by: Daniel Xu <dxu@dxuuu.xyz>
> ---
>  qga/qapi-schema.json | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/qga/qapi-schema.json b/qga/qapi-schema.json
> index b720dd4379..876e2a8ea8 100644
> --- a/qga/qapi-schema.json
> +++ b/qga/qapi-schema.json
> @@ -1220,11 +1220,13 @@
>  # @signal: signal number (linux) or unhandled exception code (windows)
>  #     if the process was abnormally terminated.
>  #
> -# @out-data: base64-encoded stdout of the process
> +# @out-data: base64-encoded stdout of the process. This field will only
> +#     be populated after the process exits.
>  #
> -# @err-data: base64-encoded stderr of the process Note: @out-data and
> +# @err-data: base64-encoded stderr of the process. Note: @out-data and
>  #     @err-data are present only if 'capture-output' was specified for
> -#     'guest-exec'
> +#     'guest-exec'. This field will only be populated after the process
> +#     exits.
>  #
>  # @out-truncated: true if stdout was not fully captured due to size
>  #     limitation.

Two spaces between sentences for consistency, please.

With that:
Acked-by: Markus Armbruster <armbru@redhat.com>



  parent reply	other threads:[~2023-10-13 13:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-01 18:38 [PATCH 0/2] Small fixes for qga Daniel Xu
2023-10-01 18:38 ` [PATCH 1/2] qga: Fix memory leak when output stream is unused Daniel Xu
2023-10-01 18:38 ` [PATCH 2/2] qapi: qga: Clarify when out-data and err-data are populated Daniel Xu
2023-10-01 19:18   ` Konstantin Kostiuk
2023-10-13 13:26   ` Markus Armbruster [this message]
2023-10-13 16:43 ` [PATCH 0/2] Small fixes for qga Konstantin Kostiuk

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=87fs2efybc.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dxu@dxuuu.xyz \
    --cc=kkostiuk@redhat.com \
    --cc=michael.roth@amd.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 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.