From: "Laszlo Ersek \(Red Hat\)" <lersek@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1821884] Re: Extend uefi-test-tools to report SMBIOS location
Date: Thu, 25 Apr 2019 10:44:38 -0000 [thread overview]
Message-ID: <155618907848.13732.2820561783658874691.malone@wampee.canonical.com> (raw)
In-Reply-To: 155368089372.19244.12131435230778764037.malonedeb@chaenomeles.canonical.com
Posted
[PATCH 0/2] tests/uefi-test-tools: report the SMBIOS entry point structures
http://mid.mail-archive.com/20190425104326.12835-1-lersek@redhat.com
** Changed in: qemu
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1821884
Title:
Extend uefi-test-tools to report SMBIOS location
Status in QEMU:
In Progress
Bug description:
UEFI helper app exposes the pointer to RSDP ACPI table that firmware allocates in guest's RAM
but it doesn't do so for SMBIOS tables. Hence bios table test would skip testing SMBIOS tables
to workaround shortcoming. This bug is a request to expose two new entry point fields (one for SMBIOS 2 and another for SMBIOS 3) so test could check SMBIOS tables when guest is started a with UEFI firmware.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1821884/+subscriptions
next parent reply other threads:[~2019-04-25 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <155368089372.19244.12131435230778764037.malonedeb@chaenomeles.canonical.com>
2019-04-25 10:44 ` Laszlo Ersek (Red Hat) [this message]
2019-04-25 10:44 ` [Qemu-devel] [Bug 1821884] Re: Extend uefi-test-tools to report SMBIOS location Laszlo Ersek (Red Hat)
2019-05-03 9:32 ` Laszlo Ersek (Red Hat)
2019-05-03 9:32 ` Laszlo Ersek (Red Hat)
2019-05-06 16:21 ` Laszlo Ersek (Red Hat)
2019-08-16 4:48 ` Thomas Huth
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=155618907848.13732.2820561783658874691.malone@wampee.canonical.com \
--to=lersek@redhat.com \
--cc=1821884@bugs.launchpad.net \
--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).