From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH] Plumb through xen-platform device logging Date: Thu, 11 Jul 2013 15:01:38 +0100 Message-ID: <1373551298.5453.196.camel@hastur.hellion.org.uk> References: <1372951983-28428-1-git-send-email-paul.durrant@citrix.com> <9AAE0902D5BC7E449B7C8E4E778ABCD006053C@LONPEX01CL01.citrite.net> <1373543014.5453.179.camel@hastur.hellion.org.uk> <9AAE0902D5BC7E449B7C8E4E778ABCD0060AA7@LONPEX01CL01.citrite.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD0060AA7@LONPEX01CL01.citrite.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Paul Durrant Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Thu, 2013-07-11 at 13:07 +0100, Paul Durrant wrote: > It doesn't change the fact though that, currently, xen builds of QEMU > don't configure any form of tracing backend at all which doesn't seem > particularly helpful, and I did introduce platform logging as an > example of an event to log so I think the patch is useful as far as it > goes, but maybe another patch to the platform device in QEMU would > also be considered a good idea. I think if we do anything we should do it properly (i.e. fix qemu to do sensible logging) rather than layering more stuff on top of the wrong thing. Ian.