If qemu is new enough to support acpi table loading,
then go move pmbase out of the way. This allows to
use the whole 0x1000 - 0x io address space on q35.
piix has hotplug ports in the 0xa000 - 0xafff area,
so we can't do the same there.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
Use the new acpi_pm_base variable instead.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
src/fw/acpi.c | 14 +++---
src/fw/biostables.c | 1 +
src/fw/paravirt.h | 2 --
src/fw/pciinit.c| 16
src/fw/smm.c| 4 ++--
src/util.h | 1 +
6
Hi,
First patch swapped for v2 of this series, using the patch from Paolo
now, which removes the pmbase dependency in the smm code altogether.
Second patch (unmodified) makes acpi pmbase a variable and figure where
to place the registers at runtime. No functional change.
With these
From d478ac82045a27f82f44ea9ce65f642197fe6078 Mon Sep 17 00:00:00 2001
From: David Woodhouse david.woodho...@intel.com
Date: Fri, 25 Jan 2013 19:39:07 -0600
Subject: [PATCH] Update EFI_COMPATIBILITY16_TABLE to match 0.98 spec update
Unless CONFIG_MALLOC_UPPERMEMORY is turned off, we expect to use
On Tue, May 20, 2014 at 12:20:34PM +0200, Gerd Hoffmann wrote:
Hi,
First patch swapped for v2 of this series, using the patch from Paolo
now, which removes the pmbase dependency in the smm code altogether.
Second patch (unmodified) makes acpi pmbase a variable and figure where
to place
On Di, 2014-05-20 at 16:42 +0200, Igor Mammedov wrote:
On Tue, 20 May 2014 12:20:37 +0200
Gerd Hoffmann kra...@redhat.com wrote:
If qemu is new enough to support acpi table loading,
then go move pmbase out of the way. This allows to
use the whole 0x1000 - 0x io address space on q35.
On Tue, 20 May 2014 12:20:37 +0200
Gerd Hoffmann kra...@redhat.com wrote:
If qemu is new enough to support acpi table loading,
then go move pmbase out of the way. This allows to
use the whole 0x1000 - 0x io address space on q35.
piix has hotplug ports in the 0xa000 - 0xafff area,
so we
