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/
Home Products Support Community News


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

To: "Lin, Ray" <Ray.Lin@xxxxxxx>
Subject: Re: [Xen-devel] FW: Xen 4.1 interrupts not delievered.
From: Bruce Edge <bruce.edge@xxxxxxxxx>
Date: Mon, 18 Oct 2010 09:12:54 -0700
Cc: "jeremy@xxxxxxxx" <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "keir@xxxxxxx" <keir@xxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, "Ian.Campbell@xxxxxxxxxxxxx" <Ian.Campbell@xxxxxxxxxxxxx>, "linux@xxxxxxxxxxxxxx" <linux@xxxxxxxxxxxxxx>, "m.a.young@xxxxxxxxxxxx" <m.a.young@xxxxxxxxxxxx>
Delivery-date: Mon, 18 Oct 2010 09:14:27 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=msQ1M1VpnukdYdA48w1rITuP8mk3BOlZGaRkxNAZ/8A=; b=x4/Q6mbkhSYzSZUqyU6RZ7Ltlba08d9qMtRMXYJ3Wv/DLXcO7vMoADeYraaaHpVDKz eeTPlUygb7iqNfstWBKJbfzeCfrmherV4dg86tQuE+wns8KGsjEq1oMqpNMPP9eP8CB0 NpI5D66NM/gfB6R2wtI7Y/BeaHS3c4UJso+uc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=EcmnYfu6iwghxGonW6Q0FTpOT/ik4Z/ZW4vMO0ofXB8bkvgCHuwfDnjqRISqaNBI4N my5LBIgfwYv2JeyIijzHleTOq4Rhz/EsAb++OqdfTNaON7aPkQYx1WMdVGbUa2gk7Fjt UIai1pp6ZU+X50XlmJaaRPL2o39tZh21a6eW8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <EB4C61A1A2501842A04B573FE42B14D601319D0F0A@xxxxxxxxxxxxxxxxx>
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: <20101018145924.GA27373@xxxxxxxxxxxx> <EB4C61A1A2501842A04B573FE42B14D601319D0F0A@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, Oct 18, 2010 at 8:18 AM, Lin, Ray <Ray.Lin@xxxxxxx> wrote:
> The dom0/domU kernel also affect it.
> dom0 kernel :
> domU kernel :  2.6.36-rc6-pvops-kpcif-08
> -Ray
> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@xxxxxxxxxx]
> Sent: Monday, October 18, 2010 7:59 AM
> To: Lin, Ray
> Cc: bruce.edge@xxxxxxxxx; linux@xxxxxxxxxxxxxx; caker@xxxxxxxxxxxx; 
> xen-devel@xxxxxxxxxxxxxxxxxxx; keir@xxxxxxx; Ian.Campbell@xxxxxxxxxxxxx; 
> m.a.young@xxxxxxxxxxxx; jeremy@xxxxxxxx; pasik@xxxxxx
> Subject: Re: [Xen-devel] FW: Xen 4.1 interrupts not delievered.
> On Fri, Oct 15, 2010 at 02:57:44PM -0600, Lin, Ray wrote:
>>   We experienced the domU interrupt/DMA issue before. The symptom is like 
>> the /proc/interrupts/irq# of Tachyon chip (FC controller) keep on 
>> incrementing, but nobody is serving the interrupts. Eventually the count of 
>> these unserved interrupts reach the max. and are forced to be disabled. 
>>  With Konrad's dom0/domU configuration, this issue is resolved now.
> Can you send the old dom0/domU configuration? I am really curious as of why 
> it would work - the configuration for domU was just mostly made minimal to 
> boot a tiny kernel, and the dom0 was based on Ubuntu/Fedora Core 13 and then 
> enabling all of the Xen options.

More detail on Ray's kernel labels (These are from my build system)

> dom0 kernel :
This is xen/stable, with the attached config

> domU kernel :  2.6.36-rc6-pvops-kpcif-08
This is Konrad's stable/xen-pcifront-0.8.1 with the attached config

I've attached our working dom0 (config.stable-2.6.32.x_dom0_debug)
domU (config.konrad-pcifront_domU_debug) as well as our old
non-working config that was used for both dom0 and domU kernels
(config.debug) Not sure if you wanted that too or not.

In the config.debug that I wanted to use for dom0/domU I threw out all
drivers I didn't need, and made all the dom0'ish drivers modules so
they would not take up space in the domU runtime.


Attachment: config.stable-2.6.32.x_dom0_debug
Description: Binary data

Attachment: config.konrad-pcifront_domU_debug
Description: Binary data

Attachment: config.debug
Description: Binary data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>