xen: support 52 bit physical addresses in pv guests
Subsystems (2)
Juergen Gross
maintainerPATCH 1/1 xen: support 52 bit physical addresses in pv guests
Physical addresses on processors supporting 5 level paging can be up to 52 bits wide. For a Xen pv guest running on such a machine those physical addresses have to be supported in order to be able to use any memory on the machine even if the guest itself does not support 5 level paging.
So when reading/writing a MFN from/to a pte don't use the kernel's PTE_PFN_MASK but a new XEN_PTE_MFN_MASK allowing full 40 bit wide MFNs.
--- arch/x86/include/asm/xen/page.h | 11 ++++++++++- arch/x86/xen/mmu_pv.c | 4 ++-- 2 files changed, 12 insertions(+), 3 deletions(-)
arch/x86/include/asm/xen/page.h +10 -1
@@ -26,6 +26,15 @@ typedef struct xpaddr {phys_addr_t paddr; } xpaddr_t; +#ifdef CONFIG_X86_64 +#define XEN_PHYSICAL_MASK ((1UL << 52) - 1) +#else +#define XEN_PHYSICAL_MASK __PHYSICAL_MASK +#endif + +#define XEN_PTE_MFN_MASK ((pteval_t)(((signed long)PAGE_MASK) & \ + XEN_PHYSICAL_MASK)) +#define XMADDR (x) ((xmaddr_t) { .maddr = (x) })#define XPADDR (x) ((xpaddr_t) { .paddr = (x) })
@@ -277,7 +286,7 @@ static inline unsigned long bfn_to_local_pfn(unsigned long mfn)static inline unsigned long pte_mfn (pte_t pte) { -return (pte.pte &PTE_PFN_MASK ) >>PAGE_SHIFT ; +return (pte.pte &XEN_PTE_MFN_MASK ) >>PAGE_SHIFT ; }static inline pte_t mfn_pte (unsigned long page_nr,pgprot_t pgprot)
arch/x86/xen/mmu_pv.c +2 -2
@@ -315,7 +315,7 @@ void xen_ptep_modify_prot_commit(struct mm_struct *mm, unsigned long addr,static pteval_t pte_mfn_to_pfn (pteval_t val) {if (val & _PAGE_PRESENT) { -unsigned long mfn = (val &PTE_PFN_MASK ) >>PAGE_SHIFT ; +unsigned long mfn = (val &XEN_PTE_MFN_MASK ) >>PAGE_SHIFT ;unsigned long pfn =mfn_to_pfn (mfn);pteval_t flags = val &PTE_FLAGS_MASK ;
@@ -1740,7 +1740,7 @@ static unsigned long __init m2p(phys_addr_t maddr) {phys_addr_t paddr; - maddr &=PTE_PFN_MASK ; + maddr &=XEN_PTE_MFN_MASK ; paddr =mfn_to_pfn (maddr >>PAGE_SHIFT ) <<PAGE_SHIFT ;return paddr;
Signature · 1 line
2.12.3
Boris Ostrovsky
reviewerQuoted 8 lines · Juergen Gross
Physical addresses on processors supporting 5 level paging can be up to 52 bits wide. For a Xen pv guest running on such a machine those physical addresses have to be supported in order to be able to use any memory on the machine even if the guest itself does not support 5 level paging.
So when reading/writing a MFN from/to a pte don't use the kernel's
PTE_PFN_MASKbut a newXEN_PTE_MFN_MASKallowing full 40 bit wide MFNs.
full 52 bits?
Quoted 12 lines
Signed-off-by Juergen Gross <[email protected]>--- arch/x86/include/asm/xen/page.h | 11 ++++++++++- arch/x86/xen/mmu_pv.c | 4 ++-- 2 files changed, 12 insertions(+), 3 deletions(-)arch/x86/include/asm/xen/page.h +0
-0
arch/x86/include/asm/xen/page.h typedef struct xpaddr { · line 30
Quoted 5 lines
arch/x86/include/asm/xen/page.h +2
-0@@ -26,6 +26,15 @@ typedef struct xpaddr {phys_addr_t paddr; } xpaddr_t; +#ifdef CONFIG_X86_64 +#define XEN_PHYSICAL_MASK ((1UL << 52) - 1)
SME is not supported for PV guests but for consistency (and in case sme bit somehow gets set)
#define XEN_PHYSICAL_MASK __sme_clr(((1UL << 52) - 1))
But the real question that I have is whether this patch is sufficient. We are trying to preserve more bits in mfn but then this mfn is used, say, in pte_pfn_to_mfn() to build a pte. Can we be sure that the pte won't be stripped of higher bits in native code (again, as an example, native_make_pte()) because we are compiled with 5LEVEL?
-boris
Quoted 34 lines
arch/x86/include/asm/xen/page.h +8
-1+#else +#define XEN_PHYSICAL_MASK __PHYSICAL_MASK +#endif + +#define XEN_PTE_MFN_MASK ((pteval_t)(((signed long)PAGE_MASK) & \ + XEN_PHYSICAL_MASK)) +#define XMADDR (x) ((xmaddr_t) { .maddr = (x) })#define XPADDR (x) ((xpaddr_t) { .paddr = (x) })@@ -277,7 +286,7 @@ static inline unsigned long bfn_to_local_pfn(unsigned long mfn)static inline unsigned long pte_mfn (pte_t pte) { -return (pte.pte &PTE_PFN_MASK ) >>PAGE_SHIFT ; +return (pte.pte &XEN_PTE_MFN_MASK ) >>PAGE_SHIFT ; }static inline pte_t mfn_pte (unsigned long page_nr,pgprot_t pgprot)arch/x86/xen/mmu_pv.c +1
-1@@ -315,7 +315,7 @@ void xen_ptep_modify_prot_commit(struct mm_struct *mm, unsigned long addr,static pteval_t pte_mfn_to_pfn (pteval_t val) {if (val & _PAGE_PRESENT) { -unsigned long mfn = (val &PTE_PFN_MASK ) >>PAGE_SHIFT ; +unsigned long mfn = (val &XEN_PTE_MFN_MASK ) >>PAGE_SHIFT ;unsigned long pfn =mfn_to_pfn (mfn);pteval_t flags = val &PTE_FLAGS_MASK ;
arch/x86/xen/mmu_pv.c static unsigned long __init m2p(phys_addr_t maddr) · line 1746
Quoted 8 lines
arch/x86/xen/mmu_pv.c +1
-1@@ -1740,7 +1740,7 @@ static unsigned long __init m2p(phys_addr_t maddr) {phys_addr_t paddr; - maddr &=PTE_PFN_MASK ; + maddr &=XEN_PTE_MFN_MASK ; paddr =mfn_to_pfn (maddr >>PAGE_SHIFT ) <<PAGE_SHIFT ;return paddr;
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xen.org/xen-devel
Boris Ostrovsky
reviewerQuoted 8 lines · Juergen Gross
Physical addresses on processors supporting 5 level paging can be up to 52 bits wide. For a Xen pv guest running on such a machine those physical addresses have to be supported in order to be able to use any memory on the machine even if the guest itself does not support 5 level paging.
So when reading/writing a MFN from/to a pte don't use the kernel's
PTE_PFN_MASKbut a newXEN_PTE_MFN_MASKallowing full 40 bit wide MFNs.
full 52 bits?
Quoted 12 lines
Signed-off-by Juergen Gross <[email protected]>--- arch/x86/include/asm/xen/page.h | 11 ++++++++++- arch/x86/xen/mmu_pv.c | 4 ++-- 2 files changed, 12 insertions(+), 3 deletions(-)arch/x86/include/asm/xen/page.h +0
-0
arch/x86/include/asm/xen/page.h typedef struct xpaddr { · line 30
Quoted 5 lines
arch/x86/include/asm/xen/page.h +2
-0@@ -26,6 +26,15 @@ typedef struct xpaddr {phys_addr_t paddr; } xpaddr_t; +#ifdef CONFIG_X86_64 +#define XEN_PHYSICAL_MASK ((1UL << 52) - 1)
SME is not supported for PV guests but for consistency (and in case sme bit somehow gets set)
#define XEN_PHYSICAL_MASK __sme_clr(((1UL << 52) - 1))
But the real question that I have is whether this patch is sufficient. We are trying to preserve more bits in mfn but then this mfn is used, say, in pte_pfn_to_mfn() to build a pte. Can we be sure that the pte won't be stripped of higher bits in native code (again, as an example, native_make_pte()) because we are compiled with 5LEVEL?
-boris
Quoted 42 lines
arch/x86/include/asm/xen/page.h +8
-1+#else +#define XEN_PHYSICAL_MASK __PHYSICAL_MASK +#endif + +#define XEN_PTE_MFN_MASK ((pteval_t)(((signed long)PAGE_MASK) & \ + XEN_PHYSICAL_MASK)) +#define XMADDR (x) ((xmaddr_t) { .maddr = (x) })#define XPADDR (x) ((xpaddr_t) { .paddr = (x) })@@ -277,7 +286,7 @@ static inline unsigned long bfn_to_local_pfn(unsigned long mfn)static inline unsigned long pte_mfn (pte_t pte) { -return (pte.pte &PTE_PFN_MASK ) >>PAGE_SHIFT ; +return (pte.pte &XEN_PTE_MFN_MASK ) >>PAGE_SHIFT ; }static inline pte_t mfn_pte (unsigned long page_nr,pgprot_t pgprot)arch/x86/xen/mmu_pv.c +2
-2@@ -315,7 +315,7 @@ void xen_ptep_modify_prot_commit(struct mm_struct *mm, unsigned long addr,static pteval_t pte_mfn_to_pfn (pteval_t val) {if (val & _PAGE_PRESENT) { -unsigned long mfn = (val &PTE_PFN_MASK ) >>PAGE_SHIFT ; +unsigned long mfn = (val &XEN_PTE_MFN_MASK ) >>PAGE_SHIFT ;unsigned long pfn =mfn_to_pfn (mfn);pteval_t flags = val &PTE_FLAGS_MASK ;@@ -1740,7 +1740,7 @@ static unsigned long __init m2p(phys_addr_t maddr) {phys_addr_t paddr; - maddr &=PTE_PFN_MASK ; + maddr &=XEN_PTE_MFN_MASK ; paddr =mfn_to_pfn (maddr >>PAGE_SHIFT ) <<PAGE_SHIFT ;return paddr;
Juergen Gross
maintainerQuoted 9 lines · Boris Ostrovsky
Quoted 6 lines · Juergen Gross
Physical addresses on processors supporting 5 level paging can be up to 52 bits wide. For a Xen pv guest running on such a machine those physical addresses have to be supported in order to be able to use any memory on the machine even if the guest itself does not support 5 level paging.
Quoted 4 lines
Quoted 2 lines
So when reading/writing a MFN from/to a pte don't use the kernel's
PTE_PFN_MASKbut a newXEN_PTE_MFN_MASKallowing full 40 bit wide MFNs.full 52 bits?
The MFN mask is only 40 bits. This plus the 12 bits page offset are 52 bits of machine address width.
Quoted 8 lines
Quoted 8 lines
Signed-off-by Juergen Gross <[email protected]>---
arch/x86/include/asm/xen/page.h| 11 ++++++++++- arch/x86/xen/mmu_pv.c | 4 ++--2 files changed, 12 insertions(+), 3 deletions(-)
Quoted 15 lines
Quoted 10 lines
arch/x86/include/asm/xen/page.h +0
-0@@ -26,6 +26,15 @@ typedef struct xpaddr { phys_addr_t paddr; } xpaddr_t;+#ifdef
CONFIG_X86_64
+#define XEN_PHYSICAL_MASK ((1UL << 52) - 1)SME is not supported for PV guests but for consistency (and in case sme bit somehow gets set)
#define XEN_PHYSICAL_MASK__sme_clr(((1UL << 52) - 1))
Hmm, really? Shouldn't we rather add something like
BUG_ON(sme_active());
somewhere?
Quoted 5 lines
But the real question that I have is whether this patch is sufficient. We are trying to preserve more bits in mfn but then this mfn is used, say, in
pte_pfn_to_mfn()to build a pte. Can we be sure that the pte won't be stripped of higher bits in native code (again, as an example,native_make_pte()) because we are compiled with 5LEVEL?
native_make_pte() just encapsulates pte_t. It doesn't modify the value of the pte at all.
Physical address bits are only ever masked away via PTE_PFN_MASK and I haven't found any place where it is used for a MFN other than those I touched in this patch.
Juergen
Boris Ostrovsky
reviewerQuoted 10 lines · Juergen Gross
Quoted 9 lines · Boris Ostrovsky
Quoted 6 lines · Juergen Gross
Physical addresses on processors supporting 5 level paging can be up to 52 bits wide. For a Xen pv guest running on such a machine those physical addresses have to be supported in order to be able to use any memory on the machine even if the guest itself does not support 5 level paging.
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
So when reading/writing a MFN from/to a pte don't use the kernel's
PTE_PFN_MASKbut a newXEN_PTE_MFN_MASKallowing full 40 bit wide MFNs.full 52 bits?
The MFN mask is only 40 bits. This plus the 12 bits page offset are 52 bits of machine address width.
Oh, right --- frames, not addresses.
Quoted 25 lines
Quoted 9 lines
Quoted 9 lines
Signed-off-by Juergen Gross <[email protected]>--- arch/x86/include/asm/xen/page.h | 11 ++++++++++- arch/x86/xen/mmu_pv.c | 4 ++-- 2 files changed, 12 insertions(+), 3 deletions(-)Quoted 15 lines
arch/x86/include/asm/xen/page.h typedef struct xpaddr { · line 29
Quoted 10 lines
arch/x86/include/asm/xen/page.h +1
-0@@ -26,6 +26,15 @@ typedef struct xpaddr { phys_addr_t paddr; } xpaddr_t; +#ifdef CONFIG_X86_64 +#define XEN_PHYSICAL_MASK ((1UL << 52) - 1)SME is not supported for PV guests but for consistency (and in case sme bit somehow gets set)
#define XEN_PHYSICAL_MASK__sme_clr(((1UL << 52) - 1))
Quoted 5 lines
Hmm, really? Shouldn't we rather add something like
BUG_ON(sme_active());
somewhere?
We can do that too.
Quoted 9 lines
Quoted 6 lines
But the real question that I have is whether this patch is sufficient. We are trying to preserve more bits in mfn but then this mfn is used, say, in
pte_pfn_to_mfn()to build a pte. Can we be sure that the pte won't be stripped of higher bits in native code (again, as an example,native_make_pte()) because we are compiled with 5LEVEL?
native_make_pte()just encapsulatespte_t. It doesn't modify the value of the pte at all.
It's an interface though and so we don't know what is (or can) happen under it.
(I also obviously meant "because we are *not* compiled with 5LEVEL")
Quoted 4 lines
Physical address bits are only ever masked away via
PTE_PFN_MASKand I haven't found any place where it is used for a MFN other than those I touched in this patch.
OK.
-boris
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xen.org/xen-devel
Boris Ostrovsky
reviewerQuoted 10 lines · Juergen Gross
Quoted 9 lines · Boris Ostrovsky
Quoted 6 lines · Juergen Gross
Physical addresses on processors supporting 5 level paging can be up to 52 bits wide. For a Xen pv guest running on such a machine those physical addresses have to be supported in order to be able to use any memory on the machine even if the guest itself does not support 5 level paging.
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
So when reading/writing a MFN from/to a pte don't use the kernel's
PTE_PFN_MASKbut a newXEN_PTE_MFN_MASKallowing full 40 bit wide MFNs.full 52 bits?
The MFN mask is only 40 bits. This plus the 12 bits page offset are 52 bits of machine address width.
Oh, right --- frames, not addresses.
Quoted 25 lines
Quoted 9 lines
Quoted 9 lines
Signed-off-by Juergen Gross <[email protected]>--- arch/x86/include/asm/xen/page.h | 11 ++++++++++- arch/x86/xen/mmu_pv.c | 4 ++-- 2 files changed, 12 insertions(+), 3 deletions(-)Quoted 15 lines
arch/x86/include/asm/xen/page.h typedef struct xpaddr { · line 29
Quoted 10 lines
arch/x86/include/asm/xen/page.h +1
-0@@ -26,6 +26,15 @@ typedef struct xpaddr { phys_addr_t paddr; } xpaddr_t; +#ifdef CONFIG_X86_64 +#define XEN_PHYSICAL_MASK ((1UL << 52) - 1)SME is not supported for PV guests but for consistency (and in case sme bit somehow gets set)
#define XEN_PHYSICAL_MASK__sme_clr(((1UL << 52) - 1))
Quoted 5 lines
Hmm, really? Shouldn't we rather add something like
BUG_ON(sme_active());
somewhere?
We can do that too.
Quoted 9 lines
Quoted 6 lines
But the real question that I have is whether this patch is sufficient. We are trying to preserve more bits in mfn but then this mfn is used, say, in
pte_pfn_to_mfn()to build a pte. Can we be sure that the pte won't be stripped of higher bits in native code (again, as an example,native_make_pte()) because we are compiled with 5LEVEL?
native_make_pte()just encapsulatespte_t. It doesn't modify the value of the pte at all.
It's an interface though and so we don't know what is (or can) happen under it.
(I also obviously meant "because we are *not* compiled with 5LEVEL")
Quoted 4 lines
Physical address bits are only ever masked away via
PTE_PFN_MASKand I haven't found any place where it is used for a MFN other than those I touched in this patch.
OK.
-boris
Quoted 26 lines · Boris Ostrovsky
Quoted 26 lines
Quoted 25 lines
Quoted 18 lines
Signed-off-by Juergen Gross <[email protected]>---
arch/x86/include/asm/xen/page.h| 11 ++++++++++- arch/x86/xen/mmu_pv.c | 4 ++--2 files changed, 12 insertions(+), 3 deletions(-)arch/x86/include/asm/xen/page.h +0
-0@@ -26,6 +26,15 @@ typedef struct xpaddr { phys_addr_t paddr; } xpaddr_t;Quoted 2 lines
+#ifdef
CONFIG_X86_64
+#define XEN_PHYSICAL_MASK ((1UL << 52) - 1)SME is not supported for PV guests but for consistency (and in case sme bit somehow gets set)
#define XEN_PHYSICAL_MASK__sme_clr(((1UL << 52) - 1))
Quoted 7 lines
Quoted 5 lines
Hmm, really? Shouldn't we rather add something like
BUG_ON(sme_active());
somewhere?
We can do that too.
Please don't do anything to cause Linux to crash if Xen is using SME itself, but leaving all of the PV guest unencrypted.
~Andrew
Boris Ostrovsky
reviewerQuoted 29 lines · Andrew Cooper
Quoted 28 lines · Boris Ostrovsky
Quoted 28 lines
Quoted 10 lines
Quoted 10 lines
Signed-off-by Juergen Gross <[email protected]>---
arch/x86/include/asm/xen/page.h| 11 ++++++++++- arch/x86/xen/mmu_pv.c | 4 ++--2 files changed, 12 insertions(+), 3 deletions(-)Quoted 15 lines
Quoted 10 lines
arch/x86/include/asm/xen/page.h +0
-0@@ -26,6 +26,15 @@ typedef struct xpaddr { phys_addr_t paddr; } xpaddr_t;+#ifdef
CONFIG_X86_64
+#define XEN_PHYSICAL_MASK ((1UL << 52) - 1)SME is not supported for PV guests but for consistency (and in case sme bit somehow gets set)
#define XEN_PHYSICAL_MASK__sme_clr(((1UL << 52) - 1))Hmm, really? Shouldn't we rather add something like
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
BUG_ON(sme_active());
somewhere?
We can do that too.
Please don't do anything to cause Linux to crash if Xen is using SME itself, but leaving all of the PV guest unencrypted.
sme_active() returns true if the *guest* enables it.
Also, if the guest's memory is unencrypted, doesn't this mean that mfns that it sees (or, rather, ptes) will not have the SME bit set?
-boris
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xen.org/xen-devel
Boris Ostrovsky
reviewerQuoted 29 lines · Andrew Cooper
Quoted 28 lines · Boris Ostrovsky
Quoted 28 lines
Quoted 10 lines
Quoted 10 lines
Signed-off-by Juergen Gross <[email protected]>---
arch/x86/include/asm/xen/page.h| 11 ++++++++++- arch/x86/xen/mmu_pv.c | 4 ++--2 files changed, 12 insertions(+), 3 deletions(-)Quoted 15 lines
Quoted 10 lines
arch/x86/include/asm/xen/page.h +0
-0@@ -26,6 +26,15 @@ typedef struct xpaddr { phys_addr_t paddr; } xpaddr_t;+#ifdef
CONFIG_X86_64
+#define XEN_PHYSICAL_MASK ((1UL << 52) - 1)SME is not supported for PV guests but for consistency (and in case sme bit somehow gets set)
#define XEN_PHYSICAL_MASK__sme_clr(((1UL << 52) - 1))Hmm, really? Shouldn't we rather add something like
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
BUG_ON(sme_active());
somewhere?
We can do that too.
Please don't do anything to cause Linux to crash if Xen is using SME itself, but leaving all of the PV guest unencrypted.
sme_active() returns true if the *guest* enables it.
Also, if the guest's memory is unencrypted, doesn't this mean that mfns that it sees (or, rather, ptes) will not have the SME bit set?
-boris
Quoted 26 lines · Boris Ostrovsky
Quoted 26 lines
Quoted 25 lines
Quoted 18 lines
Signed-off-by Juergen Gross <[email protected]>---
arch/x86/include/asm/xen/page.h| 11 ++++++++++- arch/x86/xen/mmu_pv.c | 4 ++--2 files changed, 12 insertions(+), 3 deletions(-)arch/x86/include/asm/xen/page.h +0
-0@@ -26,6 +26,15 @@ typedef struct xpaddr { phys_addr_t paddr; } xpaddr_t;Quoted 2 lines
+#ifdef
CONFIG_X86_64
+#define XEN_PHYSICAL_MASK ((1UL << 52) - 1)SME is not supported for PV guests but for consistency (and in case sme bit somehow gets set)
#define XEN_PHYSICAL_MASK__sme_clr(((1UL << 52) - 1))
Quoted 7 lines
Quoted 5 lines
Hmm, really? Shouldn't we rather add something like
BUG_ON(sme_active());
somewhere?
We can do that too.
Please don't do anything to cause Linux to crash if Xen is using SME itself, but leaving all of the PV guest unencrypted.
~Andrew
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xen.org/xen-devel
Juergen Gross
maintainerQuoted 9 lines · Boris Ostrovsky
Quoted 6 lines · Juergen Gross
Physical addresses on processors supporting 5 level paging can be up to 52 bits wide. For a Xen pv guest running on such a machine those physical addresses have to be supported in order to be able to use any memory on the machine even if the guest itself does not support 5 level paging.
Quoted 4 lines
Quoted 2 lines
So when reading/writing a MFN from/to a pte don't use the kernel's
PTE_PFN_MASKbut a newXEN_PTE_MFN_MASKallowing full 40 bit wide MFNs.full 52 bits?
The MFN mask is only 40 bits. This plus the 12 bits page offset are 52 bits of machine address width.
Quoted 8 lines
Quoted 8 lines
Signed-off-by Juergen Gross <[email protected]>---
arch/x86/include/asm/xen/page.h| 11 ++++++++++- arch/x86/xen/mmu_pv.c | 4 ++--2 files changed, 12 insertions(+), 3 deletions(-)
Quoted 15 lines
Quoted 10 lines
arch/x86/include/asm/xen/page.h +0
-0@@ -26,6 +26,15 @@ typedef struct xpaddr { phys_addr_t paddr; } xpaddr_t;+#ifdef
CONFIG_X86_64
+#define XEN_PHYSICAL_MASK ((1UL << 52) - 1)SME is not supported for PV guests but for consistency (and in case sme bit somehow gets set)
#define XEN_PHYSICAL_MASK__sme_clr(((1UL << 52) - 1))
Hmm, really? Shouldn't we rather add something like
BUG_ON(sme_active());
somewhere?
Quoted 5 lines
But the real question that I have is whether this patch is sufficient. We are trying to preserve more bits in mfn but then this mfn is used, say, in
pte_pfn_to_mfn()to build a pte. Can we be sure that the pte won't be stripped of higher bits in native code (again, as an example,native_make_pte()) because we are compiled with 5LEVEL?
native_make_pte() just encapsulates pte_t. It doesn't modify the value of the pte at all.
Physical address bits are only ever masked away via PTE_PFN_MASK and I haven't found any place where it is used for a MFN other than those I touched in this patch.
Juergen
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xen.org/xen-devel