From: Daniel De Graaf <dgdegra@tycho.nsa.gov>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Ian.Campbell@citrix.com, JBeulich@suse.com, xen-devel@lists.xen.org
Subject: Re: [PATCH RFC] xen/console: buffer and show origin of guest PV writes
Date: Tue, 13 Aug 2013 13:00:06 -0400 [thread overview]
Message-ID: <520A6616.2060808@tycho.nsa.gov> (raw)
In-Reply-To: <20130813164015.GE2924@reaktio.net>
On 08/13/2013 12:40 PM, Pasi Kärkkäinen wrote:
> On Tue, Aug 13, 2013 at 12:34:19PM -0400, Daniel De Graaf wrote:
>> Guests other than domain 0 using the console output have previously been
>> controlled by the VERBOSE define, but with no designation of which
>> guest's output was on the console. This patch converts the HVM output
>> buffering to be used by all domains, line buffering their output and
>> prefixing it with the domain ID. This is especially useful for debugging
>> stub domains during early boot.
>>
>> Signed-off-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
>>
>> ---
>>
>> A few questions for discussion (the reason this is an RFC):
>>
>> 1. HVM guests' output is currently limited to printable characters; do
>> we want to implement the same restriction on PV guests?
>>
>> 2. The prefix on the serial console for PV output is "(XEN) d5: ", while
>> HVM output is still "(XEN) HVM5: "; should these be made consistent?
>>
>> 3. Should we change to allowing console output by default, since it is
>> now controlled by log levels?
>>
>
> Also having timestamps before the log entries would be nice (like Linux has)..
>
> -- Pasi
Since this uses printk, if timestamps are turned on with opt_console_timestamps,
they will beadded to the output. It looks like the timestamp only has 1 second
resolution, unlike Linux - it might be useful to update that.
--
Daniel De Graaf
National Security Agency
next prev parent reply other threads:[~2013-08-13 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 16:34 [PATCH RFC] xen/console: buffer and show origin of guest PV writes Daniel De Graaf
2013-08-13 16:40 ` Pasi Kärkkäinen
2013-08-13 17:00 ` Daniel De Graaf [this message]
2013-08-13 16:52 ` Jan Beulich
2013-08-13 17:47 ` Daniel De Graaf
2013-08-14 9:16 ` Jan Beulich
2013-08-13 17:18 ` Andrew Cooper
2013-08-13 17:47 ` Daniel De Graaf
2013-08-14 10:03 ` Jan Beulich
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=520A6616.2060808@tycho.nsa.gov \
--to=dgdegra@tycho.nsa.gov \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xen.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.