From: "Michael S. Tsirkin" <mst@redhat.com>
To: Wei Yang <richardw.yang@linux.intel.com>
Cc: yang.zhong@intel.com, peter.maydell@linaro.org, thuth@redhat.com,
qemu-devel@nongnu.org, shannon.zhaosl@gmail.com,
qemu-arm@nongnu.org, imammedo@redhat.com, philmd@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 0/6] Extract build_mcfg
Date: Mon, 20 May 2019 18:55:53 -0400 [thread overview]
Message-ID: <20190520185508-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190520005957.6953-1-richardw.yang@linux.intel.com>
On Mon, May 20, 2019 at 08:59:51AM +0800, Wei Yang wrote:
> This patch set tries to generalize MCFG table build process. And it is
> based on one un-merged patch from Igor, which is included in this serials.
>
> v4->v5:
> * ACPI_PCI depends on both ACPI and PCI
> * rebase on latest master, adjust arm Kconfig
> * miss the reserved[8] of MCFG, add it back
> * make sure bios-tables-test all OK
So I am merging 1-4 now - they are unchanged from previous iterations.
You just need to repost 5-6.
> v3->v4:
> * adjust comment to give more information about MCFG table
>
> v2->v3:
> * Includes the un-merged patch from Igor
> * use build_append_foo() API to construct MCFG
>
> Igor Mammedov (1):
> q35: acpi: do not create dummy MCFG table
>
> Wei Yang (5):
> hw/arm/virt-acpi-build: remove unnecessary variable mcfg_start
> i386, acpi: remove mcfg_ prefix in AcpiMcfgInfo members
> hw/arm/virt-acpi-build: pass AcpiMcfgInfo to build_mcfg()
> hw/acpi: Consolidate build_mcfg to pci.c
> acpi: pci: use build_append_foo() API to construct MCFG
>
> default-configs/i386-softmmu.mak | 1 +
> hw/acpi/Kconfig | 4 +++
> hw/acpi/Makefile.objs | 1 +
> hw/acpi/pci.c | 57 ++++++++++++++++++++++++++++++++
> hw/arm/Kconfig | 1 +
> hw/arm/virt-acpi-build.c | 31 +++++------------
> hw/i386/acpi-build.c | 44 ++++--------------------
> include/hw/acpi/acpi-defs.h | 18 ----------
> include/hw/acpi/pci.h | 34 +++++++++++++++++++
> 9 files changed, 113 insertions(+), 78 deletions(-)
> create mode 100644 hw/acpi/pci.c
> create mode 100644 include/hw/acpi/pci.h
>
> --
> 2.19.1
next prev parent reply other threads:[~2019-05-20 22:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 0:59 [Qemu-devel] [PATCH v5 0/6] Extract build_mcfg Wei Yang
2019-05-20 0:59 ` [Qemu-devel] [PATCH v5 1/6] q35: acpi: do not create dummy MCFG table Wei Yang
2019-05-20 0:59 ` [Qemu-devel] [PATCH v5 2/6] hw/arm/virt-acpi-build: remove unnecessary variable mcfg_start Wei Yang
2019-05-20 0:59 ` [Qemu-devel] [PATCH v5 3/6] i386, acpi: remove mcfg_ prefix in AcpiMcfgInfo members Wei Yang
2019-05-20 0:59 ` [Qemu-devel] [PATCH v5 4/6] hw/arm/virt-acpi-build: pass AcpiMcfgInfo to build_mcfg() Wei Yang
2019-05-20 0:59 ` [Qemu-devel] [PATCH v5 5/6] hw/acpi: Consolidate build_mcfg to pci.c Wei Yang
2019-05-20 2:26 ` Wei Yang
2019-05-20 0:59 ` [Qemu-devel] [PATCH v5 6/6] acpi: pci: use build_append_foo() API to construct MCFG Wei Yang
2019-05-20 22:55 ` Michael S. Tsirkin [this message]
2019-05-21 3:16 ` [Qemu-devel] [PATCH v5 0/6] Extract build_mcfg 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=20190520185508-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=imammedo@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richardw.yang@linux.intel.com \
--cc=shannon.zhaosl@gmail.com \
--cc=thuth@redhat.com \
--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).