support >3 level p2m tree
v3 cover support >3 level p2m tree
Pv domains write the mfn of a 3 level p2m tree to arch_shared_info structure. Consumers of this information are the domain save/restore functions of the Xen tools.
Being defined as having 3 levels the maximum supported domain size of 64 bit domains is 512 GB. The following patch expands the arch_shared_info structure to support more levels.
The Xen tools are not covered in this patch as the patch series "Libxl migration v2 support":
http://lists.xen.org/archives/html/xen-devel/2014-09/msg00427.html
should be applied first.
Juergen Gross (1):
expand x86 arch_shared_info to support >3 level p2m tree
xen/include/public/arch-x86/xen.h | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
Signature · 1 line
1.8.4.5
PATCH v3 1/1 expand x86 arch_shared_info to support >3 level p2m tree
The x86 struct arch_shared_info field pfn_to_mfn_frame_list_list currently contains the mfn of the top level page frame of the 3 level p2m tree, which is used by the Xen tools during saving and restoring (and live migration) of pv domains. With three levels of the p2m tree it is possible to support up to 512 GB of RAM for a 64 bit pv domain. A 32 bit pv domain can support more, as each memory page can hold 1024 instead of 512 entries, leading to a limit of 4 TB. To be able to support more RAM on x86-64 an additional level is to be added.
This patch expands struct arch_shared_info with a new p2m tree root and the number of levels of the p2m tree. The new information is indicated by the domain to be valid by storing ~0UL into pfn_to_mfn_frame_list_list (this should be done only if more than three levels are needed, of course).
--- xen/include/public/arch-x86/xen.h | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
xen/include/public/arch-x86/xen.h +6 -1
@@ -224,7 +224,12 @@ struct arch_shared_info {/* Frame containing list of mfns containing list of mfns containing p2m. */ xen_pfn_t pfn_to_mfn_frame_list_list;unsigned long nmi_reason; -uint64_t pad[32 ]; +/* +* Following two fields are valid if pfn_to_mfn_frame_list_list contains +* ~0UL. +*/ +unsigned long p2m_levels;/* number of levels of p2m tree */ +xen_pfn_t p2m_root;/* p2m tree top level mfn */ };typedef struct arch_shared_info arch_shared_info_t ;
Signature · 1 line
1.8.4.5
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 9 lines · Juergen Gross
The x86 struct
arch_shared_infofieldpfn_to_mfn_frame_list_listcurrently contains the mfn of the top level page frame of the 3 level p2m tree, which is used by the Xen tools during saving and restoring (and live migration) of pv domains. With three levels of the p2m tree it is possible to support up to 512 GB of RAM for a 64 bit pv domain. A 32 bit pv domain can support more, as each memory page can hold 1024 instead of 512 entries, leading to a limit of 4 TB. To be able to support more RAM on x86-64 an additional level is to be added.
Quoted 5 lines
This patch expands struct
arch_shared_infowith a new p2m tree root and the number of levels of the p2m tree. The new information is indicated by the domain to be valid by storing ~0UL intopfn_to_mfn_frame_list_list(this should be done only if more than three levels are needed, of course).
A small domain feeling a little tight on space could easily opt for a 2 or even 1 level p2m. (After all, one advantage of virt is to cram many small VMs into a server).
How is xen and toolstack support for n-level p2ms going to be advertised to guests? Simply assuming the toolstack is capable of dealing with this new scheme wont work with a new pv guest running on an older Xen.
~Andrew
Quoted 24 lines
Signed-off-by Juergen Gross <[email protected]>--- xen/include/public/arch-x86/xen.h | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)xen/include/public/arch-x86/xen.h +6
-1@@ -224,7 +224,12 @@ struct arch_shared_info {/* Frame containing list of mfns containing list of mfns containing p2m. */ xen_pfn_t pfn_to_mfn_frame_list_list;unsigned long nmi_reason; -uint64_t pad[32 ]; +/* +* Following two fields are valid if pfn_to_mfn_frame_list_list contains +* ~0UL. +*/ +unsigned long p2m_levels;/* number of levels of p2m tree */ +xen_pfn_t p2m_root;/* p2m tree top level mfn */ };typedef struct arch_shared_info arch_shared_info_t ;
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 16 lines · Andrew Cooper
Quoted 9 lines · Juergen Gross
The x86 struct
arch_shared_infofieldpfn_to_mfn_frame_list_listcurrently contains the mfn of the top level page frame of the 3 level p2m tree, which is used by the Xen tools during saving and restoring (and live migration) of pv domains. With three levels of the p2m tree it is possible to support up to 512 GB of RAM for a 64 bit pv domain. A 32 bit pv domain can support more, as each memory page can hold 1024 instead of 512 entries, leading to a limit of 4 TB. To be able to support more RAM on x86-64 an additional level is to be added.Quoted 5 lines
This patch expands struct
arch_shared_infowith a new p2m tree root and the number of levels of the p2m tree. The new information is indicated by the domain to be valid by storing ~0UL intopfn_to_mfn_frame_list_list(this should be done only if more than three levels are needed, of course).
Quoted 7 lines
A small domain feeling a little tight on space could easily opt for a 2 or even 1 level p2m. (After all, one advantage of virt is to cram many small VMs into a server).
How is xen and toolstack support for n-level p2ms going to be advertised to guests? Simply assuming the toolstack is capable of dealing with this new scheme wont work with a new pv guest running on an older Xen.
Is it really worth doing such an optimization? This would save only very few pages.
If you think it should be done we can add another SIF_* flag to start_info->flags. In this case a domain using this feature could not be migrated to a server with old tools, however. So we would probably end with the need to be able to suppress that flag on a per-domain base.
Juergen
Quoted 30 lines
~Andrew
Quoted 24 lines
Signed-off-by Juergen Gross <[email protected]>--- xen/include/public/arch-x86/xen.h | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)xen/include/public/arch-x86/xen.h +6
-1@@ -224,7 +224,12 @@ struct arch_shared_info {/* Frame containing list of mfns containing list of mfns containing p2m. */ xen_pfn_t pfn_to_mfn_frame_list_list;unsigned long nmi_reason; -uint64_t pad[32 ]; +/* +* Following two fields are valid if pfn_to_mfn_frame_list_list contains +* ~0UL. +*/ +unsigned long p2m_levels;/* number of levels of p2m tree */ +xen_pfn_t p2m_root;/* p2m tree top level mfn */ };typedef struct arch_shared_info arch_shared_info_t ;
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 25 lines · Juergen Gross
Quoted 16 lines · Andrew Cooper
Quoted 9 lines · Juergen Gross
The x86 struct
arch_shared_infofieldpfn_to_mfn_frame_list_listcurrently contains the mfn of the top level page frame of the 3 level p2m tree, which is used by the Xen tools during saving and restoring (and live migration) of pv domains. With three levels of the p2m tree it is possible to support up to 512 GB of RAM for a 64 bit pv domain. A 32 bit pv domain can support more, as each memory page can hold 1024 instead of 512 entries, leading to a limit of 4 TB. To be able to support more RAM on x86-64 an additional level is to be added.Quoted 5 lines
This patch expands struct
arch_shared_infowith a new p2m tree root and the number of levels of the p2m tree. The new information is indicated by the domain to be valid by storing ~0UL intopfn_to_mfn_frame_list_list(this should be done only if more than three levels are needed, of course).Quoted 7 lines
A small domain feeling a little tight on space could easily opt for a 2 or even 1 level p2m. (After all, one advantage of virt is to cram many small VMs into a server).
How is xen and toolstack support for n-level p2ms going to be advertised to guests? Simply assuming the toolstack is capable of dealing with this new scheme wont work with a new pv guest running on an older Xen.
Quoted 7 lines
Is it really worth doing such an optimization? This would save only very few pages.
If you think it should be done we can add another SIF_* flag to
start_info->flags. In this case a domain using this feature could not be migrated to a server with old tools, however. So we would probably end with the need to be able to suppress that flag on a per-domain base.
Any further comments?
Which way should I go?
Juergen
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 29 lines · Juergen Gross
Quoted 28 lines · Juergen Gross
Quoted 16 lines · Andrew Cooper
Quoted 9 lines · Juergen Gross
The x86 struct
arch_shared_infofieldpfn_to_mfn_frame_list_listcurrently contains the mfn of the top level page frame of the 3 level p2m tree, which is used by the Xen tools during saving and restoring (and live migration) of pv domains. With three levels of the p2m tree it is possible to support up to 512 GB of RAM for a 64 bit pv domain. A 32 bit pv domain can support more, as each memory page can hold 1024 instead of 512 entries, leading to a limit of 4 TB. To be able to support more RAM on x86-64 an additional level is to be added.Quoted 5 lines
This patch expands struct
arch_shared_infowith a new p2m tree root and the number of levels of the p2m tree. The new information is indicated by the domain to be valid by storing ~0UL intopfn_to_mfn_frame_list_list(this should be done only if more than three levels are needed, of course).Quoted 7 lines
A small domain feeling a little tight on space could easily opt for a 2 or even 1 level p2m. (After all, one advantage of virt is to cram many small VMs into a server).
How is xen and toolstack support for n-level p2ms going to be advertised to guests? Simply assuming the toolstack is capable of dealing with this new scheme wont work with a new pv guest running on an older Xen.
Is it really worth doing such an optimization? This would save only very few pages.
Quoted 9 lines
Quoted 4 lines
If you think it should be done we can add another SIF_* flag to
start_info->flags. In this case a domain using this feature could not be migrated to a server with old tools, however. So we would probably end with the need to be able to suppress that flag on a per-domain base.Any further comments?
Which way should I go?
There are two approaches, with different up/downsides
1) continue to use the old method, and use the new method only when absolutely required. This will function, but on old toolstacks, suffer migration/suspend failures when the toolstack fails to find the p2m.
2) Provide a Xen feature flag indicating the presence of N-level p2m support. Guests which can see this flag are free to use N-level, and guests which can't are not.
Ultimately, giving more than 512GB to a current 64bit PV domain is not going to work, and the choice above depends on which failure mode you wish a new/old mix to have.
~Andrew
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 48 lines · Andrew Cooper
Quoted 30 lines · Juergen Gross
Quoted 29 lines · Juergen Gross
Quoted 16 lines · Andrew Cooper
Quoted 9 lines · Juergen Gross
The x86 struct
arch_shared_infofieldpfn_to_mfn_frame_list_listcurrently contains the mfn of the top level page frame of the 3 level p2m tree, which is used by the Xen tools during saving and restoring (and live migration) of pv domains. With three levels of the p2m tree it is possible to support up to 512 GB of RAM for a 64 bit pv domain. A 32 bit pv domain can support more, as each memory page can hold 1024 instead of 512 entries, leading to a limit of 4 TB. To be able to support more RAM on x86-64 an additional level is to be added.Quoted 5 lines
This patch expands struct
arch_shared_infowith a new p2m tree root and the number of levels of the p2m tree. The new information is indicated by the domain to be valid by storing ~0UL intopfn_to_mfn_frame_list_list(this should be done only if more than three levels are needed, of course).Quoted 8 lines
A small domain feeling a little tight on space could easily opt for a 2 or even 1 level p2m. (After all, one advantage of virt is to cram many small VMs into a server).
How is xen and toolstack support for n-level p2ms going to be advertised
to guests? Simply assuming the toolstack is capable of dealing with this new scheme wont work with a new pv guest running on an older Xen.Is it really worth doing such an optimization? This would save only very few pages.
Quoted 9 lines
Quoted 4 lines
If you think it should be done we can add another SIF_* flag to
start_info->flags. In this case a domain using this feature could not be migrated to a server with old tools, however. So we would probably end with the need to be able to suppress that flag on a per-domain base.Any further comments?
Which way should I go?
There are two approaches, with different up/downsides
1) continue to use the old method, and use the new method only when absolutely required. This will function, but on old toolstacks, suffer migration/suspend failures when the toolstack fails to find the p2m.
Quoted 7 lines
2) Provide a Xen feature flag indicating the presence of N-level p2m support. Guests which can see this flag are free to use N-level, and guests which can't are not.
Ultimately, giving more than 512GB to a current 64bit PV domain is not going to work, and the choice above depends on which failure mode you wish a new/old mix to have.
I'd prefer solution 1), as it will enable Dom0 with more than 512 GB without requiring a change of any Xen component. Additionally large domains can be started by users who don't care for migrating or suspending them.
So I'd rather keep my patch as posted.
Juergen
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 54 lines
Quoted 1 line
Quoted 1 line · On 15.09.14 at 10:52, <[email protected]> wrote:
Quoted 52 lines · Andrew Cooper
Quoted 30 lines · Juergen Gross
Quoted 29 lines · Juergen Gross
Quoted 16 lines · Andrew Cooper
Quoted 9 lines · Juergen Gross
The x86 struct
arch_shared_infofieldpfn_to_mfn_frame_list_listcurrently contains the mfn of the top level page frame of the 3 level p2m tree, which is used by the Xen tools during saving and restoring (and live migration) of pv domains. With three levels of the p2m tree it is possible to support up to 512 GB of RAM for a 64 bit pv domain. A 32 bit pv domain can support more, as each memory page can hold 1024 instead of 512 entries, leading to a limit of 4 TB. To be able to support more RAM on x86-64 an additional level is to be added.Quoted 5 lines
This patch expands struct
arch_shared_infowith a new p2m tree root and the number of levels of the p2m tree. The new information is indicated by the domain to be valid by storing ~0UL intopfn_to_mfn_frame_list_list(this should be done only if more than three levels are needed, of course).Quoted 8 lines
A small domain feeling a little tight on space could easily opt for a 2 or even 1 level p2m. (After all, one advantage of virt is to cram many small VMs into a server).
How is xen and toolstack support for n-level p2ms going to be advertised
to guests? Simply assuming the toolstack is capable of dealing with this new scheme wont work with a new pv guest running on an older Xen.Is it really worth doing such an optimization? This would save only very few pages.
Quoted 9 lines
Quoted 4 lines
If you think it should be done we can add another SIF_* flag to
start_info->flags. In this case a domain using this feature could not be migrated to a server with old tools, however. So we would probably end with the need to be able to suppress that flag on a per-domain base.Any further comments?
Which way should I go?
There are two approaches, with different up/downsides
1) continue to use the old method, and use the new method only when absolutely required. This will function, but on old toolstacks, suffer migration/suspend failures when the toolstack fails to find the p2m.
2) Provide a Xen feature flag indicating the presence of N-level p2m support. Guests which can see this flag are free to use N-level, and guests which can't are not.
Quoted 8 lines
Quoted 3 lines
Ultimately, giving more than 512GB to a current 64bit PV domain is not going to work, and the choice above depends on which failure mode you wish a new/old mix to have.
I'd prefer solution 1), as it will enable Dom0 with more than 512 GB without requiring a change of any Xen component. Additionally large domains can be started by users who don't care for migrating or suspending them.
With the hopefully well understood limitation of kexec not working there (as it, just like migration for DomU, uses this table for Dom0 in at least machine_crash_shutdown()).
Jan
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 58 lines · Jan Beulich
Quoted 58 lines
Quoted 1 line
Quoted 1 line · On 15.09.14 at 10:52, <[email protected]> wrote:
Quoted 55 lines · Andrew Cooper
Quoted 30 lines · Juergen Gross
Quoted 29 lines · Juergen Gross
Quoted 16 lines · Andrew Cooper
Quoted 9 lines · Juergen Gross
The x86 struct
arch_shared_infofieldpfn_to_mfn_frame_list_listcurrently contains the mfn of the top level page frame of the 3 level p2m tree, which is used by the Xen tools during saving and restoring (and live migration) of pv domains. With three levels of the p2m tree it is possible to support up to 512 GB of RAM for a 64 bit pv domain. A 32 bit pv domain can support more, as each memory page can hold 1024 instead of 512 entries, leading to a limit of 4 TB. To be able to support more RAM on x86-64 an additional level is to be added.Quoted 5 lines
This patch expands struct
arch_shared_infowith a new p2m tree root and the number of levels of the p2m tree. The new information is indicated by the domain to be valid by storing ~0UL intopfn_to_mfn_frame_list_list(this should be done only if more than three levels are needed, of course).Quoted 8 lines
A small domain feeling a little tight on space could easily opt for a 2 or even 1 level p2m. (After all, one advantage of virt is to cram many small VMs into a server).
How is xen and toolstack support for n-level p2ms going to be advertised
to guests? Simply assuming the toolstack is capable of dealing with this new scheme wont work with a new pv guest running on an older Xen.Is it really worth doing such an optimization? This would save only very few pages.
Quoted 9 lines
Quoted 4 lines
If you think it should be done we can add another SIF_* flag to
start_info->flags. In this case a domain using this feature could not be migrated to a server with old tools, however. So we would probably end with the need to be able to suppress that flag on a per-domain base.Any further comments?
Which way should I go?
There are two approaches, with different up/downsides
1) continue to use the old method, and use the new method only when absolutely required. This will function, but on old toolstacks, suffer migration/suspend failures when the toolstack fails to find the p2m.
2) Provide a Xen feature flag indicating the presence of N-level p2m support. Guests which can see this flag are free to use N-level, and guests which can't are not.
Ultimately, giving more than 512GB to a current 64bit PV domain is not going to work, and the choice above depends on which failure mode you wish a new/old mix to have.
Quoted 8 lines
Quoted 4 lines
I'd prefer solution 1), as it will enable Dom0 with more than 512 GB without requiring a change of any Xen component. Additionally large domains can be started by users who don't care for migrating or suspending them.
With the hopefully well understood limitation of kexec not working there (as it, just like migration for DomU, uses this table for Dom0 in at least
machine_crash_shutdown()).
Sure. That's another issue to be addressed.
Juergen
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
In reply to Juergen GrossQuoted 62 lines · Juergen Gross
Quoted 53 lines · Andrew Cooper
Quoted 40 lines · Juergen Gross
Quoted 33 lines · Juergen Gross
Quoted 23 lines · Andrew Cooper
Quoted 10 lines · Juergen Gross
The x86 struct
arch_shared_infofieldpfn_to_mfn_frame_list_listcurrently contains the mfn of the top level page frame of the 3 level p2m tree, which is used by the Xen tools during saving and restoring (and live migration) of pv domains. With three levels of the p2m tree it is possible to support up to 512 GB of RAM for a 64 bit pv domain. A 32 bit pv domain can support more, as each memory page can hold 1024
instead of 512 entries, leading to a limit of 4 TB. To be able to support more RAM on x86-64 an additional level is to be added.Quoted 5 lines
This patch expands struct
arch_shared_infowith a new p2m tree root and the number of levels of the p2m tree. The new information is indicated by the domain to be valid by storing ~0UL intopfn_to_mfn_frame_list_list(this should be done only if more than three levels are needed, of course).A small domain feeling a little tight on space could easily opt for a 2
or even 1 level p2m. (After all, one advantage of virt is to cram many
small VMs into a server).Quoted 4 lines
How is xen and toolstack support for n-level p2ms going to be advertised
to guests? Simply assuming the toolstack is capable of dealing with this new scheme wont work with a new pv guest running on an older Xen.Is it really worth doing such an optimization? This would save only very
few pages.Quoted 5 lines
If you think it should be done we can add another SIF_* flag to
start_info->flags. In this case a domain using this feature could not be
migrated to a server with old tools, however. So we would probably end with the need to be able to suppress that flag on a per-domain base.Quoted 4 lines
Any further comments?
Which way should I go?
There are two approaches, with different up/downsides
1) continue to use the old method, and use the new method only when absolutely required. This will function, but on old toolstacks, suffer migration/suspend failures when the toolstack fails to find the p2m.
Quoted 7 lines
2) Provide a Xen feature flag indicating the presence of N-level p2m support. Guests which can see this flag are free to use N-level, and guests which can't are not.
Ultimately, giving more than 512GB to a current 64bit PV domain is not going to work, and the choice above depends on which failure mode you wish a new/old mix to have.
Quoted 6 lines
I'd prefer solution 1), as it will enable Dom0 with more than 512 GB without requiring a change of any Xen component. Additionally large domains can be started by users who don't care for migrating or suspending them.
So I'd rather keep my patch as posted.
PV guests can have extra memory added, beyond their initial limit. Supporting this would require option 2.
David
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 68 lines · David Vrabel
Quoted 67 lines · Juergen Gross
Quoted 53 lines · Andrew Cooper
Quoted 40 lines · Juergen Gross
Quoted 33 lines · Juergen Gross
Quoted 23 lines · Andrew Cooper
Quoted 10 lines · Juergen Gross
The x86 struct
arch_shared_infofieldpfn_to_mfn_frame_list_listcurrently contains the mfn of the top level page frame of the 3 level p2m tree, which is used by the Xen tools during saving and restoring (and live migration) of pv domains. With three levels of the p2m tree it is possible to support up to 512 GB of RAM for a 64 bit pv domain. A 32 bit pv domain can support more, as each memory page can hold 1024
instead of 512 entries, leading to a limit of 4 TB. To be able to support more RAM on x86-64 an additional level is to be added.Quoted 5 lines
This patch expands struct
arch_shared_infowith a new p2m tree root and the number of levels of the p2m tree. The new information is indicated by the domain to be valid by storing ~0UL intopfn_to_mfn_frame_list_list(this should be done only if more than three levels are needed, of course).A small domain feeling a little tight on space could easily opt for a 2
or even 1 level p2m. (After all, one advantage of virt is to cram many
small VMs into a server).Quoted 4 lines
How is xen and toolstack support for n-level p2ms going to be advertised
to guests? Simply assuming the toolstack is capable of dealing with this new scheme wont work with a new pv guest running on an older Xen.Is it really worth doing such an optimization? This would save only very
few pages.Quoted 5 lines
If you think it should be done we can add another SIF_* flag to
start_info->flags. In this case a domain using this feature could not be
migrated to a server with old tools, however. So we would probably end with the need to be able to suppress that flag on a per-domain base.Quoted 4 lines
Any further comments?
Which way should I go?
There are two approaches, with different up/downsides
1) continue to use the old method, and use the new method only when absolutely required. This will function, but on old toolstacks, suffer migration/suspend failures when the toolstack fails to find the p2m.
Quoted 7 lines
2) Provide a Xen feature flag indicating the presence of N-level p2m support. Guests which can see this flag are free to use N-level, and guests which can't are not.
Ultimately, giving more than 512GB to a current 64bit PV domain is not going to work, and the choice above depends on which failure mode you wish a new/old mix to have.
I'd prefer solution 1), as it will enable Dom0 with more than 512 GB without requiring a change of any Xen component. Additionally large domains can be started by users who don't care for migrating or suspending them.
Quoted 4 lines
Quoted 1 line
So I'd rather keep my patch as posted.
PV guests can have extra memory added, beyond their initial limit. Supporting this would require option 2.
I don't see why this should require option 2. Option 1 only prohibits suspending/migrating a domain with more than 512 GB. Just running it is fine with either option. I should mention, however, that the number of p2m tree levels will be increased on demand when needed. The tree won't be created with more than 3 levels if the domain isn't started with more than 512 GB.
Juergen
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 75 lines · Juergen Gross
Quoted 74 lines · David Vrabel
Quoted 73 lines · Juergen Gross
Quoted 59 lines · Andrew Cooper
Quoted 46 lines · Juergen Gross
Quoted 38 lines · Juergen Gross
Quoted 27 lines · Andrew Cooper
Quoted 14 lines · Juergen Gross
The x86 struct
arch_shared_infofieldpfn_to_mfn_frame_list_listcurrently contains the mfn of the top level page frame of the 3 level
p2m tree, which is used by the Xen tools during saving and restoring
(and live migration) of pv domains. With three levels of the p2m tree
it is possible to support up to 512 GB of RAM for a 64 bit pv domain.
A 32 bit pv domain can support more, as each memory page can hold 1024
instead of 512 entries, leading to a limit of 4 TB. To be able to support more RAM on x86-64 an additional level is to be added.Quoted 5 lines
This patch expands struct
arch_shared_infowith a new p2m tree root and the number of levels of the p2m tree. The new information is indicated by the domain to be valid by storing ~0UL intopfn_to_mfn_frame_list_list(this should be done only if more than three levels are needed, of course).A small domain feeling a little tight on space could easily opt for a 2
or even 1 level p2m. (After all, one advantage of virt is to cram many
small VMs into a server).Quoted 5 lines
How is xen and toolstack support for n-level p2ms going to be advertised
to guests? Simply assuming the toolstack is capable of dealing with this new scheme wont work with a new pv guest running on an older Xen.Is it really worth doing such an optimization? This would save only very
few pages.Quoted 6 lines
If you think it should be done we can add another SIF_* flag to
start_info->flags. In this case a domain using this feature could not be
migrated to a server with old tools, however. So we would probably end
with the need to be able to suppress that flag on a per-domain base.Quoted 4 lines
Any further comments?
Which way should I go?
There are two approaches, with different up/downsides
1) continue to use the old method, and use the new method only when absolutely required. This will function, but on old toolstacks, suffer migration/suspend failures when the toolstack fails to find the p2m.
Quoted 7 lines
2) Provide a Xen feature flag indicating the presence of N-level p2m support. Guests which can see this flag are free to use N-level, and guests which can't are not.
Ultimately, giving more than 512GB to a current 64bit PV domain is not going to work, and the choice above depends on which failure mode you wish a new/old mix to have.
I'd prefer solution 1), as it will enable Dom0 with more than 512 GB without requiring a change of any Xen component. Additionally large domains can be started by users who don't care for migrating or suspending them.
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
So I'd rather keep my patch as posted.
PV guests can have extra memory added, beyond their initial limit. Supporting this would require option 2.
I don't see why this should require option 2.
Um...
Quoted 1 line
Option 1 only prohibits suspending/migrating a domain with more than 512 GB.
...this is the reason.
With the exception of VMs that have assigned direct access to hardware, migration is an essential feature and must be supported.
David
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 83 lines · David Vrabel
Quoted 75 lines · Juergen Gross
Quoted 74 lines · David Vrabel
Quoted 73 lines · Juergen Gross
Quoted 59 lines · Andrew Cooper
Quoted 46 lines · Juergen Gross
Quoted 38 lines · Juergen Gross
Quoted 27 lines · Andrew Cooper
Quoted 14 lines · Juergen Gross
The x86 struct
arch_shared_infofieldpfn_to_mfn_frame_list_listcurrently contains the mfn of the top level page frame of the 3 level
p2m tree, which is used by the Xen tools during saving and restoring
(and live migration) of pv domains. With three levels of the p2m tree
it is possible to support up to 512 GB of RAM for a 64 bit pv domain.
A 32 bit pv domain can support more, as each memory page can hold 1024
instead of 512 entries, leading to a limit of 4 TB. To be able to support more RAM on x86-64 an additional level is to be added.Quoted 5 lines
This patch expands struct
arch_shared_infowith a new p2m tree root and the number of levels of the p2m tree. The new information is indicated by the domain to be valid by storing ~0UL intopfn_to_mfn_frame_list_list(this should be done only if more than three levels are needed, of course).A small domain feeling a little tight on space could easily opt for a 2
or even 1 level p2m. (After all, one advantage of virt is to cram many
small VMs into a server).Quoted 5 lines
How is xen and toolstack support for n-level p2ms going to be advertised
to guests? Simply assuming the toolstack is capable of dealing with this new scheme wont work with a new pv guest running on an older Xen.Is it really worth doing such an optimization? This would save only very
few pages.Quoted 6 lines
If you think it should be done we can add another SIF_* flag to
start_info->flags. In this case a domain using this feature could not be
migrated to a server with old tools, however. So we would probably end
with the need to be able to suppress that flag on a per-domain base.Quoted 4 lines
Any further comments?
Which way should I go?
There are two approaches, with different up/downsides
1) continue to use the old method, and use the new method only when absolutely required. This will function, but on old toolstacks, suffer migration/suspend failures when the toolstack fails to find the p2m.
Quoted 7 lines
2) Provide a Xen feature flag indicating the presence of N-level p2m support. Guests which can see this flag are free to use N-level, and guests which can't are not.
Ultimately, giving more than 512GB to a current 64bit PV domain is not going to work, and the choice above depends on which failure mode you wish a new/old mix to have.
I'd prefer solution 1), as it will enable Dom0 with more than 512 GB without requiring a change of any Xen component. Additionally large domains can be started by users who don't care for migrating or suspending them.
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
So I'd rather keep my patch as posted.
PV guests can have extra memory added, beyond their initial limit. Supporting this would require option 2.
I don't see why this should require option 2.
Quoted 8 lines
Um...
Quoted 1 line
Option 1 only prohibits suspending/migrating a domain with more than 512 GB.
...this is the reason.
With the exception of VMs that have assigned direct access to hardware, migration is an essential feature and must be supported.
So you'd prefer:
1) >512GB pv-domains (including Dom0) will be supported only with new Xen (4.6?), no matter if the user requires migration to be supported
to:
2) >512GB pv-domains (especially Dom0 and VMs with direct hw access) can be started on current Xen versions, migration is possible only if Xen is new (4.6?)
What is the common use case for migration? I doubt it is used very often for really huge domains.
I'm not really opposed to solution 2, but I doubt it is the correct one.
Juergen
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 10 lines
Quoted 1 line
Quoted 1 line · On 15.09.14 at 12:46, <[email protected]> wrote:
Quoted 2 lines · David Vrabel
With the exception of VMs that have assigned direct access to hardware, migration is an essential feature and must be supported.
So you'd prefer:
1) >512GB pv-domains (including Dom0) will be supported only with new Xen (4.6?), no matter if the user requires migration to be supported
Quoted 8 lines
to:
2) >512GB pv-domains (especially Dom0 and VMs with direct hw access) can be started on current Xen versions, migration is possible only if Xen is new (4.6?)
What is the common use case for migration? I doubt it is used very often for really huge domains.
Even without any guessing on the likelihood and usefulness of huge domains getting migrated, 1) clearly causing more functionality reduction than 2) I'm having a hard time seeing why 1) would be favored by anyone outside of academical/theoretical considerations.
Jan
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
In reply to Juergen GrossQuoted 97 lines · Juergen Gross
Quoted 96 lines · David Vrabel
Quoted 81 lines · Juergen Gross
Quoted 80 lines · David Vrabel
Quoted 79 lines · Juergen Gross
Quoted 64 lines · Andrew Cooper
Quoted 50 lines · Juergen Gross
Quoted 41 lines · Juergen Gross
Quoted 29 lines · Andrew Cooper
Quoted 14 lines · Juergen Gross
The x86 struct
arch_shared_infofieldpfn_to_mfn_frame_list_listcurrently contains the mfn of the top level page frame of the 3 level
p2m tree, which is used by the Xen tools during saving and restoring
(and live migration) of pv domains. With three levels of the p2m tree
it is possible to support up to 512 GB of RAM for a 64 bit pv domain.
A 32 bit pv domain can support more, as each memory page can hold 1024
instead of 512 entries, leading to a limit of 4 TB. To be able to support more RAM on x86-64 an additional level is to be added.Quoted 6 lines
This patch expands struct
arch_shared_infowith a new p2m tree root
and the number of levels of the p2m tree. The new information is indicated by the domain to be valid by storing ~0UL intopfn_to_mfn_frame_list_list(this should be done only if more than three levels are needed, of course).A small domain feeling a little tight on space could easily opt for
a 2
or even 1 level p2m. (After all, one advantage of virt is to cram many
small VMs into a server).Quoted 6 lines
How is xen and toolstack support for n-level p2ms going to be advertised
to guests? Simply assuming the toolstack is capable of dealing with
this new scheme wont work with a new pv guest running on an older Xen.Is it really worth doing such an optimization? This would save only very
few pages.Quoted 7 lines
If you think it should be done we can add another SIF_* flag to
start_info->flags. In this case a domain using this feature could not be
migrated to a server with old tools, however. So we would probably end
with the need to be able to suppress that flag on a per-domain base.Quoted 4 lines
Any further comments?
Which way should I go?
There are two approaches, with different up/downsides
1) continue to use the old method, and use the new method only when absolutely required. This will function, but on old toolstacks, suffer
migration/suspend failures when the toolstack fails to find the p2m.Quoted 8 lines
2) Provide a Xen feature flag indicating the presence of N-level p2m support. Guests which can see this flag are free to use N-level, and guests which can't are not.
Ultimately, giving more than 512GB to a current 64bit PV domain is not
going to work, and the choice above depends on which failure mode you wish a new/old mix to have.I'd prefer solution 1), as it will enable Dom0 with more than 512 GB without requiring a change of any Xen component. Additionally large domains can be started by users who don't care for migrating or suspending them.
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
So I'd rather keep my patch as posted.
PV guests can have extra memory added, beyond their initial limit. Supporting this would require option 2.
I don't see why this should require option 2.
Um...
Quoted 2 lines
Option 1 only prohibits suspending/migrating a domain with more than 512 GB.
...this is the reason.
Quoted 7 lines
Quoted 2 lines
With the exception of VMs that have assigned direct access to hardware, migration is an essential feature and must be supported.
So you'd prefer:
1) >512GB pv-domains (including Dom0) will be supported only with new Xen (4.6?), no matter if the user requires migration to be supported
Yes. >512 GiB and not being able to migrate are not obviously related from the point of view of the end user (unlike assigning a PCI device).
Failing at domain save time is most likely too late for the end user.
Quoted 5 lines
to:
2) >512GB pv-domains (especially Dom0 and VMs with direct hw access) can be started on current Xen versions, migration is possible only if Xen is new (4.6?)
There's also my preferred option:
3) >512 GiB PV domains are not supported. Large guests must be PVH or PVHVM.
Quoted 2 lines
What is the common use case for migration? I doubt it is used very often for really huge domains.
XenServer uses it for server pool upgrades with no VM downtime.
Also, today's huge VM is tomorrow's common size.
David
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 103 lines · David Vrabel
Quoted 102 lines · Juergen Gross
Quoted 91 lines · David Vrabel
Quoted 81 lines · Juergen Gross
Quoted 80 lines · David Vrabel
Quoted 79 lines · Juergen Gross
Quoted 64 lines · Andrew Cooper
Quoted 50 lines · Juergen Gross
Quoted 41 lines · Juergen Gross
Quoted 29 lines · Andrew Cooper
Quoted 14 lines · Juergen Gross
The x86 struct
arch_shared_infofieldpfn_to_mfn_frame_list_listcurrently contains the mfn of the top level page frame of the 3 level
p2m tree, which is used by the Xen tools during saving and restoring
(and live migration) of pv domains. With three levels of the p2m tree
it is possible to support up to 512 GB of RAM for a 64 bit pv domain.
A 32 bit pv domain can support more, as each memory page can hold 1024
instead of 512 entries, leading to a limit of 4 TB. To be able to support more RAM on x86-64 an additional level is to be added.Quoted 6 lines
This patch expands struct
arch_shared_infowith a new p2m tree root
and the number of levels of the p2m tree. The new information is indicated by the domain to be valid by storing ~0UL intopfn_to_mfn_frame_list_list(this should be done only if more than three levels are needed, of course).A small domain feeling a little tight on space could easily opt for
a 2
or even 1 level p2m. (After all, one advantage of virt is to cram many
small VMs into a server).Quoted 6 lines
How is xen and toolstack support for n-level p2ms going to be advertised
to guests? Simply assuming the toolstack is capable of dealing with
this new scheme wont work with a new pv guest running on an older Xen.Is it really worth doing such an optimization? This would save only very
few pages.Quoted 7 lines
If you think it should be done we can add another SIF_* flag to
start_info->flags. In this case a domain using this feature could not be
migrated to a server with old tools, however. So we would probably end
with the need to be able to suppress that flag on a per-domain base.Quoted 4 lines
Any further comments?
Which way should I go?
There are two approaches, with different up/downsides
1) continue to use the old method, and use the new method only when absolutely required. This will function, but on old toolstacks, suffer
migration/suspend failures when the toolstack fails to find the p2m.Quoted 8 lines
2) Provide a Xen feature flag indicating the presence of N-level p2m support. Guests which can see this flag are free to use N-level, and guests which can't are not.
Ultimately, giving more than 512GB to a current 64bit PV domain is not
going to work, and the choice above depends on which failure mode you wish a new/old mix to have.I'd prefer solution 1), as it will enable Dom0 with more than 512 GB without requiring a change of any Xen component. Additionally large domains can be started by users who don't care for migrating or suspending them.
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
So I'd rather keep my patch as posted.
PV guests can have extra memory added, beyond their initial limit. Supporting this would require option 2.
I don't see why this should require option 2.
Um...
Quoted 7 lines
Quoted 2 lines
Option 1 only prohibits suspending/migrating a domain with more than 512 GB.
...this is the reason.
With the exception of VMs that have assigned direct access to hardware, migration is an essential feature and must be supported.
So you'd prefer:
Quoted 7 lines
Quoted 2 lines
1) >512GB pv-domains (including Dom0) will be supported only with new Xen (4.6?), no matter if the user requires migration to be supported
Yes. >512 GiB and not being able to migrate are not obviously related from the point of view of the end user (unlike assigning a PCI device).
Failing at domain save time is most likely too late for the end user.
What would you think about following compromise:
We add a flag that indicates support of multi-level p2m. Additionally the Linux kernel can ignore the flag not being set either if started as Dom0 or if told so via kernel parameter.
Quoted 11 lines
Quoted 6 lines
to:
2) >512GB pv-domains (especially Dom0 and VMs with direct hw access) can be started on current Xen versions, migration is possible only if Xen is new (4.6?)
There's also my preferred option:
3) >512 GiB PV domains are not supported. Large guests must be PVH or PVHVM.
In theory okay, but not right now, I think. PVH Dom0 is not production ready.
Juergen
Quoted 15 lines
Quoted 3 lines
What is the common use case for migration? I doubt it is used very often for really huge domains.
XenServer uses it for server pool upgrades with no VM downtime.
Also, today's huge VM is tomorrow's common size.
David
_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xen.org/xen-devel
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 10 lines · Juergen Gross
Quoted 9 lines · David Vrabel
Quoted 4 lines · Juergen Gross
So you'd prefer:
1) >512GB pv-domains (including Dom0) will be supported only with new Xen (4.6?), no matter if the user requires migration to be supported
Yes. >512 GiB and not being able to migrate are not obviously related from the point of view of the end user (unlike assigning a PCI device).
Quoted 7 lines
Quoted 1 line
Failing at domain save time is most likely too late for the end user.
What would you think about following compromise:
We add a flag that indicates support of multi-level p2m. Additionally the Linux kernel can ignore the flag not being set either if started as Dom0 or if told so via kernel parameter.
This sounds fine but this override should be via the command line parameter only. Crash dump analysis tools may not understand the 4 level p2m.
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
to:
2) >512GB pv-domains (especially Dom0 and VMs with direct hw access) can be started on current Xen versions, migration is possible only if
Xenis new (4.6?)
Quoted 7 lines
Quoted 4 lines
There's also my preferred option:
3) >512 GiB PV domains are not supported. Large guests must be PVH or PVHVM.
In theory okay, but not right now, I think. PVH Dom0 is not production ready.
I'm not really seeing the need for such a large dom0.
I remain unconvinced that there are sufficient use cases to justify extending the PV only ABI and increasing complexity of the current 3-level p2m code.
I'm concerned that 4-level p2m support will impact the performance of guests that do not need the 4 levels. It may be necessary to use the alternatives mechanism to select the correct low-level lookup function.
I also think a flat array for the p2m might be better (less complex). There's plenty of virtual address space in a 64-bit guest to allow for this.
David
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 32 lines · David Vrabel
Quoted 10 lines · Juergen Gross
Quoted 9 lines · David Vrabel
Quoted 4 lines · Juergen Gross
So you'd prefer:
1) >512GB pv-domains (including Dom0) will be supported only with new Xen (4.6?), no matter if the user requires migration to be supported
Yes. >512 GiB and not being able to migrate are not obviously related from the point of view of the end user (unlike assigning a PCI device).
Quoted 7 lines
Quoted 1 line
Failing at domain save time is most likely too late for the end user.
What would you think about following compromise:
We add a flag that indicates support of multi-level p2m. Additionally the Linux kernel can ignore the flag not being set either if started as Dom0 or if told so via kernel parameter.
This sounds fine but this override should be via the command line parameter only. Crash dump analysis tools may not understand the 4 level p2m.
Quoted 9 lines
Quoted 9 lines
Quoted 6 lines
to:
2) >512GB pv-domains (especially Dom0 and VMs with direct hw access) can be started on current Xen versions, migration is possible only if
Xenis new (4.6?)There's also my preferred option:
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
3) >512 GiB PV domains are not supported. Large guests must be PVH or PVHVM.
In theory okay, but not right now, I think. PVH Dom0 is not production ready.
I'm not really seeing the need for such a large dom0.
Okay, then I'd come back to V1 of my patches. This is the minimum required to be able to boot up a system with Xen and more than 512GB memory without having to reduce the Dom0 memory via Xen boot parameter.
Otherwise the hypervisor built mfn_list mapped into the initial address space will be too large.
And no, I don't think setting the boot parameter is the solution here. Dom0 should be usable on a huge machine without special parameters.
Quoted 8 lines
I remain unconvinced that there are sufficient use cases to justify extending the PV only ABI and increasing complexity of the current 3-level p2m code.
I'm concerned that 4-level p2m support will impact the performance of guests that do not need the 4 levels. It may be necessary to use the alternatives mechanism to select the correct low-level lookup function.
I'll try to get some numbers to post together with a patch.
Quoted 2 lines
I also think a flat array for the p2m might be better (less complex). There's plenty of virtual address space in a 64-bit guest to allow for this.
Hmm, do you think we could reserve an area of many GBs for Xen in virtual space? I suspect this would be rejected as another "Xen-ism".
BTW: the mfn_list_list will still be required to be built as a tree.
Juergen
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 47 lines · Juergen Gross
Quoted 34 lines · David Vrabel
Quoted 11 lines · Juergen Gross
Quoted 10 lines · David Vrabel
Quoted 5 lines · Juergen Gross
So you'd prefer:
1) >512GB pv-domains (including Dom0) will be supported only with new Xen (4.6?), no matter if the user requires migration to be
supportedYes. >512 GiB and not being able to migrate are not obviously related from the point of view of the end user (unlike assigning a PCI device).
Quoted 7 lines
Quoted 1 line
Failing at domain save time is most likely too late for the end user.
What would you think about following compromise:
We add a flag that indicates support of multi-level p2m. Additionally the Linux kernel can ignore the flag not being set either if started as Dom0 or if told so via kernel parameter.
This sounds fine but this override should be via the command line parameter only. Crash dump analysis tools may not understand the 4 level p2m.
Quoted 10 lines
Quoted 10 lines
Quoted 7 lines
to:
2) >512GB pv-domains (especially Dom0 and VMs with direct hw access) can
be started on current Xen versions, migration is possible only if
Xenis new (4.6?)There's also my preferred option:
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
3) >512 GiB PV domains are not supported. Large guests must be PVH or PVHVM.
In theory okay, but not right now, I think. PVH Dom0 is not production ready.
I'm not really seeing the need for such a large dom0.
Okay, then I'd come back to V1 of my patches. This is the minimum required to be able to boot up a system with Xen and more than 512GB memory without having to reduce the Dom0 memory via Xen boot parameter.
Quoted 5 lines
Otherwise the hypervisor built
mfn_listmapped into the initial address space will be too large.And no, I don't think setting the boot parameter is the solution here. Dom0 should be usable on a huge machine without special parameters.
Ok. The case where's dom0's p2m format matters is pretty specialized.
Quoted 6 lines
Quoted 3 lines
I also think a flat array for the p2m might be better (less complex). There's plenty of virtual address space in a 64-bit guest to allow for this.
Hmm, do you think we could reserve an area of many GBs for Xen in virtual space? I suspect this would be rejected as another "Xen-ism".
alloc_vm_area()
Quoted 1 line
BTW: the
mfn_list_listwill still be required to be built as a tree.
The tools could be given the guest virtual address and walk the guest page tables.
This is probably too much of a difference from the existing ABI to be worth pursuing at this point.
David
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 56 lines · David Vrabel
Quoted 47 lines · Juergen Gross
Quoted 34 lines · David Vrabel
Quoted 11 lines · Juergen Gross
Quoted 10 lines · David Vrabel
Quoted 5 lines · Juergen Gross
So you'd prefer:
1) >512GB pv-domains (including Dom0) will be supported only with new Xen (4.6?), no matter if the user requires migration to be
supportedYes. >512 GiB and not being able to migrate are not obviously related from the point of view of the end user (unlike assigning a PCI device).
Quoted 7 lines
Quoted 1 line
Failing at domain save time is most likely too late for the end user.
What would you think about following compromise:
We add a flag that indicates support of multi-level p2m. Additionally the Linux kernel can ignore the flag not being set either if started as Dom0 or if told so via kernel parameter.
This sounds fine but this override should be via the command line parameter only. Crash dump analysis tools may not understand the 4 level p2m.
Quoted 10 lines
Quoted 10 lines
Quoted 7 lines
to:
2) >512GB pv-domains (especially Dom0 and VMs with direct hw access) can
be started on current Xen versions, migration is possible only if
Xenis new (4.6?)There's also my preferred option:
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
3) >512 GiB PV domains are not supported. Large guests must be PVH or PVHVM.
In theory okay, but not right now, I think. PVH Dom0 is not production ready.
I'm not really seeing the need for such a large dom0.
Okay, then I'd come back to V1 of my patches. This is the minimum required to be able to boot up a system with Xen and more than 512GB memory without having to reduce the Dom0 memory via Xen boot parameter.
Quoted 5 lines
Otherwise the hypervisor built
mfn_listmapped into the initial address space will be too large.And no, I don't think setting the boot parameter is the solution here. Dom0 should be usable on a huge machine without special parameters.
Ok. The case where's dom0's p2m format matters is pretty specialized.
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
I also think a flat array for the p2m might be better (less complex). There's plenty of virtual address space in a 64-bit guest to allow for this.
Hmm, do you think we could reserve an area of many GBs for Xen in virtual space? I suspect this would be rejected as another "Xen-ism".
alloc_vm_area()
Nice idea, but alloc_vm_area() allocates ptes for the whole area. __get_vm_area() would be better, I think.
Quoted 8 lines
Quoted 2 lines
BTW: the
mfn_list_listwill still be required to be built as a tree.The tools could be given the guest virtual address and walk the guest page tables.
This is probably too much of a difference from the existing ABI to be worth pursuing at this point.
Okay, coming back to the main question:
What to do regarding support of >512GB domains:
1. we need another level of the p2m map
2. we are trying the linear p2m table
a) with a 4 level mfn_list_list
b) with access to the p2m table via page tables
3. my V1 patches are okay, as they enable Dom0 to start on machines with huge memory
Juergen
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 86 lines · Juergen Gross
Quoted 62 lines · David Vrabel
Quoted 53 lines · Juergen Gross
Quoted 39 lines · David Vrabel
Quoted 14 lines · Juergen Gross
Quoted 13 lines · David Vrabel
Quoted 6 lines · Juergen Gross
So you'd prefer:
1) >512GB pv-domains (including Dom0) will be supported only with new
Xen (4.6?), no matter if the user requires migration to be
supportedYes. >512 GiB and not being able to migrate are not obviously related
from the point of view of the end user (unlike assigning a PCI device).Quoted 8 lines
Quoted 1 line
Failing at domain save time is most likely too late for the end user.
What would you think about following compromise:
We add a flag that indicates support of multi-level p2m. Additionally the Linux kernel can ignore the flag not being set either if started as
Dom0 or if told so via kernel parameter.This sounds fine but this override should be via the command line parameter only. Crash dump analysis tools may not understand the 4 level p2m.
Quoted 11 lines
Quoted 11 lines
Quoted 8 lines
to:
2) >512GB pv-domains (especially Dom0 and VMs with direct hw access) can
be started on current Xen versions, migration is possible
only if
Xenis new (4.6?)There's also my preferred option:
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
3) >512 GiB PV domains are not supported. Large guests must be PVH or
PVHVM.In theory okay, but not right now, I think. PVH Dom0 is not production ready.
I'm not really seeing the need for such a large dom0.
Okay, then I'd come back to V1 of my patches. This is the minimum required to be able to boot up a system with Xen and more than 512GB memory without having to reduce the Dom0 memory via Xen boot parameter.
Quoted 5 lines
Otherwise the hypervisor built
mfn_listmapped into the initial address space will be too large.And no, I don't think setting the boot parameter is the solution here. Dom0 should be usable on a huge machine without special parameters.
Ok. The case where's dom0's p2m format matters is pretty specialized.
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
I also think a flat array for the p2m might be better (less complex). There's plenty of virtual address space in a 64-bit guest to allow for this.
Hmm, do you think we could reserve an area of many GBs for Xen in virtual space? I suspect this would be rejected as another "Xen-ism".
alloc_vm_area()Nice idea, but
alloc_vm_area()allocates ptes for the whole area.__get_vm_area()would be better, I think.Quoted 8 lines
Quoted 2 lines
BTW: the
mfn_list_listwill still be required to be built as a tree.The tools could be given the guest virtual address and walk the guest page tables.
This is probably too much of a difference from the existing ABI to be worth pursuing at this point.
Okay, coming back to the main question:
Quoted 8 lines
What to do regarding support of >512GB domains:
1. we need another level of the p2m map
2. we are trying the linear p2m table
a) with a 4 levelmfn_list_list
b) with access to the p2m table via page tables
3. my V1 patches are okay, as they enable Dom0 to start on machines with huge memory
I thought a little bit more about this.
I like the idea to use the virtual mapped linear p2m list. It would remove the need to build the p2m tree at an early boot stage, as the initial mfn_list supplied by the hypervisor can be used until the kernel builds it's own list.
I'll try to create patch doing this. As this is not affecting the initial mapping of initrd and mfn_list I've posted V2 of my patches to eliminate some of the limitations of those initial mappings.
Whether the mfn_list_list should be kept as a tree or (if indicated by a flag to be supported) is accessed via page table walk of the tools can be decided later.
Juergen
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
In reply to Juergen GrossQuoted 10 lines
Quoted 1 line
Quoted 1 line · On 09.09.14 at 11:58, <"[email protected]".non-mime.internet> wrote:
The x86 struct
arch_shared_infofieldpfn_to_mfn_frame_list_listcurrently contains the mfn of the top level page frame of the 3 level p2m tree, which is used by the Xen tools during saving and restoring (and live migration) of pv domains. With three levels of the p2m tree it is possible to support up to 512 GB of RAM for a 64 bit pv domain. A 32 bit pv domain can support more, as each memory page can hold 1024 instead of 512 entries, leading to a limit of 4 TB. To be able to support more RAM on x86-64 an additional level is to be added.
Quoted 7 lines
This patch expands struct
arch_shared_infowith a new p2m tree root and the number of levels of the p2m tree. The new information is indicated by the domain to be valid by storing ~0UL intopfn_to_mfn_frame_list_list(this should be done only if more than three levels are needed, of course).Signed-off-by Juergen Gross <[email protected]>
Still having this in my to-be-committed-or-otherwise list, David - you had reservations here. Did they get addressed by Jürgen? Is there any alternative proposal? Or are we setting this aside until after 4.5?
Thanks, Jan
Quoted 27 lines
--- xen/include/public/arch-x86/xen.h | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)xen/include/public/arch-x86/xen.h +0
-0@@ -224,7 +224,12 @@ struct arch_shared_info {/* Frame containing list of mfns containing list of mfns containing p2m. */
xen_pfn_t pfn_to_mfn_frame_list_list; unsigned long nmi_reason;xen/include/public/arch-x86/xen.h +2
-1-uint64_t pad[32 ]; +/* +* Following two fields are valid if pfn_to_mfn_frame_list_list contains
xen/include/public/arch-x86/xen.h +4
-0+* ~0UL. +*/ +unsigned long p2m_levels;/* number of levels of p2m tree */ +xen_pfn_t p2m_root;/* p2m tree top level mfn */ };typedef struct arch_shared_info arch_shared_info_t ;Signature · 2 lines
-- 1.8.4.5
_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xen.org/xen-devel
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: [PATCH V3 1/1] expand x86 arch_shared_info to support >3 level p2m tree
Quoted 16 lines · Jan Beulich
Quoted 16 lines
Quoted 1 line
Quoted 1 line · On 09.09.14 at 11:58, <"[email protected]".non-mime.internet> wrote:
The x86 struct
arch_shared_infofieldpfn_to_mfn_frame_list_listcurrently contains the mfn of the top level page frame of the 3 level p2m tree, which is used by the Xen tools during saving and restoring (and live migration) of pv domains. With three levels of the p2m tree it is possible to support up to 512 GB of RAM for a 64 bit pv domain. A 32 bit pv domain can support more, as each memory page can hold 1024 instead of 512 entries, leading to a limit of 4 TB. To be able to support more RAM on x86-64 an additional level is to be added.This patch expands struct
arch_shared_infowith a new p2m tree root and the number of levels of the p2m tree. The new information is indicated by the domain to be valid by storing ~0UL intopfn_to_mfn_frame_list_list(this should be done only if more than three levels are needed, of course).
Quoted 6 lines
Quoted 1 line
Signed-off-by Juergen Gross <[email protected]>Still having this in my to-be-committed-or-otherwise list, David - you had reservations here. Did they get addressed by Jürgen? Is there any alternative proposal? Or are we setting this aside until after 4.5?
David had the alternative proposal to use a virtual mapped linear mfn_list with the tools doing the translation as needed. I'm just trying to do this, so please ignore my patch.
Juergen
_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xen.org/xen-devel