From: Paolo Bonzini <pbonzini@redhat.com>
To: Wei Yang <richardw.yang@linux.intel.com>, qemu-devel@nongnu.org
Cc: armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH] vl: make sure char-pty message displayed by moving setbuf to the beginning
Date: Tue, 16 Jul 2019 09:27:29 +0200 [thread overview]
Message-ID: <e5169a0a-327a-df29-9a07-0055cd0a73f3@redhat.com> (raw)
In-Reply-To: <20190716072127.2000-1-richardw.yang@linux.intel.com>
On 16/07/19 09:21, Wei Yang wrote:
> Recently we found a behavior change after commit 6ade45f2ac93611
> ('char-pty: Print "char device redirected" message to stdout').
>
> When we redirect output to a file, the message "char device redirected
> to PTY_NAME (label LABEL)" would not be seen at the beginning of the
> file. Instead, the message is displayed after QEMU quit. This will block
> test automation.
>
> The reason is this message is printed after we set line buffer mode. So
> move this to the beginning.
>
> Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
> ---
> vl.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/vl.c b/vl.c
> index 5089fce6c5..a5808f9a02 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -2890,6 +2890,8 @@ int main(int argc, char **argv, char **envp)
> char *dir, **dirs;
> BlockdevOptionsQueue bdo_queue = QSIMPLEQ_HEAD_INITIALIZER(bdo_queue);
>
> + os_set_line_buffering();
> +
> error_init(argv[0]);
> module_call_init(MODULE_INIT_TRACE);
>
> @@ -4246,8 +4248,6 @@ int main(int argc, char **argv, char **envp)
> semihosting_arg_fallback(kernel_filename, kernel_cmdline);
> }
>
> - os_set_line_buffering();
> -
> /* spice needs the timers to be initialized by this point */
> qemu_spice_init();
>
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2019-07-16 7:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 7:21 [Qemu-devel] [PATCH] vl: make sure char-pty message displayed by moving setbuf to the beginning Wei Yang
2019-07-16 7:27 ` Paolo Bonzini [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=e5169a0a-327a-df29-9a07-0055cd0a73f3@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richardw.yang@linux.intel.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).