From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrange" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Michael Roth" <mdroth@linux.vnet.ibm.com>,
qemu-arm@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Ani Sinha" <ani@anisinha.ca>,
"Igor Mammedov" <imammedo@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PATCH v3 0/3] pc: Support configuration of SMBIOS entry point type
Date: Tue, 26 Oct 2021 11:10:57 -0400 [thread overview]
Message-ID: <20211026151100.1691925-1-ehabkost@redhat.com> (raw)
This includes code previously submitted[1] by Daniel P. Berrangé
to add a "smbios-ep" machine property on PC.
SMBIOS 3.0 is necessary to support more than ~720 VCPUs, as a
large number of VCPUs can easily hit the table size limit of
SMBIOS 2.1 entry points.
Changes from v2:
* Renamed option to "smbios-entry-point-type" for clarity
* Renamed option values to "32" and "64", for two reasons:
* The option is not about reporting an exact SMBIOS
version, but just the entry point format.
FWIW, the SMBIOS specification uses the phrases "32-bit entry
point" and "64-bit entry point" more often than "2.1 entry
point" and "3.0 entry point".
* QAPI doesn't allow us to use enum member names with dots
or underscores
[1] https://lore.kernel.org/qemu-devel/20200908165438.1008942-5-berrange@redhat.com
https://lore.kernel.org/qemu-devel/20200908165438.1008942-6-berrange@redhat.com
Eduardo Habkost (3):
smbios: Rename SMBIOS_ENTRY_POINT_* enums
hw/smbios: Use qapi for SmbiosEntryPointType
hw/i386: expose a "smbios-entry-point-type" PC machine property
include/hw/firmware/smbios.h | 10 ++--------
include/hw/i386/pc.h | 4 ++++
hw/arm/virt.c | 2 +-
hw/i386/pc.c | 26 ++++++++++++++++++++++++++
hw/i386/pc_piix.c | 2 +-
hw/i386/pc_q35.c | 2 +-
hw/smbios/smbios.c | 8 ++++----
qapi/machine.json | 12 ++++++++++++
8 files changed, 51 insertions(+), 15 deletions(-)
--
2.32.0
next reply other threads:[~2021-10-26 15:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 15:10 Eduardo Habkost [this message]
2021-10-26 15:10 ` [PATCH v3 1/3] smbios: Rename SMBIOS_ENTRY_POINT_* enums Eduardo Habkost
2021-10-26 15:13 ` Philippe Mathieu-Daudé
2021-10-27 7:43 ` Michael S. Tsirkin
2021-10-27 14:23 ` Eduardo Habkost
2021-10-26 15:10 ` [PATCH v3 2/3] hw/smbios: Use qapi for SmbiosEntryPointType Eduardo Habkost
2021-10-26 15:14 ` Philippe Mathieu-Daudé
2021-11-03 10:03 ` Markus Armbruster
2021-10-26 15:11 ` [PATCH v3 3/3] hw/i386: expose a "smbios-entry-point-type" PC machine property Eduardo Habkost
2021-11-02 8:51 ` Philippe Mathieu-Daudé
2021-11-02 11:25 ` Michael S. Tsirkin
2021-11-10 22:06 ` Eduardo Habkost
2021-11-22 9:08 ` Gerd Hoffmann
2021-11-01 22:32 ` [PATCH v3 0/3] pc: Support configuration of SMBIOS entry point type Michael S. Tsirkin
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=20211026151100.1691925-1-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=ani@anisinha.ca \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=imammedo@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).