> To be able to add the PAE specific changes, we need to settle on a
> #define for ifdefing around them in the core Xen code.
>
> What about CONFIG_PAE? We could add this to asm-x86/config.h if pae=y
> is passed in on the make line (via Rules.mk)
CONFIG_PAE seems reasonable.
> New parallel files vs. ifdef existing files:
>
> Has anyone settled on if the PAE code is going into the files under
> xen/arch/x86/x86_32, using #ifdef''s for PAE, or are you
> planning to add
> a parallel directory to x86_32 and x86_64 under xen/arch?
Most of the changes can be hidden in header files. There should be no
need for extra c files.
> Same question for headers. Are you adding the 3-level page tables to
> the existing include/asm-x86/x86_32/page.h using #ifdef''s or
adding a
> new directory parallel to x86_32 and x86_64 which would have a new
> page.h, etc?
Having a separate 2 and 3 level file that is conditionally included by
x86_32/page.h would seem to be the best approach.
Ian
-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content.
Register
by 3/29 & save $300
http://ads.osdn.com/?ad_idh83&alloc_id149&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel