From: Shannon Zhao <zhaoshenglong@huawei.com>
To: Andrew Jones <drjones@redhat.com>
Cc: qemu-arm@nongnu.org, peter.maydell@linaro.org,
"Michael S. Tsirkin" <mst@redhat.com>,
david.daney@cavium.com, peter.huangpeng@huawei.com,
qemu-devel@nongnu.org, shannon.zhao@linaro.org,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 4/5] ACPI: move acpi_build_srat_memory to common place
Date: Mon, 25 Apr 2016 15:50:53 +0800 [thread overview]
Message-ID: <571DCC5D.8010405@huawei.com> (raw)
In-Reply-To: <20160424170049.mxfial3f5xbmfmxs@hawk.localdomain>
On 2016/4/25 1:00, Andrew Jones wrote:
> On Sat, Apr 23, 2016 at 05:06:35PM +0800, Shannon Zhao wrote:
>> > From: Shannon Zhao <shannon.zhao@linaro.org>
>> >
>> > Move acpi_build_srat_memory to common place so that it could be reused
>> > by ARM.
>> >
>> > Cc: Michael S. Tsirkin <mst@redhat.com>
>> > Cc: Igor Mammedov <imammedo@redhat.com>
>> > Signed-off-by: Shannon Zhao <shannon.zhao@linaro.org>
>> > ---
>> > hw/acpi/aml-build.c | 12 ++++++++++++
>> > hw/i386/acpi-build.c | 20 --------------------
>> > include/hw/acpi/aml-build.h | 10 ++++++++++
>> > 3 files changed, 22 insertions(+), 20 deletions(-)
>> >
>> > diff --git a/hw/acpi/aml-build.c b/hw/acpi/aml-build.c
>> > index ab89ca6..d167003 100644
>> > --- a/hw/acpi/aml-build.c
>> > +++ b/hw/acpi/aml-build.c
>> > @@ -1563,3 +1563,15 @@ build_rsdt(GArray *table_data, GArray *linker, GArray *table_offsets,
>> > build_header(linker, table_data,
>> > (void *)rsdt, "RSDT", rsdt_len, 1, oem_id, oem_table_id);
>> > }
>> > +
>> > +void acpi_build_srat_memory(AcpiSratMemoryAffinity *numamem, uint64_t base,
>> > + uint64_t len, int node, MemoryAffinityFlags flags)
> It looks like functions like these in hw/acpi/aml-build.c usually start
> with 'build_' not 'acpi_'
>
Ok, I will rename it to build_acpi_srat_memory.
>> > +{
>> > + numamem->type = ACPI_SRAT_MEMORY;
>> > + numamem->length = sizeof(*numamem);
>> > + memset(numamem->proximity, 0, 4);
> This memset thing is still weird...
>
I will add a patch before this one to fix the definition of proximity
and use uint32_t as you said before.
Thanks,
--
Shannon
next prev parent reply other threads:[~2016-04-25 7:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 9:06 [Qemu-devel] [PATCH v6 0/5] ARM: Add NUMA support for machine virt Shannon Zhao
2016-04-23 9:06 ` [Qemu-devel] [PATCH v6 1/5] ARM: Virt: Set numa-node-id for CPUs Shannon Zhao
2016-04-23 9:06 ` [Qemu-devel] [PATCH v6 2/5] ARM: Add numa-node-id for /memory node Shannon Zhao
2016-04-24 16:55 ` Andrew Jones
2016-04-23 9:06 ` [Qemu-devel] [PATCH v6 3/5] ACPI: Add GICC Affinity Structure Shannon Zhao
2016-04-23 9:06 ` [Qemu-devel] [PATCH v6 4/5] ACPI: move acpi_build_srat_memory to common place Shannon Zhao
2016-04-24 17:00 ` Andrew Jones
2016-04-25 7:50 ` Shannon Zhao [this message]
2016-04-23 9:06 ` [Qemu-devel] [PATCH v6 5/5] ACPI: Virt: Generate SRAT table Shannon Zhao
2016-04-24 17:10 ` Andrew Jones
2016-04-24 17:12 ` [Qemu-devel] [PATCH v6 0/5] ARM: Add NUMA support for machine virt Andrew Jones
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=571DCC5D.8010405@huawei.com \
--to=zhaoshenglong@huawei.com \
--cc=david.daney@cavium.com \
--cc=drjones@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhao@linaro.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).