From: Laszlo Ersek <lersek@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>,
Kevin O'Connor <kevin@koconnor.net>
Cc: kraxel@redhat.com, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH 00/11] build ACPI MADT for fw_cfg clients
Date: Thu, 04 Apr 2013 09:52:31 +0200 [thread overview]
Message-ID: <515D313F.4010109@redhat.com> (raw)
In-Reply-To: <87hajncrcr.fsf@codemonkey.ws>
(adding Kevin)
On 04/03/13 22:05, Anthony Liguori wrote:
> Laszlo Ersek <lersek@redhat.com> writes:
>
>> On 03/21/13 00:23, Laszlo Ersek wrote:
>>> This series reworks the internals of the -acpitable command line option,
>>> and if that option is not specified, produces the APIC (MADT) table
>>> inside qemu, to be consumed over fw_cfg (alongside the DSDT).
>>
>>> Laszlo Ersek (11):
>>> strip some whitespace
>>> change element type from "char" to "unsigned char" in ACPI table data
>>> acpi_table_add(): report fatal errors through an internal Error
>>> object
>>> qapi schema: add AcpiTableOptions
>>> acpi_table_add(): accept QemuOpts and parse it with OptsVisitor
>>> acpi_table_add(): extract and reimplement internals
>>> like acpi_table_install(), acpi_table_add() should propagate Errors
>>> extract/unify the constant 0xfee00000 as APIC_DEFAULT_ADDRESS
>>> Introduce IO_APIC_DEFAULT_ADDRESS for 0xfec00000
>>> pc_acpi_init(): don't bail as soon as failing to find default DSDT
>>> i386/pc: build ACPI MADT for fw_cfg clients
>>
>> Any chance patches 01 to 09 could be considered? Esp. 06 which removes
>> an out-of-bounds access (an innocent-looking one, admittedly).
>>
>> I'm OK too if the series is dropped (patch 11 was the main motivation,
>> but the interface that it extends was deemed unsuitable going forward on
>> the seabios list). I'd just like to hear the maintainer with
>> jurisdiction say the NAK. ("Too expensive even to review for too little
>> gain" is a good reason.)
>
> The whole thing looks pretty nice to me.
That's awesome, thank you very much!
> I'll merge the full series in
> a day or so unless anyone objects.
For transparency's sake: Kevin, this is where you'd object to patch 11:
it adds an MADT to the existing fw_cfg blob, which, combined with an
older (=current) SeaBIOS, leads to a duplicated MADT; see also the blurb
in 00/11 which quotes that from
<http://www.seabios.org/pipermail/seabios/2013-March/005960.html>. (I'm
adding this paragraph because you can argue this better; I yet have to
go through your detailed design
<http://www.seabios.org/pipermail/seabios/2013-March/006020.html> once
more.)
Anyway, if you could tolerate such a duplicate MADT for a very short
time, I'd send a qemu patch that reworks pc_acpi_madt() (in 11/11), such
that it's final call is not made to acpi_table_install() -- ie.
appending the MADT to the existing fw_cfg ACPI blob --, but installs it
as a separate fw_cfg file as you're suggesting (/etc/acpi/APIC or so) --
the existing "-acpitable" switch would still benefit from 01-10, and I'd
salvage the meat of 11/11 as well. I'd then attempt to write a SeaBIOS
patch too for /etc/acpi/APIC. Would that be acceptable for you?
> This is an under maintained area of QEMU so it's very nice to see
> improvements!
>
> Reviewed-by: Anthony Liguori <aliguori@us.ibm.com>
Can't thank enough for your quick response, Anthony.
Laszlo
next prev parent reply other threads:[~2013-04-04 7:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 23:23 [Qemu-devel] [PATCH 00/11] build ACPI MADT for fw_cfg clients Laszlo Ersek
2013-03-20 23:23 ` [Qemu-devel] [PATCH 01/11] strip some whitespace Laszlo Ersek
2013-03-20 23:23 ` [Qemu-devel] [PATCH 02/11] change element type from "char" to "unsigned char" in ACPI table data Laszlo Ersek
2013-03-20 23:40 ` Eric Blake
2013-03-21 0:18 ` Laszlo Ersek
2013-03-20 23:23 ` [Qemu-devel] [PATCH 03/11] acpi_table_add(): report fatal errors through an internal Error object Laszlo Ersek
2013-03-20 23:23 ` [Qemu-devel] [PATCH 04/11] qapi schema: add AcpiTableOptions Laszlo Ersek
2013-03-20 23:45 ` Eric Blake
2013-03-21 0:31 ` Laszlo Ersek
2013-03-21 10:41 ` Laszlo Ersek
2013-03-21 11:51 ` Paolo Bonzini
2013-03-21 12:36 ` Michael S. Tsirkin
2013-03-21 12:42 ` Laszlo Ersek
2013-03-21 12:44 ` Paolo Bonzini
2013-04-03 19:59 ` Anthony Liguori
2013-04-03 20:01 ` Anthony Liguori
2013-03-20 23:23 ` [Qemu-devel] [PATCH 05/11] acpi_table_add(): accept QemuOpts and parse it with OptsVisitor Laszlo Ersek
2013-03-20 23:23 ` [Qemu-devel] [PATCH 06/11] acpi_table_add(): extract and reimplement internals Laszlo Ersek
2013-03-20 23:23 ` [Qemu-devel] [PATCH 07/11] like acpi_table_install(), acpi_table_add() should propagate Errors Laszlo Ersek
2013-03-20 23:23 ` [Qemu-devel] [PATCH 08/11] extract/unify the constant 0xfee00000 as APIC_DEFAULT_ADDRESS Laszlo Ersek
2013-03-20 23:23 ` [Qemu-devel] [PATCH 09/11] Introduce IO_APIC_DEFAULT_ADDRESS for 0xfec00000 Laszlo Ersek
2013-03-20 23:23 ` [Qemu-devel] [PATCH 10/11] pc_acpi_init(): don't bail as soon as failing to find default DSDT Laszlo Ersek
2013-03-20 23:23 ` [Qemu-devel] [PATCH 11/11] i386/pc: build ACPI MADT for fw_cfg clients Laszlo Ersek
2013-04-03 16:44 ` [Qemu-devel] [PATCH 00/11] " Laszlo Ersek
2013-04-03 20:05 ` Anthony Liguori
2013-04-04 7:52 ` Laszlo Ersek [this message]
2013-04-04 23:22 ` Kevin O'Connor
2013-04-05 11:39 ` Laszlo Ersek
2013-04-05 12:51 ` Anthony Liguori
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=515D313F.4010109@redhat.com \
--to=lersek@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kevin@koconnor.net \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--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).