From: Bruce Rogers <brogers@suse.com>
To: qemu-devel@nongnu.org
Cc: imammedo@redhat.com, sstabellini@kernel.org, mst@redhat.com,
qemu-stable@nongnu.org, Bruce Rogers <brogers@suse.com>
Subject: [Qemu-devel] [PATCH] ACPI: call acpi_set_pci_info when only acpi enabled
Date: Wed, 26 Apr 2017 13:07:02 -0600 [thread overview]
Message-ID: <1493233622-14485-1-git-send-email-brogers@suse.com> (raw)
Commit f0c9d64a exposed an issue with the code order in acpi_setup.
As of that commit, a xenfv machine type guest will no longer start
if using pci passthrough. Re-order the code in that function to
allow acpi_set_pci_info to be called before bailing on the other,
non-related conditions. With this change I can again use pci
passthrough and xenfv together.
Signed-off-by: Bruce Rogers <brogers@suse.com>
---
hw/i386/acpi-build.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index 2073108..1ec072f 100644
--- a/hw/i386/acpi-build.c
+++ b/hw/i386/acpi-build.c
@@ -2834,6 +2834,13 @@ void acpi_setup(void)
AcpiBuildState *build_state;
Object *vmgenid_dev;
+ if (!acpi_enabled) {
+ ACPI_BUILD_DPRINTF("ACPI disabled. Bailing out.\n");
+ return;
+ }
+
+ acpi_set_pci_info();
+
if (!pcms->fw_cfg) {
ACPI_BUILD_DPRINTF("No fw cfg. Bailing out.\n");
return;
@@ -2844,15 +2851,8 @@ void acpi_setup(void)
return;
}
- if (!acpi_enabled) {
- ACPI_BUILD_DPRINTF("ACPI disabled. Bailing out.\n");
- return;
- }
-
build_state = g_malloc0(sizeof *build_state);
- acpi_set_pci_info();
-
acpi_build_tables_init(&tables);
acpi_build(&tables, MACHINE(pcms));
--
1.9.0
next reply other threads:[~2017-04-26 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 19:07 Bruce Rogers [this message]
2017-04-27 9:11 ` [Qemu-devel] [PATCH] ACPI: call acpi_set_pci_info when only acpi enabled Igor Mammedov
2017-04-27 15:44 ` Bruce Rogers
2017-04-27 16:08 ` Igor Mammedov
2017-04-27 16:29 ` Bruce Rogers
2017-04-27 16:51 ` Bruce Rogers
2017-04-27 17:35 ` Igor Mammedov
2017-04-27 18:08 ` Stefano Stabellini
2017-04-27 19:57 ` Bruce Rogers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1493233622-14485-1-git-send-email-brogers@suse.com \
--to=brogers@suse.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=sstabellini@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).