From: Andrew Jones <drjones@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Wei Huang <wei@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Eduardo Habkost <ehabkost@redhat.com>,
Ivan Khoronzhuk <ivan.khoronzhuk@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Gabriel L. Somlo" <somlo@cmu.edu>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Shannon Zhao <zhaoshenglong@huawei.co>,
QEMU Developers <qemu-devel@nongnu.org>,
Roy Franz <roy.franz@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [ARM SMBIOS V1 PATCH 0/6] SMBIOS Support for ARM
Date: Thu, 6 Aug 2015 14:41:20 +0200 [thread overview]
Message-ID: <20150806124120.GB3083@hawk.localdomain> (raw)
In-Reply-To: <55C25764.9090302@redhat.com>
On Wed, Aug 05, 2015 at 08:35:16PM +0200, Laszlo Ersek wrote:
> On 08/05/15 19:35, Peter Maydell wrote:
> > On 5 August 2015 at 18:16, Laszlo Ersek <lersek@redhat.com> wrote:
> >> On 07/28/15 08:00, Wei Huang wrote:
[...]
> SMBIOS is usually not needed by the guest OS or the firmware. The spec says,
I think SMBIOS is the only way we can expose to an ACPI-booted ARM
guest (without heuristics) that it's a QEMU/KVM guest. While that
information isn't useful in most cases, and we should do our best to
avoid its need in almost all cases, there are times it's nice to have
(or necessary for distros...)
drew
next prev parent reply other threads:[~2015-08-06 12:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 6:00 [Qemu-devel] [ARM SMBIOS V1 PATCH 0/6] SMBIOS Support for ARM Wei Huang
2015-07-28 6:00 ` [Qemu-devel] [ARM SMBIOS V1 PATCH 1/6] smbios: extract x86 smbios building code into a function Wei Huang
2015-07-28 6:00 ` [Qemu-devel] [ARM SMBIOS V1 PATCH 2/6] smbios: remove dependency on x86 e820 tables Wei Huang
2015-07-28 6:00 ` [Qemu-devel] [ARM SMBIOS V1 PATCH 3/6] smbios: pass ram size as a parameter to build smbios tables Wei Huang
2015-07-28 6:00 ` [Qemu-devel] [ARM SMBIOS V1 PATCH 4/6] smbios: move smbios code into a common folder Wei Huang
2015-07-28 6:00 ` [Qemu-devel] [ARM SMBIOS V1 PATCH 5/6] smbios: add smbios 3.0 support Wei Huang
2015-07-31 17:12 ` Laszlo Ersek
2015-07-28 6:00 ` [Qemu-devel] [ARM SMBIOS V1 PATCH 6/6] smbios: implement smbios support for mach-virt Wei Huang
2015-07-31 2:11 ` Shannon Zhao
2015-07-31 6:08 ` Wei Huang
2015-08-05 17:16 ` [Qemu-devel] [ARM SMBIOS V1 PATCH 0/6] SMBIOS Support for ARM Laszlo Ersek
2015-08-05 17:35 ` Peter Maydell
2015-08-05 18:35 ` Laszlo Ersek
2015-08-05 19:39 ` Ivan Khoronzhuk
2015-08-05 22:03 ` Jean Delvare
2015-08-06 8:07 ` Laszlo Ersek
2015-08-06 8:16 ` Ivan Khoronzhuk
2015-08-06 11:20 ` Jean Delvare
2015-08-10 7:43 ` [Qemu-devel] dmidecode repository (Was: [ARM SMBIOS V1 PATCH 0/6] SMBIOS Support for ARM) Jean Delvare
2015-08-10 11:58 ` Laszlo Ersek
2015-08-10 12:26 ` Jean Delvare
2015-08-10 15:08 ` Laszlo Ersek
2015-08-06 12:41 ` Andrew Jones [this message]
2015-08-07 11:12 ` [Qemu-devel] [ARM SMBIOS V1 PATCH 0/6] SMBIOS Support for ARM Ard Biesheuvel
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=20150806124120.GB3083@hawk.localdomain \
--to=drjones@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=ivan.khoronzhuk@linaro.org \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=roy.franz@linaro.org \
--cc=rth@twiddle.net \
--cc=somlo@cmu.edu \
--cc=wei@redhat.com \
--cc=zhaoshenglong@huawei.co \
/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).