qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Xu <dxu@dxuuu.xyz>
To: michael.roth@amd.com, kkostiuk@redhat.com
Cc: qemu-devel@nongnu.org, dxu@dxuuu.xyz
Subject: [PATCH 0/3] qga: Add optional `merge-output` flag to guest-exec QAPI
Date: Thu, 23 Feb 2023 19:05:12 -0700	[thread overview]
Message-ID: <cover.1677197937.git.dxu@dxuuu.xyz> (raw)

Currently, the captured output (via `capture-output`) is segregated into
separate GuestExecStatus fields (`out-data` and `err-data`). This means
that downstream consumers have no way to reassemble the captured data
back into the original stream.

This is relevant for chatty and semi-interactive (ie. read only) CLI
tools.  Such tools may deliberately interleave stdout and stderr for
visual effect. If segregated, the output becomes harder to visually
understand.

This patchset adds support for merging stderr and stdout output streams
via a new QAPI flag.

Daniel Xu (3):
  qga: test: Use absolute path to test data
  qga: Add optional `merge-output` flag to guest-exec qapi
  qga: test: Add tests for `merge-output` flag

 qga/commands.c        |  13 +++-
 qga/qapi-schema.json  |   6 +-
 tests/unit/test-qga.c | 135 ++++++++++++++++++++++++++++++++++++------
 3 files changed, 133 insertions(+), 21 deletions(-)

-- 
2.39.1



WARNING: multiple messages have this Message-ID (diff)
From: Daniel Xu <dxu@dxuuu.xyz>
To: Michael Roth <michael.roth@amd.com>,
	Konstantin Kostiuk <kkostiuk@redhat.com>,
	qemu-devel@nongnu.org
Subject: [PATCH 0/3] qga: Add optional `merge-output` flag to guest-exec QAPI
Date: Thu, 23 Feb 2023 17:21:29 -0700	[thread overview]
Message-ID: <cover.1677197937.git.dxu@dxuuu.xyz> (raw)
Message-ID: <20230224002129.YrkBkAsrO7KsjnHQTnsvq6tZO28xIKUiXYWrVtAi6Sw@z> (raw)

Currently, the captured output (via `capture-output`) is segregated into
separate GuestExecStatus fields (`out-data` and `err-data`). This means
that downstream consumers have no way to reassemble the captured data
back into the original stream.

This is relevant for chatty and semi-interactive (ie. read only) CLI
tools.  Such tools may deliberately interleave stdout and stderr for
visual effect. If segregated, the output becomes harder to visually
understand.

This patchset adds support for merging stderr and stdout output streams
via a new QAPI flag.

Daniel Xu (3):
  qga: test: Use absolute path to test data
  qga: Add optional `merge-output` flag to guest-exec qapi
  qga: test: Add tests for `merge-output` flag

 qga/commands.c        |  13 +++-
 qga/qapi-schema.json  |   6 +-
 tests/unit/test-qga.c | 135 ++++++++++++++++++++++++++++++++++++------
 3 files changed, 133 insertions(+), 21 deletions(-)

-- 
2.39.1



WARNING: multiple messages have this Message-ID (diff)
From: Daniel Xu <dxu@dxuuu.xyz>
To: michael.roth@amd.com, kkostiuk@redhat.com
Cc: qemu-devel@nongnu.org
Subject: [PATCH 0/3] qga: Add optional `merge-output` flag to guest-exec QAPI
Date: Thu, 23 Feb 2023 17:34:32 -0700	[thread overview]
Message-ID: <cover.1677197937.git.dxu@dxuuu.xyz> (raw)
Message-ID: <20230224003432.wA8vDTbzB-t61xSIMz4JiTFGnO35yYrQsgXL1s2cSRI@z> (raw)

Currently, the captured output (via `capture-output`) is segregated into
separate GuestExecStatus fields (`out-data` and `err-data`). This means
that downstream consumers have no way to reassemble the captured data
back into the original stream.

This is relevant for chatty and semi-interactive (ie. read only) CLI
tools.  Such tools may deliberately interleave stdout and stderr for
visual effect. If segregated, the output becomes harder to visually
understand.

This patchset adds support for merging stderr and stdout output streams
via a new QAPI flag.

Daniel Xu (3):
  qga: test: Use absolute path to test data
  qga: Add optional `merge-output` flag to guest-exec qapi
  qga: test: Add tests for `merge-output` flag

 qga/commands.c        |  13 +++-
 qga/qapi-schema.json  |   6 +-
 tests/unit/test-qga.c | 135 ++++++++++++++++++++++++++++++++++++------
 3 files changed, 133 insertions(+), 21 deletions(-)

-- 
2.39.1



             reply	other threads:[~2023-02-24  4:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24  2:05 Daniel Xu [this message]
2023-02-24  0:21 ` [PATCH 0/3] qga: Add optional `merge-output` flag to guest-exec QAPI Daniel Xu
2023-02-24  0:21 ` [PATCH 1/3] qga: test: Use absolute path to test data Daniel Xu
2023-02-24  0:34   ` Daniel Xu
2023-02-24  2:05   ` Daniel Xu
2023-02-27  8:16   ` Marc-André Lureau
2023-02-28  1:00     ` Daniel Xu
2023-02-24  0:34 ` [PATCH 0/3] qga: Add optional `merge-output` flag to guest-exec QAPI Daniel Xu
2023-02-24  0:34 ` [PATCH 3/3] qga: test: Add tests for `merge-output` flag Daniel Xu
2023-02-24  0:21   ` Daniel Xu
2023-02-24  2:05   ` Daniel Xu
2023-02-27  8:40   ` Marc-André Lureau
2023-02-28  1:36     ` Daniel Xu
2023-02-24  2:05 ` [PATCH 2/3] qga: Add optional `merge-output` flag to guest-exec qapi Daniel Xu
2023-02-24  0:21   ` Daniel Xu
2023-02-24  0:34   ` Daniel Xu
2023-02-27  8:22   ` Marc-André Lureau
2023-02-28  1:15     ` Daniel Xu
2023-02-28  8:18       ` Marc-André Lureau
2023-02-24  4:50 ` [PATCH 0/3] qga: Add optional `merge-output` flag to guest-exec QAPI Daniel Xu

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=cover.1677197937.git.dxu@dxuuu.xyz \
    --to=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 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).