WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] debug logging in windows

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, "Steven Smith" <steven.smith@xxxxxxxxxx>
Subject: RE: [Xen-devel] debug logging in windows
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Mon, 24 Nov 2008 09:39:31 +1100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 23 Nov 2008 14:40:09 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C54F2ED9.1F82B%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D0154FCA7@trantor> <C54F2ED9.1F82B%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AclFPG8nawy+9gREQg25GEk4k28qJQIKSgiAAAfJ5bYADdHD0A==
Thread-topic: [Xen-devel] debug logging in windows
> On 23/11/08 12:32, "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
wrote:
> 
> > The only change I'd like to make is one that I did in my own version
> > which is to keep separate log buffers per io port (with the intent
that
> > each DomU CPU writes to a different port), as I was finding the log
> > messages from different CPU's writing at the same time causing
garbled
> > messages. Synchronising access to the io port between different
drivers
> > in windows would require a heap of overhead.
> 
> Significant overhead compared with trapping to ioemu for every byte
> transmitted?
> 

Not so much performance overhead, but code overhead in terms of
providing a synchronisation mechanism between all the bits of code that
might actually write debug output. Under Linux it's easy enough to
export a global spinlock to everything, but it's not so easy under
Windows.

James

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel