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] Permissive devices in Xen

To: Lukas Hejtmanek <xhejtman@xxxxxxxxxxx>
Subject: Re: [Xen-devel] Permissive devices in Xen
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Sun, 08 Jul 2007 11:10:12 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 08 Jul 2007 03:04:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070708100044.GX3885@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/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: AcfBSCvMaoDnti07EdyYRQAWy6hiGQ==
Thread-topic: [Xen-devel] Permissive devices in Xen
User-agent: Microsoft-Entourage/11.3.3.061214
On 8/7/07 11:00, "Lukas Hejtmanek" <xhejtman@xxxxxxxxxxx> wrote:

>> domU is not trusted to manage the i/o address space. We assume dom0 has set
>> up the values sanely and domU should have no reason to change them.
> 
> OK, I see. But there is problem with, e.g., InfiniBand card that during
> initialization performs reset of the card. The reset destroys the PCI config
> space therefore the driver reads 16 dwords from the config space and after
> reset, it writes them back. In DomU, it obviously does not restore address
> bars and the device fails to respond via MMIO.
> 
> So, I've tried to allow DomU (via pciback driver) to write also the address
> bars but in this case, I'm facing to huge SLAB corruptions. In Dom0 or non-Xen
> kernel, it works pretty well.
> 
> Do you have any hints how to track it down?

This was tracked down by Alex Williamson some time ago. There is code in
drivers/xen/pciback/conf_space_capability_pm.c:pm_ctrl_write() to restore
bars after a D3->D0 transition. I guess either your kernel does not have
that fix, or the fix needs to be extended slightly to cover whatever case
you are seeing.

 -- Keir


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