All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Chun Yan Liu <cyliu@novell.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V3] Support logging xen-guest console
Date: Thu, 30 Jun 2011 13:18:54 +0200	[thread overview]
Message-ID: <4E0C5B9E.9070809@suse.de> (raw)
In-Reply-To: <201106301739.59597.cyliu@novell.com>

On 06/30/2011 11:39 AM, Chun Yan Liu wrote:
> On Thursday, June 30, 2011 03:58:57 PM Alexander Graf wrote:
>> On 30.06.2011, at 09:08, Chunyan Liu wrote:
>>> Add code to support logging xen-domU console, as what xenconsoled does.
>>> To enable logging, set environment variable XENCONSOLED_TRACE=guest and
>>> XENCONSOLED_LOGDIR=<specified directory>, log file will be saved in
>>> <specified directory>.
>> In fact, this whole thing looks as if you're merely trying to reimplement
>> "tee" on the xenconsole output. Wouldn't it make more sense to do this in
>> the char layer? So we could do:
>>
>>    -xenconsole tee:stdio,file:/tmp/xen.log
>>
>> or similar? That's probably a lot more useful than a random Xen specific
>> hack.
>>
> Thanks, Alex.  It IS something like "tee". But IMO, change in xen_console.c
> and change in char layer are just different time points, do not have essential
> difference. Change in xen_console.c is trying to backup output data into log
> file before sending to char device, change in char device is trying to
> dupicate data from char device to log file. Correct me if I'm wrong.

Sure, the outcome is the same though, no? We get the output data in both 
a file and the char backend.


Alex

  reply	other threads:[~2011-06-30 11:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30  7:08 [Qemu-devel] [PATCH V3] Support logging xen-guest console Chunyan Liu
2011-06-30  7:53 ` Alexander Graf
2011-06-30  7:58 ` Alexander Graf
2011-06-30  9:39   ` Chun Yan Liu
2011-06-30 11:18     ` Alexander Graf [this message]
2011-07-01  3:20       ` Chun Yan Liu
2011-07-01 18:00         ` Stefano Stabellini

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=4E0C5B9E.9070809@suse.de \
    --to=agraf@suse.de \
    --cc=cyliu@novell.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 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.