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

[Xen-devel] Re: Xen 4.1 interrupts not delievered.

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Bruce Edge <bruce.edge@xxxxxxxxx>, <Ray.Lin@xxxxxxx>, <linux@xxxxxxxxxxxxxx>, <caker@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, <m.a.young@xxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, <pasik@xxxxxx>
Subject: [Xen-devel] Re: Xen 4.1 interrupts not delievered.
From: Keir Fraser <keir@xxxxxxx>
Date: Wed, 13 Oct 2010 00:34:58 +0100
Cc:
Delivery-date: Tue, 12 Oct 2010 16:36:04 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:user-agent:date :subject:from:to:message-id:thread-topic:thread-index:in-reply-to :mime-version:content-type:content-transfer-encoding; bh=/tonbsxLC1FGc59xA/MGPKni4uqthpojNsQbZf24SvM=; b=OnDmSsnUp+IWbbGKzx9myAfk4aBX+AJ/i1rQm2eaoZ29fJLLkkaQnU5LQbKTFKdHpf ox3M+rkYNqH4+0+SPAKErOppschRobKqnoC3ZID6zXY0keXQFCaHbY2M2kt6hrOpYQJd +QHDWvNw35IMc104MeRLGLFgt3JAEjNPuiBGo=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=NSEooqGRhmMn3BVtUsEc/MgsjueZoEVTpPDkKHIpy+2Jb9qEmsgceAqI8Q06mHqIka d7daVbJ+1TgX9n88a6tiNHEdIp9NFjKJ2FMFW8cCaBnOzQEZeeMyLsnEjKcH4IesmnLQ Q+tdfixrezfSbR+lIiLqKg4w3/RtZtsIoEc8k=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20101012171745.GA27232@xxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: ActqZhTlAIXqZ/5kNESzhXMM69nbug==
Thread-topic: Xen 4.1 interrupts not delievered.
User-agent: Microsoft-Entourage/12.26.0.100708
On 12/10/2010 18:17, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx> wrote:

> A couple of that might fix the problems are:
> 
>  1). Ian's fix to the event channels:
> http://xenbits.xen.org/gitweb?p=people/ianc/linux-2.6.git;a=commit;h=5d30cb2a8
> 5912ffb5f6556d55472c26801eef2ea
>  2). Disable IRQ balancing in Xen (and also in Linux kernel). "noirqbalance"
>  3). Pin domains, but nothing to Domain 0.

ITYM cpu 0. Not that this should rightly make any difference that I can see.

My suspicion would be the per-CPU IDT patches introduced during 4.0
development. Or changes to enable deep C-state sleeps by default. One or the
other causing lost interrupts. I think the latter can be discounted by
max_cstate=1 as a Xen boot parameter. The former would require trying a
build of Xen before and after changesets 20072/20073 -- they are the ones
that did the heavy lifting to implement per-CPU IDTs.

 -- Keir

> But it might be worth trying them out?



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

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