qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: qemu-devel@nongnu.org
Cc: Aleksei Kovura <alex3kov@zoho.com>,
	Xiao Guangrong <guangrong.xiao@linux.intel.com>,
	Steven Newbury <steve@snewbury.org.uk>,
	"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 v2 0/4] set the OEM fields in the RSDT and the FADT from the SLIC
Date: Mon, 18 Jan 2016 15:12:09 +0100	[thread overview]
Message-ID: <1453126333-19474-1-git-send-email-lersek@redhat.com> (raw)

This is version 2 of
<http://thread.gmane.org/gmane.comp.emulators.qemu/386728>.

Changes in v2 (also annotated per patch):
- introduce acpi_get_slic_oem() [MST],
- drop machine property that disables the SLIC-based override [MST].

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: Steven Newbury <steve@snewbury.org.uk>
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: add function to extract oem_id and oem_table_id from the user's
    SLIC
  pc: set the OEM fields in the RSDT and the FADT from the SLIC

 include/hw/acpi/acpi.h      |  7 +++++++
 include/hw/acpi/aml-build.h |  5 +++--
 hw/acpi/aml-build.c         | 14 ++++++++++----
 hw/acpi/core.c              | 16 ++++++++++++++++
 hw/acpi/nvdimm.c            |  4 ++--
 hw/arm/virt-acpi-build.c    | 14 +++++++-------
 hw/i386/acpi-build.c        | 31 ++++++++++++++++++-------------
 qemu-options.hx             |  4 ++++
 8 files changed, 67 insertions(+), 28 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2016-01-18 14:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 14:12 Laszlo Ersek [this message]
2016-01-18 14:12 ` [Qemu-devel] [PATCH v2 1/4] acpi: take oem_id in build_header(), optionally Laszlo Ersek
2016-01-19  3:27   ` Shannon Zhao
2016-01-18 14:12 ` [Qemu-devel] [PATCH v2 2/4] acpi: expose oem_id and oem_table_id in build_rsdt() Laszlo Ersek
2016-01-19  3:29   ` Shannon Zhao
2016-01-18 14:12 ` [Qemu-devel] [PATCH v2 3/4] acpi: add function to extract oem_id and oem_table_id from the user's SLIC Laszlo Ersek
2016-01-18 14:12 ` [Qemu-devel] [PATCH v2 4/4] pc: set the OEM fields in the RSDT and the FADT from the SLIC Laszlo Ersek
2016-01-19  7:35 ` [Qemu-devel] [PATCH v2 0/4] " Steven Newbury
2016-01-19  7:40   ` Steven Newbury
2016-01-27 18:31 ` Laszlo Ersek
2016-02-03 18:51   ` Laszlo Ersek
2016-02-03 19:02     ` Michael Tokarev
2016-02-03 19:45       ` Laszlo Ersek
2016-02-03 20:37       ` Richard W.M. Jones

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=1453126333-19474-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=steve@snewbury.org.uk \
    --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).