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] megasas stops I/O when running kernel as dom0 under xen4

To: Andreas Olsowski <andreas.olsowski@xxxxxxxxxxx>
Subject: Re: [Xen-devel] megasas stops I/O when running kernel as dom0 under xen4.1/4.2
From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date: Mon, 22 Aug 2011 10:05:25 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 22 Aug 2011 02:07:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E4EA725.30405@xxxxxxxxxxx>
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: <4E43E04B.8010401@xxxxxxxxxxx> <20110811225119.GA3557@xxxxxxxxxxxx> <4E44EE51.70802@xxxxxxxxxxx> <201108151149.44053.simon.rowe@xxxxxxxxxxxxx> <4E4916A3.9070106@xxxxxxxxxxx> <4E4E56EE.2070801@xxxxxxxxxx> <4E4E705E.3040505@xxxxxxxxxxx> <4E4E79E8.3020808@xxxxxxxxxx> <4E4E913C.40809@xxxxxxxxxxx> <4E4E9423.8010904@xxxxxxxxxx> <4E4EA725.30405@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11
On 19/08/11 19:10, Andreas Olsowski wrote:
> Am 19.08.2011 18:49, schrieb Andrew Cooper:
>
> > The only change you need to make is in megasas_probe_one() in
> > megaraid_sas_base.c
> >
> > Add a call to pci_enable_msi(pdev) immediately after the current
> call to
> > pci_set_master(pdev);
> >
> > ~Andrew
> >
>
> Yep, that works fine. Removed the module option as well.
>
> root@tarballerina:~# cat /proc/interrupts  |grep mega
> 2236:      69010          0          0          0          0         
> 0          0          0  xen-pirq-msi       megasas
>
> The same procedure that would have lead to almost instant errors has
> not brought them to appear again.
>

Good.  This is what we are seeing as well.  I am still awaiting a reply
from LSI on this topic.

Unfortunately, this does point to a regression in the way Xen deals with
legacy interrupts.

-- 
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com


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

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