mirror of
https://github.com/xen-project/xen.git
synced 2026-10-28 10:11:27 +01:00
Keir Fraser
c6d8d541e9
By adding another ELF note, the kernel can now direct the hypervisor (for Dom0) and in the future also the tools (for DomU-s) to place the initial phys->mach translation table at other than an address immediately above the kernel/initrd images. This eliminates the size restriction imposed on this table by Linux (the kernel loads above the -2Gb boundary, and hence the entire initial mapping cannot reach or even exceed 2Gb). There are a few items in this patch I'm not particularly happy with, but couldn't think of a better solution: - there is a hidden assumption that pages allocated for the domain are put on the domain's page list sequentially - the way backward compatibility is maintained is placing requirements on the kernel side that make the code somewhat convoluted (because it needs to check where the map is actually placed in quite a few places) - code is there to use 1Gb mappings for the hypervisor created table, but lacking a machine with 512G+ memory for immediate testing I can't verify this works; I know that 2Mb mappings work, and hence imply that 1Gb ones would too (of course, if the kernel replaces the table - like Linux does -, it cannot use 2Mb/1Gb mappings or even try to re-use the page table entries, but I don't consider this a problem) Signed-off-by: Jan Beulich <jbeulich@novell.com>
19 lines
783 B
Plaintext
19 lines
783 B
Plaintext
|
|
structs | x86_32 x86_64 ia64
|
|
|
|
start_info | 1112 1168 1168
|
|
trap_info | 8 16 -
|
|
pt_fpreg | - - 16
|
|
cpu_user_regs | 68 200 -
|
|
xen_ia64_boot_param | - - 96
|
|
ia64_tr_entry | - - 32
|
|
vcpu_tr_regs | - - 768
|
|
vcpu_guest_context_regs | - - 22176
|
|
vcpu_guest_context | 2800 5168 22208
|
|
arch_vcpu_info | 24 16 0
|
|
vcpu_time_info | 32 32 32
|
|
vcpu_info | 64 64 48
|
|
arch_shared_info | 268 280 272
|
|
shared_info | 2584 3368 4384
|
|
|