All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@suse.de>
To: Yuji Shimada <shimada-yxb@necst.nec.co.jp>
Cc: xen-devel@lists.xensource.com,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com>
Subject: Re: [PATCH] Log qemu-dm's message with date, time and pid
Date: Fri, 27 Jun 2008 11:10:55 +0200	[thread overview]
Message-ID: <4864AE9F.1070207@suse.de> (raw)
In-Reply-To: <20080627171727.A932.SHIMADA-YXB@necst.nec.co.jp>

Yuji Shimada schrieb:
> Ian Jackson wrote:
>> I agree with Kevin Wolf's comments.  But I would go further: why can
>> this not be done by the code in xend which starts qemu-dm ?  That
>> would avoid any change to the qemu code.

Right, that would be even better.

Or maybe as another option, introduce proper logging functions instead
of fprintf on stderr into (upstream) qemu. This would be the most work,
of course, but IMHO also the cleanest solution.

> I think that my implementation is more safety way because of the
> following reason.
> 
>   qemu-dm can easily restart ioemu-logger when ioemu-logger die.
>   And ioemu-logger death doesn't affected to guest software.

ioemu-logger is so simple that it would be a shame to see it crash anyway.

> In addition:
> 
>   We developed ioemu-logger without changing the codes which write
>   messages. This enables less changes of the codes in qemu-dm.

You could do the same from within qemu-dm or in xend.

Kevin

  reply	other threads:[~2008-06-27  9:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26  5:02 [PATCH] Log qemu-dm's message with date, time and pid Yosuke Iwamatsu
2008-06-26 11:20 ` Kevin Wolf
2008-06-26 14:46 ` Ian Jackson
2008-06-26 16:38   ` Daniel P. Berrange
2008-07-01 17:38     ` Ian Jackson
2008-07-01 18:10       ` Daniel P. Berrange
2008-07-01 20:06       ` John Levon
2008-07-02 10:26         ` Ian Jackson
2008-07-02 10:41           ` Daniel P. Berrange
2008-07-02 15:20             ` Brendan Cully
2008-06-27  8:19   ` Yuji Shimada
2008-06-27  9:10     ` Kevin Wolf [this message]
2008-06-27 13:40       ` Ian Jackson
2008-06-30  8:21         ` Yuji Shimada
2008-06-30  9:45           ` Kevin Wolf
2008-07-01  8:01             ` Yuji Shimada

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=4864AE9F.1070207@suse.de \
    --to=kwolf@suse.de \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=shimada-yxb@necst.nec.co.jp \
    --cc=xen-devel@lists.xensource.com \
    --cc=y-iwamatsu@ab.jp.nec.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 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.