Re: [Xen-devel] [PATCH 17/17] PVH xen: PVH dom0 creation....

[Mukesh Rathor <mukesh.rathor@xxxxxxxxxx>]

On Fri, 26 Apr 2013 08:22:08 +0100
"Jan Beulich" <JBeulich@xxxxxxxx> wrote:

> >>> On 26.04.13 at 03:18, Mukesh Rathor <mukesh.rathor@xxxxxxxxxx>
> >>> wrote:
> > On Wed, 24 Apr 2013 10:28:35 +0100
> > "Jan Beulich" <JBeulich@xxxxxxxx> wrote:
> > 
> >> >>> On 23.04.13 at 23:26, Mukesh Rathor <mukesh.rathor@xxxxxxxxxx>
> >> >>> wrote:
> >> > +    /* If the e820 ended under 4GB, we must map the remaining
> >> > space upto 4GB */
> >> > +    if ( end < GB(4) )
> >> > +    {
> >> > +        start_pfn = PFN_UP(end);
> >> > +        end_pfn = (GB(4)) >> PAGE_SHIFT;
> >> > +        nump = end_pfn - start_pfn;
> >> > +        rc = domctl_memory_mapping(d, start_pfn, start_pfn,
> >> > nump, 1);
> >> > +        BUG_ON(rc);
> >> > +    }
> >> 
> >> That's necessary, but not sufficient. Or did I overlook MMIO ranges
> >> getting added somewhere else for Dom0, when they sit above the
> >> highest E820 covered address?
> > 
> > construct_dom0() adds the entire range:
> > 
> >     /* DOM0 is permitted full I/O capabilities. */
> >     rc |= ioports_permit_access(dom0, 0, 0xFFFF);
> >     rc |= iomem_permit_access(dom0, 0UL, ~0UL);
> 
> Which does not create any mappings at all - these are just
> permissions being granted.

Right. I'm not sure where its happening for dom0.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel