Le Jeudi 05 Octobre 2006 14:03, Akio Takebe a écrit : > Hi, Isaku and Tristan > > Thank you for your comments. [...]
> >I think there are two right way. > >A avoid overlap somehow > > A.0 fake up ACPI table and assign pci somewhere. > > A.1 detect pci bridge > > To detect the region of pci bridge, it is necessary to parse > > ACPI table. But xen doesn't have such a ACPI parser. > > A.2 As a temporal work around, we can introduce xen boot option to > > indicate pci io area. > > A.3 assign RAM following the original MD. > > This might be easy. > > The current complete_dom0_memmap() seeks a gap and fill it > > with RAM. modify it so that it only assigns RAM only when > > a found gap is in baremetal's RAM. > >B modify ioremap hypercall and linux ioremap somehow > > to not use ram region. > > Probably Linux ioremap() wouldn't return __IA64_UNCACHED_OFFSET|offset > > so that iounmap() might need to be implemented. > >C don't give so much memory to dom0 > > The original motivation is to get modular vnif work. > > Now xencomm has been merged, this isn't an issue anymore. > > Akio, Is this right? > > Yes, you are right. > I have not tried to check modular vnif yet. > But I have checked it with cset 11635 + Tristan's xen-xcom-[a-c]3.diffs. > The results is good work. > > >Option C or A.3 is preferable. I don't think those are > >ery good, though. Any ideas? > > I also prefer A.3 to others. A.3 is definitly safe. Option B may be required for driver domains, unless we also follow the original MD in domU. Tristan. _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
