]> xenbits.xensource.com Git - people/julieng/xen-unstable.git/commit
xen/mm: Clarify the granularity for each Frame Number
authorStefano Stabellini <stefano.stabellini@eu.citrix.com>
Fri, 24 Jul 2015 12:02:30 +0000 (13:02 +0100)
committerJulien Grall <julien.grall@citrix.com>
Thu, 17 Dec 2015 15:54:47 +0000 (15:54 +0000)
commit58f7ba12c09c84b84fe81dc46363fff41ce75655
tree33d4466d67bb8f022dab1875391d36607b9fc699
parentbe366f593b1786a16e71da2634587d73b33ecb06
xen/mm: Clarify the granularity for each Frame Number

ARM64 is able to support 64KB and 4KB page granularities. While the guest
will support both granularities, Xen and hypercall interface will always
be in 4KB.

Signed-off-by: Stefano Stabellini <stefano.stabellini@citrix.com>
Signed-off-by: Julien Grall <julien.grall@citrix.com>
---
Cc: Ian Campbell <ian.campbell@citrix.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Jan Beulich <jbeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>
Cc: Tim Deegan <tim@xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
I'm missing one term for Linux Frame Number but always in 4KB
granularity. It's necessary in few places such as the balloon code where
we need to map a Linux 4KB Frame Number into a Machine Frame Number.

I was thinking to name it xen_pfn.
xen/include/xen/mm.h