Re: [Xen-devel] BUG: bad page map under Xen

[Konrad Rzeszutek Wilk <konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>]

On Mon, Oct 21, 2013 at 03:27:50PM +0100, Jan Beulich wrote:
> >>> On 21.10.13 at 16:18, Konrad Rzeszutek Wilk <konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org> wrote:
> > On Mon, Oct 21, 2013 at 04:06:07PM +0200, Lukas Hejtmanek wrote:
> >>         Region 2: Memory at 380fff000000 (64-bit, prefetchable) [size=8M]
> >...
> > --- a/arch/x86/xen/setup.c
> > +++ b/arch/x86/xen/setup.c
> > @@ -92,6 +92,9 @@ static void __init xen_add_extra_mem(u64 start, u64 size)
> >  
> >                 __set_phys_to_machine(pfn, INVALID_P2M_ENTRY);
> >         }
> > +       /* Anything past the balloon area is marked as identity. */
> > +       for (pfn = xen_max_p2m_pfn; pfn < MAX_DOMAIN_PAGES; pfn++)
> > +               __set_phys_to_machine(pfn, IDENTITY_FRAME(pfn));
> 
> Hardly - MAX_DOMAIN_PAGES derives from
> CONFIG_XEN_MAX_DOMAIN_MEMORY, which in turn is unrelated
> to where MMIO might be. Should you perhaps simply start from

Looks like your mailer ate some words.

> an all 1:1 mapping, inserting the RAM translations as you find
> them?


Yeah, as this code can be called for the regions under 4GB. Definitly
needs more analysis.

Were you suggesting a lookup when we scan the PCI devices? (xen_add_device)?

> 
> Jan
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html