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/
Home Products Support Community News


RE: [Xen-devel] Error getting mfn for PCI SR-IOV device?

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: RE: [Xen-devel] Error getting mfn for PCI SR-IOV device?
From: "Fischer, Anna" <anna.fischer@xxxxxx>
Date: Wed, 26 May 2010 11:15:12 +0000
Accept-language: en-US
Acceptlanguage: en-US
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 26 May 2010 04:18:08 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BFD0AD402000078000040CF@xxxxxxxxxxxxxxxxxx>
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: <0199E0D51A61344794750DC57738F58E70B14DD0D0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4BFCEA790200007800004046@xxxxxxxxxxxxxxxxxx> <0199E0D51A61344794750DC57738F58E70B14DD510@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4BFD0AD402000078000040CF@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acr8uMTc9Ng8pXs+S8CeZ1wWehgSuQAC3enQ
Thread-topic: [Xen-devel] Error getting mfn for PCI SR-IOV device?
> Subject: RE: [Xen-devel] Error getting mfn for PCI SR-IOV device?
> >>> On 26.05.10 at 11:19, "Fischer, Anna" <anna.fischer@xxxxxx> wrote:
> >>  Subject: Re: [Xen-devel] Error getting mfn for PCI SR-IOV device?
> >>
> >> >>> On 25.05.10 at 15:58, "Fischer, Anna" <anna.fischer@xxxxxx> wrote:
> >> > (XEN) mm.c:859:d0 Error getting mfn 40300 (pfn 5555555555555555)
> from
> >> L1
> >> > entry 8000000040300473 for l1e_owner=0, pg_owner=32753
> >> >...
> >> > entry 800000004037e473 for l1e_owner=0, pg_owner=32753
> >> > (XEN) mm.c:859:d0 Error getting mfn 4037f (pfn 5555555555555555)
> from
> >> L1
> >> > entry 800000004037f473 for l1e_owner=0, pg_owner=32753
> >> >
> >> > I boot Xen with 'dom0_mem=max:1024M iommu=0' set in GRUB. The
> system
> >> > supports VT-d, but I am disabling it.
> >>
> >> Would seem like the kernel assigns I/O memory space to the device,
> >> based on the physical (not machine) memory map it gets (making the
> >> assumption that there is RAM at 0x40000000 aka 1Gb). Does the
> >> behavior change if you remove the dom0_mem= option?
> >
> > Yes, thanks, I was going to post to the list that the problem is
> solved, and
> > the issue was that the PCI BARs were allocated > 1G while I was only
> making
> > 1024MB visible to Dom0. Now it works.
> But it's a kernel side bug nevertheless...

Yes, it should not allocate > 1G if Dom0 does not have access to that memory 
space. This runs the latest pv-ops kernel 
http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=summary from the 
xen/master branch.

It only happens for the SRIOV device when the kernel does PCI memory 
reassignment on boot. 


Xen-devel mailing list

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