From: Igor Mammedov <imammedo@redhat.com>
To: Wei Yang <richardw.yang@linux.intel.com>
Cc: yang.zhong@intel.com, ehabkost@redhat.com, mst@redhat.com,
qemu-devel@nongnu.org, pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [RFC PATCH 0/9] hw/acpi: make build_madt arch agnostic
Date: Tue, 18 Jun 2019 17:59:56 +0200 [thread overview]
Message-ID: <20190618175956.4373ac7e@redhat.com> (raw)
In-Reply-To: <20190513061913.9284-1-richardw.yang@linux.intel.com>
On Mon, 13 May 2019 14:19:04 +0800
Wei Yang <richardw.yang@linux.intel.com> wrote:
> Now MADT is highly depend in architecture and machine type and leaves
> duplicated code in different architecture. The series here tries to generalize
> it.
>
> MADT contains one main table and several sub tables. These sub tables are
> highly related to architecture. Here we introduce one method to make it
> architecture agnostic.
>
> * each architecture define its sub-table implementation function in madt_sub
> * introduces struct madt_input to collect sub table information and pass to
> build_madt
>
> By doing so, each architecture could prepare its own sub-table implementation
> and madt_input. And keep build_madt architecture agnostic.
I've skimmed over patches, and to me it looks mostly as code movement
without apparent benefits and probably a bit more complex than what we have now
(it might be ok cost if it simplifies MADT support for other boards).
Before I do line by line review could you demonstrate what effect new way
to build MADT would have on arm/virt and i386/virt (from NEMU). So it would be
possible to estimate net benefits from new approach?
(PS: it doesn't have to be patches ready for merging, just a dirty hack
that would demonstrate adding MADT for new board using mad_sub[])
>
> Wei Yang (9):
> hw/acpi: expand pc_madt_cpu_entry in place
> hw/acpi: implement madt_sub[ACPI_APIC_PROCESSOR]
> hw/acpi: implement madt_sub[ACPI_APIC_LOCAL_X2APIC]
> hw/acpi: implement madt_sub[ACPI_APIC_IO]
> hw/acpi: implement madt_sub[ACPI_APIC_XRUPT_OVERRIDE]
> hw/acpi: implement madt_sub[ACPI_APIC_LOCAL_X2APIC_NMI]
> hw/acpi: implement madt_sub[ACPI_APIC_LOCAL_NMI]
> hw/acpi: factor build_madt with madt_input
> hw/acpi: implement madt_main to manipulate main madt table
>
> hw/acpi/cpu.c | 14 +-
> hw/acpi/piix4.c | 3 +-
> hw/i386/acpi-build.c | 265 +++++++++++++++++----------
> hw/isa/lpc_ich9.c | 3 +-
> include/hw/acpi/acpi_dev_interface.h | 12 +-
> include/hw/i386/pc.h | 2 +
> 6 files changed, 194 insertions(+), 105 deletions(-)
>
next prev parent reply other threads:[~2019-06-18 16:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 6:19 [Qemu-devel] [RFC PATCH 0/9] hw/acpi: make build_madt arch agnostic Wei Yang
2019-05-13 6:19 ` [Qemu-devel] [RFC PATCH 1/9] hw/acpi: expand pc_madt_cpu_entry in place Wei Yang
2019-05-13 6:19 ` [Qemu-devel] [RFC PATCH 2/9] hw/acpi: implement madt_sub[ACPI_APIC_PROCESSOR] Wei Yang
2019-05-13 6:19 ` [Qemu-devel] [RFC PATCH 3/9] hw/acpi: implement madt_sub[ACPI_APIC_LOCAL_X2APIC] Wei Yang
2019-05-13 6:19 ` [Qemu-devel] [RFC PATCH 4/9] hw/acpi: implement madt_sub[ACPI_APIC_IO] Wei Yang
2019-05-13 6:19 ` [Qemu-devel] [RFC PATCH 5/9] hw/acpi: implement madt_sub[ACPI_APIC_XRUPT_OVERRIDE] Wei Yang
2019-05-13 6:19 ` [Qemu-devel] [RFC PATCH 6/9] hw/acpi: implement madt_sub[ACPI_APIC_LOCAL_X2APIC_NMI] Wei Yang
2019-05-13 6:19 ` [Qemu-devel] [RFC PATCH 7/9] hw/acpi: implement madt_sub[ACPI_APIC_LOCAL_NMI] Wei Yang
2019-05-13 6:19 ` [Qemu-devel] [RFC PATCH 8/9] hw/acpi: factor build_madt with madt_input Wei Yang
2019-05-13 6:19 ` [Qemu-devel] [RFC PATCH 9/9] hw/acpi: implement madt_main to manipulate main madt table Wei Yang
2019-06-03 6:22 ` [Qemu-devel] [RFC PATCH 0/9] hw/acpi: make build_madt arch agnostic Wei Yang
2019-06-18 15:59 ` Igor Mammedov [this message]
2019-06-19 6:20 ` Wei Yang
2019-06-19 9:04 ` Igor Mammedov
2019-06-20 14:18 ` Wei Yang
2019-06-20 15:04 ` Igor Mammedov
2019-06-21 0:56 ` Wei Yang
2019-06-21 8:11 ` Igor Mammedov
2019-06-21 21:33 ` Wei Yang
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=20190618175956.4373ac7e@redhat.com \
--to=imammedo@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richardw.yang@linux.intel.com \
--cc=rth@twiddle.net \
--cc=yang.zhong@intel.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).