All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Yuji Shimada <shimada-yxb@necst.nec.co.jp>,
	xen-devel@lists.xensource.com,
	Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com>,
	Kevin Wolf <kwolf@suse.de>
Subject: Re: [PATCH] Log qemu-dm's message with date, time and pid
Date: Thu, 26 Jun 2008 17:38:44 +0100	[thread overview]
Message-ID: <20080626163844.GW20952@redhat.com> (raw)
In-Reply-To: <18531.43971.119239.17511@mariner.uk.xensource.com>

On Thu, Jun 26, 2008 at 03:46:27PM +0100, Ian Jackson wrote:
> Yosuke Iwamatsu writes ("[Xen-devel] [PATCH] Log qemu-dm's message with date, time and pid"):
> > The qemu-dm's log message doesn't have date, time, and pid. It is
> > difficult to find out the message we want.
> 
> 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.
> 
> Also, I think I would discourage the introduction of new features in
> tools/ioemu.  I would much prefer submissions to be made against my
> new merged qemu tree, which you can currently find at
>  http://www.chiark.greenend.org.uk/~ijackson/qemu-xen.git

What are your plans wrt to QEMU longer term ?  Are you going to merge this
GIT repo into tools/ioemu in xen-unstable.hg, or thinking its better to
keep a separate tree on an ongoing basis ? Would we have synced up 
releases of the two, or try to apply some ABI stability to libxc and 
libxenstore APIs to allow separate release of QEMU vs XenD tools ? The
latter could be interesting because apps like Xenner are able to use
QEMU-DM in isolation from the rest of the XenD stack.

Regards,
Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  reply	other threads:[~2008-06-26 16:38 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 [this message]
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
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=20080626163844.GW20952@redhat.com \
    --to=berrange@redhat.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=kwolf@suse.de \
    --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.