[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] Plumb through xen-platform device logging


  • To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
  • From: Paul Durrant <Paul.Durrant@xxxxxxxxxx>
  • Date: Thu, 11 Jul 2013 14:49:40 +0000
  • Accept-language: en-GB, en-US
  • Cc: "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
  • Delivery-date: Thu, 11 Jul 2013 14:49:56 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: AQHOeMvNIzPGWv1t6U+7WoMZRNbgdplfLixAgAAnOACAABPhsIAAErIAgAAdcvA=
  • Thread-topic: [Xen-devel] [PATCH] Plumb through xen-platform device logging

> -----Original Message-----
> From: Ian Campbell [mailto:ian.campbell@xxxxxxxxxx]
> Sent: 11 July 2013 15:02
> To: Paul Durrant
> Cc: xen-devel@xxxxxxxxxxxxx
> Subject: Re: [Xen-devel] [PATCH] Plumb through xen-platform device logging
> 
> 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.
> 

Sure. I'll get together a patch to allow QEMU tracing to be configured in a xen 
build anyway, but then I'll do a QEMU patch to take a logfile parameter into 
the platform device model.

  Paul
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.