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] pci-passthrough not working on 4.0.1-rc1-pre: mm.c:3847:

To: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] pci-passthrough not working on 4.0.1-rc1-pre: mm.c:3847:d10 Bad page 00000000001beab4: ed=ffff830151210000(10), sd=ffff830151210000, caf=8000000000000002, taf=7400000000000001
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Thu, 22 Apr 2010 14:57:47 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 22 Apr 2010 12:00:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1365246793.20100421234440@xxxxxxxxxxxxxx>
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: <1497488369.20100419164714@xxxxxxxxxxxxxx> <20100419155936.GA11619@xxxxxxxxxxxxxxxxxxx> <103758397.20100419181342@xxxxxxxxxxxxxx> <20100419162736.GA9988@xxxxxxxxxxxxxxxxxxx> <1144401458.20100419190923@xxxxxxxxxxxxxx> <1934472801.20100419192319@xxxxxxxxxxxxxx> <20100419182839.GA8349@xxxxxxxxxxxxxxxxxxx> <1538293002.20100421155829@xxxxxxxxxxxxxx> <20100421150202.GA6906@xxxxxxxxxxxxxxxxxxx> <1365246793.20100421234440@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
On Wed, Apr 21, 2010 at 11:44:40PM +0200, Sander Eikelenboom wrote:
> For the fun of it, with the 2.6.33 and pvgrub
> with kernel line iommu=soft of iommu=1 it fails to boot (no output from a 
> kernel booting)
> with kernel line iommu=off .. it boots fine.
> 
> Does something in the regular kernel around the iommu stuff get run that 
> early in the boot that if it fails it doesn't give output, and could that be 
> triggered by the handing over from mini-os to the actual kernel ?

Not around the code that handles the 'iommu=' stuff. It just sets a
variable (swiotlb in this case) to 1 if 'soft' is specified.


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

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