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][RFC]degradation on IPF due to hypercall set irq

To: "Xu, Anthony" <anthony.xu@xxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel][RFC]degradation on IPF due to hypercall set irq
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Wed, 22 Nov 2006 10:27:47 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 22 Nov 2006 02:27:59 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <51CFAB8CB6883745AE7B93B3E084EBE207DD55@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccN5wYmUmir46SdT8a+ptVHeNZ8fgAHbs2mAACOJaAAASp7iwAAG0VmAAB2zNAAAmxzrgAAEGDgAAAZWmIAAC5KoAAAk0fTAAD34HAAAGv3kg==
Thread-topic: [Xen-devel][RFC]degradation on IPF due to hypercall set irq
User-agent: Microsoft-Entourage/11.2.5.060620
On 22/11/06 10:23, "Xu, Anthony" <anthony.xu@xxxxxxxxx> wrote:

>> because it will require the shadow wire bitmap to be updated with
>> atomic accesses and the multicall state to be per-thread or to be
>> protected with a mutex. Each thread should flush multicall state
>> before it blocks.
> 
> I prefer atomic access, we used it in shared PIC.
> If each thread flush multicall seperately,
> There are some extra hypercalls.

Since the threads run independently there seems little choice but for each
to be able to flush. If the IDE DMA support had been properly integrated
into the qemu select() event loop this would not be an issue.

 -- Keir


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

<Prev in Thread] Current Thread [Next in Thread>