All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Keir Fraser <keir.xen@gmail.com>,
	Daniel De Graaf <dgdegra@tycho.nsa.gov>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH v2] xen/console: buffer and show origin of guest PV writes
Date: Mon, 09 Sep 2013 13:48:32 +0100	[thread overview]
Message-ID: <522DDFC002000078000F17D2@nat28.tlf.novell.com> (raw)
In-Reply-To: <CE52FB76.5D124%keir.xen@gmail.com>

>>> On 09.09.13 at 13:13, Keir Fraser <keir.xen@gmail.com> wrote:
> On 16/08/2013 20:01, "Daniel De Graaf" <dgdegra@tycho.nsa.gov> 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.
>> 
>> Signed-off-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
> 
> This seems good, but, if we process and buffer dom0's output, we lose the
> possibility of running a terminal session in dom0 over the Xen console.
> Personally I do that quite a bit -- serial access only, get Xen's debugging
> there, but also can log in to dom0. Does noone else??

I use this only rarely; where possible I prefer using the normal
(VGA) console, and in most other cases ssh access to a remote
machine is available. But yes, I view this as an important feature
too, and simply failed to realize it would get broken by the change
here.

Jan

  parent reply	other threads:[~2013-09-09 12:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16 19:01 [PATCH v2] xen/console: buffer and show origin of guest PV writes Daniel De Graaf
2013-09-09 11:13 ` Keir Fraser
2013-09-09 12:13   ` Ian Campbell
2013-09-09 13:43     ` Keir Fraser
2013-09-09 13:46       ` Keir Fraser
2013-09-09 12:48   ` Jan Beulich [this message]
2013-09-09 13:46   ` Daniel De Graaf
2013-09-09 14:14     ` Keir Fraser

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=522DDFC002000078000F17D2@nat28.tlf.novell.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=keir.xen@gmail.com \
    --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.