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] pciback for usb-controller and usb-storage on x86_64 end

To: Patrick Scharrenberg <pittipatti@xxxxxx>
Subject: Re: [Xen-devel] pciback for usb-controller and usb-storage on x86_64 ends in Oops
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 02 Nov 2006 11:26:23 +0000
Cc: Xen-Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 02 Nov 2006 13:51:45 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4549D2D3.5070008@xxxxxx>
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: Acb+cbni+IE3ZWpkEdusfgAX8io7RQ==
Thread-topic: [Xen-devel] pciback for usb-controller and usb-storage on x86_64 ends in Oops
User-agent: Microsoft-Entourage/11.2.5.060620
On 2/11/06 11:13, "Patrick Scharrenberg" <pittipatti@xxxxxx> wrote:

>> 
>> Is dma_ops == NULL at that point? If not, what value does it have?
>>   
> It is indeed NULL at that point and as far as I can see it's an issue of
> the fedora-kernel since there in arch/x86_64/mm/init-xen.c:mem_init()
> "pci_iommu_alloc()" is called instead of "no_iommu_init()"!
> I replaced pci_iommu_alloc() with the "pci_swiotlb_init()" /
> "no_iommu_init()"-block from xen-unstable and now it works!
> 
> The fedora init-xen.c looks very different to the one on your repository
> in many places, but I can't see if theses changes were intended or if
> it's just an older revision in the fedora-tree.

Most likely it's just a result of some dodgy forward porting from 2.6.16 to
2.6.18. We will upgrade our vanilla kernel version before 3.0.4 and it's
likely that vendors will sync with us when we do (or at least compare ports
for bugs).

Another 'fix' for the issue you saw, and maybe a good idea anyway if you
have 4GB or more of memory, is to put 'swiotlb=force,1' on your
driver-domain command line.

 -- Keir



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