diff options
| author | Jan Beulich <jbeulich@novell.com> | 2011-07-25 16:42:53 +0100 |
|---|---|---|
| committer | Jan Beulich <jbeulich@novell.com> | 2011-07-25 16:42:53 +0100 |
| commit | 4297249197a5adf2c7517f6d55ed4273ce5e8a05 (patch) | |
| tree | 5f74b00680e9b010daf872aebb31d57297e7ec6f /xen/include/asm-x86/e820.h | |
| parent | 278acdb073c35391c5dea22e1bd8179a3cef58bc (diff) | |
| download | xen-4297249197a5adf2c7517f6d55ed4273ce5e8a05.tar.gz xen-4297249197a5adf2c7517f6d55ed4273ce5e8a05.tar.bz2 xen-4297249197a5adf2c7517f6d55ed4273ce5e8a05.zip | |
x86-64/MMCFG: finally make Fam10 enabling work
Forcibly enabling the MMCFG space on AMD Fam10 CPUs cannot be expected
to work since with the firmware not being aware of the address range
used it cannot possibly reserve the space in E820 or ACPI resources.
Hence we need to manually insert the range into the E820 table, and
enable the range only when the insertion actually works without
conflict.
Further, the actual enabling of the space is done from identify_cpu(),
which means that acpi_mmcfg_init() muts be called after that function
(and hance should not be called from acpi_boot_init()). Otherwise,
Dom0 would be able to use MMCFG, but Xen wouldn't.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Diffstat (limited to 'xen/include/asm-x86/e820.h')
| -rw-r--r-- | xen/include/asm-x86/e820.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/xen/include/asm-x86/e820.h b/xen/include/asm-x86/e820.h index d0486ae7c5..0fd81f6a0f 100644 --- a/xen/include/asm-x86/e820.h +++ b/xen/include/asm-x86/e820.h @@ -28,6 +28,8 @@ extern int reserve_e820_ram(struct e820map *e820, uint64_t s, uint64_t e); extern int e820_change_range_type( struct e820map *e820, uint64_t s, uint64_t e, uint32_t orig_type, uint32_t new_type); +extern int e820_add_range( + struct e820map *, uint64_t s, uint64_t e, uint32_t type); extern unsigned long init_e820(const char *, struct e820entry *, int *); extern struct e820map e820; |