From: Laszlo Ersek <lersek@redhat.com>
To: qemu-devel@nongnu.org
Cc: Aleksei Kovura <alex3kov@zoho.com>,
Xiao Guangrong <guangrong.xiao@linux.intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Shannon Zhao <zhaoshenglong@huawei.com>,
Michael Tokarev <mjt@tls.msk.ru>,
"Richard W.M. Jones" <rjones@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: [Qemu-devel] [PATCH 0/4] set the OEM fields in the RSDT and the FADT from the SLIC
Date: Thu, 14 Jan 2016 02:36:53 +0100 [thread overview]
Message-ID: <1452735417-5461-1-git-send-email-lersek@redhat.com> (raw)
Background:
- https://bugzilla.redhat.com/show_bug.cgi?id=1248758
- http://thread.gmane.org/gmane.comp.emulators.qemu/358854
- https://github.com/tianocore/edk2/issues/5
This matters mostly for Win7 installations that were converted with p2v.
Testing feedback from such environments would be appreciated.
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Aleksei Kovura <alex3kov@zoho.com>
Cc: Igor Mammedov <imammedo@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Richard W.M. Jones <rjones@redhat.com>
Cc: Shannon Zhao <zhaoshenglong@huawei.com>
Cc: Xiao Guangrong <guangrong.xiao@linux.intel.com>
Thanks
Laszlo
Laszlo Ersek (4):
acpi: take oem_id in build_header(), optionally
acpi: expose oem_id and oem_table_id in build_rsdt()
acpi: stash the OEM ID and OEM Table ID fields from an external SLIC
table
pc: set the OEM fields in the RSDT and the FADT from the SLIC
include/hw/acpi/acpi.h | 2 ++
include/hw/acpi/aml-build.h | 5 +++--
include/hw/i386/pc.h | 2 ++
hw/acpi/aml-build.c | 14 ++++++++++----
hw/acpi/core.c | 18 ++++++++++++++++++
hw/acpi/nvdimm.c | 4 ++--
hw/arm/virt-acpi-build.c | 14 +++++++-------
hw/i386/acpi-build.c | 40 +++++++++++++++++++++++++++-------------
hw/i386/pc.c | 19 +++++++++++++++++++
qemu-options.hx | 10 +++++++++-
10 files changed, 99 insertions(+), 29 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-01-14 1:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 1:36 Laszlo Ersek [this message]
2016-01-14 1:36 ` [Qemu-devel] [PATCH 1/4] acpi: take oem_id in build_header(), optionally Laszlo Ersek
2016-01-14 1:36 ` [Qemu-devel] [PATCH 2/4] acpi: expose oem_id and oem_table_id in build_rsdt() Laszlo Ersek
2016-01-14 1:36 ` [Qemu-devel] [PATCH 3/4] acpi: stash the OEM ID and OEM Table ID fields from an external SLIC table Laszlo Ersek
2016-01-14 10:21 ` Michael S. Tsirkin
2016-01-14 16:38 ` Laszlo Ersek
2016-01-14 1:36 ` [Qemu-devel] [PATCH 4/4] pc: set the OEM fields in the RSDT and the FADT from the SLIC Laszlo Ersek
2016-01-14 10:24 ` Michael S. Tsirkin
2016-01-14 16:44 ` Laszlo Ersek
2016-01-14 17:09 ` Laszlo Ersek
2016-01-14 10:03 ` [Qemu-devel] [PATCH 0/4] " Richard W.M. Jones
2016-01-14 10:06 ` Alex
2016-01-14 10:23 ` Richard W.M. Jones
2016-01-14 16:35 ` Laszlo Ersek
2016-01-15 16:07 ` Richard W.M. Jones
2016-01-15 16:13 ` Alex
2016-01-21 11:37 ` Richard W.M. Jones
2016-01-21 11:42 ` Michael Tokarev
2016-01-21 11:44 ` Richard W.M. Jones
2016-01-21 11:55 ` Laszlo Ersek
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=1452735417-5461-1-git-send-email-lersek@redhat.com \
--to=lersek@redhat.com \
--cc=alex3kov@zoho.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=imammedo@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=zhaoshenglong@huawei.com \
/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).