aboutsummaryrefslogtreecommitdiffstats
path: root/xen/include/asm-x86/e820.h
Commit message (Collapse)AuthorAgeFilesLines
* x86-64/MMCFG: finally make Fam10 enabling workJan Beulich2011-07-251-0/+2
| | | | | | | | | | | | | | | | 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>
* Enable pci mmcfg and ATS for x86_64Keir Fraser2009-06-021-0/+1
| | | | | | This patch enables PCI MMCONFIG in xen and turns on hooks for ATS. Signed-off-by: Allen Kay <allen.m.kay@intel.com>
* tboot: tboot no longer marks TXT regions as E820_UNUSABLE, so Xen mustKeir Fraser2009-01-291-0/+3
| | | | | | | explicitly disallow them itself. Signed-off-by: Shane Wang <shane.wang@intel.com> Signed-off-by: Joseph Cihula <joseph.cihula@intel.com>
* x86: force DMI table to not be in E820 RAM regionKeir Fraser2007-09-261-0/+1
| | | | | | | | | | In order for Dom0 to be able to map the DMI table, it must not be in E820 RAM; since some BIOS versions apparently fail to set the type correctly for the page(s) containing this table, adjust it before starting to consume memory. Signed-off-by: Jan Beulich <jbeulich@novell.com> Signed-off-by: Keir Fraser <keir@xensource.com>
* xen: Understand the E820_UNUSABLE (type code 5) memory type.kfraser@localhost.localdomain2007-08-301-0/+1
| | | | | Signed-off-by: Joseph Cihula <joseph.cihula@intel.com> Signed-off-by: Keir Fraser <keir@xensource.com>
* hvm: e820 public header cleanup.Keir Fraser2007-06-101-1/+13
| | | | Signed-off-by: Keir Fraser <keir@xensource.com>
* x86: Print source of e820 memory map during boot. Fix Xen-e801 memmapkfraser@localhost.localdomain2007-06-071-2/+5
| | | | | | parsing. Get rid of unneeded e820_raw variable -- map straight onto boot-trampoline e820 array. Signed-off-by: Keir Fraser <keir@xensource.com>
* x86: Return to real-mode when booting primary CPU, and gatherkfraser@localhost.localdomain2007-06-071-0/+5
| | | | | | | memory-map information (from int15{e820,e801,88} and int12 bios calls). Signed-off-by: Keir Fraser <keir@xensource.com>
* [XEN] Clean up e820 definitions. Define shared set in hvm public dir.kaf24@localhost.localdomain2006-08-131-30/+1
| | | | Signed-off-by: Keir Fraser <keir@xensource.com>
* [hvm/qemu] Add HVM buffered IO writes framework to accelerate stdvga speed.chris@kneesaa.uk.xensource.com2006-08-091-0/+1
| | | | | | | | | | With this patch, win2k VMX guest boots fine on xen. Signed-off-by: Zhu Han <zhu.han@intel.com> Signed-off-by: Eddie Dong <eddie.dong@intel.com> Signed-off-by: Xin Li <xin.b.li@intel.com> Signed-off-by: Christian Limpach <Christian.Limpach@xensource.com>
* Clean up xc_vmx_build():kaf24@firebug.cl.cam.ac.uk2005-09-231-0/+5
| | | | | | | | | | | | 1. Remove linux parameters. 2. Remove init ramdisk. 3. Remove e820 memmap config file parse. 4. Removed provisional GDT. 5. Removed some ugly tailing space. Signed-off-by: Xin B Li <xin.b.li@intel.com>
* We found machines with >32 E820 memory map entries, where Xen fails tokaf24@firebug.cl.cam.ac.uk2005-08-171-1/+1
| | | | | | | | | | | boot (but Linux does boot fine). The native Linux (both x86 and x86_86) already has: #define E820MAX 128 /* number of entries in E820MAP */ Signed-off-by: Jun Nakajima <jun.nakajima@intel.com>
* bitkeeper revision 1.1428 (4289c9f6GdUyHEH-FCu9rRuWtOXnXQ)kaf24@firebug.cl.cam.ac.uk2005-05-171-1/+1
| | | | | | | | Initialise 1:1 mapping of physical memory map early during x86/64 boot. This mapping should include all ACPI tables, so simplify the mapping check in the ACPI code. Signed-off-by: Keir Fraser <keir@xensource.com>
* bitkeeper revision 1.1233 (421a1c36TYJWUEtp558QjJv1X0XXrQ)maf46@burn.cl.cam.ac.uk2005-02-211-0/+4
| | | | | | | If debugging is enabled, printout the e820 map for vmx guests. Signed-off-by: michael.fetterman@cl.cam.ac.uk
* bitkeeper revision 1.1159.1.518 (41d448acXfjJK8iSoExMLCtViOvsoA)kaf24@scramble.cl.cam.ac.uk2004-12-301-2/+2
|\ | | | | | | | | | | Merge scramble.cl.cam.ac.uk:/local/scratch/kaf24/xen-2.0-testing.bk into scramble.cl.cam.ac.uk:/local/scratch/kaf24/xen-unstable.bk
| * bitkeeper revision 1.1159.170.74 (41d4488f9fINTxUzyjoq2FnTn5AvMQ)kaf24@scramble.cl.cam.ac.uk2004-12-301-2/+2
| | | | | | | | | | Improved memory bootstrapping takes into account e820 RAM holes.
* | bitkeeper revision 1.1159.207.2 (41d3ee2b8X5k263Pk7ShvbMkpcLkMg)kaf24@scramble.cl.cam.ac.uk2004-12-301-4/+6
|/ | | | | manual merge
* bitkeeper revision 1.1159.170.72 (41d3eaaftC1Zqz_rl9bIUUcTSZFIjg)kaf24@scramble.cl.cam.ac.uk2004-12-301-0/+33
Add e820 parsing to Xen. Currently not hooked into heap initialisation: this is the next step.