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>
Subject: Re: [Xen-devel][RFC]degradation on IPF due to hypercall set irq
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 22 Nov 2006 07:06:39 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 21 Nov 2006 23:06:49 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <51CFAB8CB6883745AE7B93B3E084EBE207DD4F@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+ptVHeNZ8fgAHbs2m
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 3:33 am, "Xu, Anthony" <anthony.xu@xxxxxxxxx> wrote:

> After moving from sharing PIC to hypercall set irq.
> KB on UP VTI domain incurs > 10% degradation.
> 
> The root cause is hypercall is very expensive on IPF side
> due to huge processor context.
> 
> I revert to sharing PIC in lastest Cset of IPF side,
> Then We can get performance back.

We may well have similar degradation on x86 too. The cause is lots of
unnecessary calls to the set_level hypercall (when the level hasn't actually
changed). Qemu *definitely* needs to keep shadow wire state and only notify
Xen on transitions. If the rate of hypercalls is still too high (which I
think is unlikely) we can use batching multicalls.

> I prepare to use shared IOSAPIC to deliver interrupt from
> Qemu to VTI domain.
> In IPF side, PIC is not needed,
> In the same time, we can assign more interrupt pins(24) to qemu.

I moved x86 away from this on purpose, to obtain a clean abstraction. I
don't think it's a good idea for ia64 to step backwards here.

 -- Keir



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