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: [ofa-general] MTHCA driver for Linux

To: Roland Dreier <rdreier@xxxxxxxxx>
Subject: [Xen-devel] Re: [ofa-general] MTHCA driver for Linux
From: Lukas Hejtmanek <xhejtman@xxxxxxxxxxx>
Date: Fri, 18 Jan 2008 23:50:58 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, general@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 18 Jan 2008 14:51:49 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <adalk6mx194.fsf@xxxxxxxxx>
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>
References: <20080118170117.GH4136@xxxxxxxxxxx> <adatzlax45r.fsf@xxxxxxxxx> <20080118204834.GI4136@xxxxxxxxxxx> <adalk6mx194.fsf@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.17 (2007-11-01)
On Fri, Jan 18, 2008 at 01:38:47PM -0800, Roland Dreier wrote:
> I'm not sure I'm understanding what you're saying.  Do you mean that
> you've found a bug in the Xen pci front-end, or do you still think we
> should fix this by changing the mthca driver?

I'm not sure where exactly the bug is.

The bug is triggered by Xen PCI front-end driver in DomU.

The workaround is to either rmmod mthca driver or merge .shutdown and .remove
sections of the mthca driver (in the module that runs in DomU kernel).

I'm not sure where the bug is as the driver should leave the device in correct
state. The current Linux kernel does not do that for most devices.

Similar problem was with e1000 driver. If the driver was not removed before
reboot, the system froze in BIOS code. This one was fixed in the BIOS of
motherboard. But I believe, the drivers should not leave the device as is.

Maybe people from Xen could write their opinion  what should be done here.

-- 
Lukáš Hejtmánek

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

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