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-ia64-devel

Re: [Xen-ia64-devel] [PATCH][RFC][TAKE4] the P2M/VP patches

On Sun, Apr 09, 2006 at 09:43:07PM -0600, Alex Williamson wrote:

> > Maybe some special code for handling such a huge range is needed.
> 
>    Yes, for the short term we may be able to ignore this range, but we
> need a solution fairly soon as it's possible firmware or dom0 might
> choose to map cards into this MMIO space (this range is also descried in
> ACPI for dom0).  Identity mapping of the entire uncached address space
> for dom0 might be sufficient until we start on driver domains.  Thanks,


I have the following ideas. I think B. or C. might be good.
What do you think of them?

A. record a huge region to somewhere (maybe struct arch_domain) and
   add region check code to lookup_domian_mpa() (and its families)
   for special conversion on a huge region.

B. introduce a flag of super page for the P2M table.
   Then only a PGD (, PUD and PMD )page is needed to map such a huge page.
   Modify lookup_domain_mpa(), dom_fw_dom0_passthrough() and their families
   to be aware of super page flag.

C. Don't map MMIO range at domain creation. But map it when ioremap hypercall.
   Maybe only small portion of the range will be used.

D. other?

-- 
yamahata

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

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