>>> On 13.02.15 at 19:09, <andrew.coop...@citrix.com> wrote: > On 13/02/15 18:03, Tamas K Lengyel wrote: >> On Fri, Feb 13, 2015 at 6:23 PM, Andrew Cooper >> <andrew.coop...@citrix.com> wrote: >>> On 13/02/15 16:33, Tamas K Lengyel wrote: >>>> v5: Style fixes >>>> Convert gfn to uint32_t >>> It is perfectly possible to have guests with more memory than is covered >>> by 44 bits, or PV guests whose frames reside above the 44bit boundary. >>> All gfn values should be 64bits wide. >>> >>> ~Andrew >> Internally Xen handles all gfn's as unsigned long's so depending on >> the compiler it may be only 32-bit wide. If gfn must be larger than >> 32-bit than we should use unsigned long long's within Xen. > > x86_32 Xen support was ripped out a while ago. For the time being all > unsigned longs are 64bit. > > With the arm32/64 split, there is a slow move in the direction of > paddr_t rather than unsigned long.
But (hopefully) not for GFNs. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
