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

Re: [Xen-devel] Hypercall interface changes for PAE


On 31 May 2005, at 19:21, Keir Fraser wrote:

The downside of this approach is that the C declarations of mmu_update_t, update_va_mapping, etc are different on 32-bit PAE builds. But only low-level guest code will touch those interfaces anyway, and there is unlikely to be code sharing between PAE and non-PAE at that level.

What do you think?

Actually, we could export intpte_t and physaddr_t at the guest interface and declare mmu_update_t and friends in terms of those typedefs. This would also avoid needing different wrapper implementations of those hypercalls within Xen itself. Neat. :-)

 -- Keir


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