From: Stefan Weil <weil@mail.berlios.de>
To: Peter Chubb <peter.chubb@nicta.com.au>
Cc: bernard.blackham@nicta.com.au, qemu-devel@nongnu.org,
philipo@ok-labs.com
Subject: Re: [Qemu-devel] [PATCH] Remove line buffering from log file
Date: Thu, 29 Sep 2011 06:47:39 +0200 [thread overview]
Message-ID: <4E83F86B.2020208@mail.berlios.de> (raw)
In-Reply-To: <w4wrcsysno.wl%peter@chubb.wattle.id.au>
Am 29.09.2011 04:43, schrieb Peter Chubb:
>
> This patch was originally written by Bernard Blackham, and modified by
> Peter Chubb.
>
> From 0d755af2f5bef22432da71f2fe0a9dce7d2882cd Mon Sep 17 00:00:00 2001
> From: Bernard Blackham <bernard.blackham@nicta.com.au>
> Date: Fri, 24 Jul 2009 13:38:03 +1000
> Subject: Disable line-based log buffering.
>
> There's no real reason for line-based buffering in log file output.
> If block buffering with a decent sized buffer is used, it can speed
> qemu up for -d all or -d exec significantly.
>
> The only thing you lose is that the last up to 4k of log output may be
> lost if
> qemu crashes.
That's the reason why line buffering is needed today.
I enable log file output to see what happened last before the crash.
It might be possible to use buffered output with a new function
qemu_abort() which replaces the existing calls of abort().
This function could call flush() for the log output before aborting.
In addition, SIGSEGV needs to be catched, and the signal handler
would have to call flush(), too (is that possible in signal handlers?).
Speed is not the primary target when somebody runs qemu -d ...
Kind regards,
Stefan Weil
next prev parent reply other threads:[~2011-09-29 4:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 2:43 [Qemu-devel] [PATCH] Remove line buffering from log file Peter Chubb
2011-09-29 4:47 ` Stefan Weil [this message]
2011-09-29 5:03 ` Peter Chubb
2011-09-29 7:57 ` Peter Maydell
2011-09-29 20:11 ` Blue Swirl
2011-09-29 21:26 ` Stefan Weil
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=4E83F86B.2020208@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=bernard.blackham@nicta.com.au \
--cc=peter.chubb@nicta.com.au \
--cc=philipo@ok-labs.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).