Not sure how much it counts, but I personally can agree with you on this
direction :)
One note below:
@@ -603,8 +604,72 @@ acpi_setup(void)
if (! CONFIG_ACPI)
return;
+int acpi_generate = 1;
+
dprintf(3, init ACPI tables\n);
+struct romfile_s *file = NULL;
On Mon, Apr 29, 2013 at 01:41:01PM +0200, Laszlo Ersek wrote:
Not sure how much it counts, but I personally can agree with you on this
direction :)
One note below:
@@ -603,8 +604,72 @@ acpi_setup(void)
if (! CONFIG_ACPI)
return;
+int acpi_generate = 1;
+
Load memory window setup for pci from host.
This makes it possible for host to make sure
setup matches hardware exactly: especially important
for when ACPI tables are loaded from host.
This will also make it easier to add more chipsets
down the road.
Signed-off-by: Michael S. Tsirkin
On Mon, Apr 29, 2013 at 06:21:43PM +0300, Michael S. Tsirkin wrote:
This will make it possible to use fw config
info for pci initialization.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
src/paravirt.c | 2 ++
src/post.c | 1 -
2 files changed, 2 insertions(+), 1 deletion(-)
On Mon, Apr 29, 2013 at 06:21:40PM +0300, Michael S. Tsirkin wrote:
Load memory window setup for pci from host.
This makes it possible for host to make sure
setup matches hardware exactly: especially important
for when ACPI tables are loaded from host.
This will also make it easier to add
On Mon, Apr 29, 2013 at 07:27:29PM -0400, Kevin O'Connor wrote:
On Mon, Apr 29, 2013 at 06:21:40PM +0300, Michael S. Tsirkin wrote:
Load memory window setup for pci from host.
This makes it possible for host to make sure
setup matches hardware exactly: especially important
for when ACPI
On Mon, Apr 29, 2013 at 07:23:37PM -0400, Kevin O'Connor wrote:
On Mon, Apr 29, 2013 at 06:21:43PM +0300, Michael S. Tsirkin wrote:
This will make it possible to use fw config
info for pci initialization.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
src/paravirt.c | 2 ++
