qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Glauber Costa <glommer@redhat.com>
To: bochs-developers@lists.sourceforge.net
Cc: aliguori@us.ibm.com, Avi Kivity <avi@redhat.com>,
	qemu-devel@nongnu.org, Glauber Costa <gcosta@redhat.com>
Subject: [Qemu-devel] [PATCH 2/2] kvm: bios: remove acpi_build_processor_ssdt
Date: Fri, 17 Apr 2009 16:57:40 -0400	[thread overview]
Message-ID: <1240001860-2280-3-git-send-email-glommer@redhat.com> (raw)
In-Reply-To: <1240001860-2280-2-git-send-email-glommer@redhat.com>

From: Glauber Costa <gcosta@redhat.com>

It is now present in the dsdt, provided by acpi-dst.dsl, so having it
in here confuses things.

Signed-off-by: Glauber Costa <gcosta@redhat.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
---
 bios/rombios32.c |   11 +++++------
 1 files changed, 5 insertions(+), 6 deletions(-)

diff --git a/bios/rombios32.c b/bios/rombios32.c
index 3c7757b..cf6610d 100644
--- a/bios/rombios32.c
+++ b/bios/rombios32.c
@@ -1251,9 +1251,9 @@ struct rsdt_descriptor_rev1
 {
 	ACPI_TABLE_HEADER_DEF                           /* ACPI common table header */
 #ifdef BX_QEMU
-	uint32_t                             table_offset_entry [4]; /* Array of pointers to other */
-#else
 	uint32_t                             table_offset_entry [3]; /* Array of pointers to other */
+#else
+	uint32_t                             table_offset_entry [2]; /* Array of pointers to other */
 #endif
 			 /* ACPI tables */
 } __attribute__((__packed__));
@@ -1494,12 +1494,12 @@ void acpi_bios_init(void)
     struct fadt_descriptor_rev1 *fadt;
     struct facs_descriptor_rev1 *facs;
     struct multiple_apic_table *madt;
-    uint8_t *dsdt, *ssdt;
+    uint8_t *dsdt;
 #ifdef BX_QEMU
     struct acpi_20_hpet *hpet;
     uint32_t hpet_addr;
 #endif
-    uint32_t base_addr, rsdt_addr, fadt_addr, addr, facs_addr, dsdt_addr, ssdt_addr;
+    uint32_t base_addr, rsdt_addr, fadt_addr, addr, facs_addr, dsdt_addr;
     uint32_t acpi_tables_size, madt_addr, madt_size;
     int i;
 
@@ -1573,9 +1573,8 @@ void acpi_bios_init(void)
     memset(rsdt, 0, sizeof(*rsdt));
     rsdt->table_offset_entry[0] = cpu_to_le32(fadt_addr);
     rsdt->table_offset_entry[1] = cpu_to_le32(madt_addr);
-    rsdt->table_offset_entry[2] = cpu_to_le32(ssdt_addr);
 #ifdef BX_QEMU
-    rsdt->table_offset_entry[3] = cpu_to_le32(hpet_addr);
+    rsdt->table_offset_entry[2] = cpu_to_le32(hpet_addr);
 #endif
     acpi_build_table_header((struct acpi_table_header *)rsdt,
                             "RSDT", sizeof(*rsdt), 1);
-- 
1.5.6.6

  reply	other threads:[~2009-04-17 20:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 20:57 [Qemu-devel] [PATCH 0/2] CPU hotplug support Glauber Costa
2009-04-17 20:57 ` [Qemu-devel] [PATCH 1/2] create acpi cpu definitions Glauber Costa
2009-04-17 20:57   ` Glauber Costa [this message]
2009-04-18 21:50   ` [Qemu-devel] Re: [Bochs-developers] " Sebastian Herbszt
2009-04-19  1:31     ` Brendan Trotter
2009-04-19 11:12       ` Gleb Natapov
2009-04-19 14:04         ` Brendan Trotter
2009-04-19 21:55         ` Sebastian Herbszt
2009-04-20  5:28           ` Gleb Natapov

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=1240001860-2280-3-git-send-email-glommer@redhat.com \
    --to=glommer@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=bochs-developers@lists.sourceforge.net \
    --cc=gcosta@redhat.com \
    --cc=qemu-devel@nongnu.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).