From: Jeremy Linton <jeremy.linton@arm.com>
To: Hanjun Guo <hanjun.guo@linaro.org>, linux-arm-kernel@lists.infradead.org
Cc: mark.rutland@arm.com, lorenzo.pieralisi@arm.com,
linux-acpi@vger.kernel.org, steve.capper@arm.com,
punit.agrawal@arm.com, will.deacon@arm.com,
linux@armlinux.org.uk, mlangsdorf@redhat.com, msalter@redhat.com,
bamvor.zhangjian@linaro.org
Subject: Re: [PATCH v13 1/7] arm64: Rename the common MADT parse routine
Date: Thu, 19 Jan 2017 11:17:57 -0600 [thread overview]
Message-ID: <5aa277bd-b9ce-1adf-c1e9-3e76fd241175@arm.com> (raw)
In-Reply-To: <c9056b99-7a32-3c91-eb8a-5b44a182c140@linaro.org>
Hi,
Thanks for taking a look at this!
On 01/18/2017 09:51 PM, Hanjun Guo wrote:
> Hi Jeremy,
>
> On 2017/1/18 4:50, Jeremy Linton wrote:
>> The MADT parser in smp.c is now being used to parse
>> out NUMA, PMU and ACPI parking protocol information as
>> well as the GIC information for which it was originally
>> created. Rename it to avoid a misleading name.
>>
>> Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
>> ---
>> arch/arm64/kernel/smp.c | 13 +++++++------
>> 1 file changed, 7 insertions(+), 6 deletions(-)
>>
>> diff --git a/arch/arm64/kernel/smp.c b/arch/arm64/kernel/smp.c
>> index cb87234..8ea244c 100644
>> --- a/arch/arm64/kernel/smp.c
>> +++ b/arch/arm64/kernel/smp.c
>> @@ -517,13 +517,14 @@ static unsigned int cpu_count = 1;
>>
>> #ifdef CONFIG_ACPI
>> /*
>> - * acpi_map_gic_cpu_interface - parse processor MADT entry
>> + * acpi_verify_and_map_madt - parse processor MADT entry
>> *
>> * Carry out sanity checks on MADT processor entry and initialize
>> - * cpu_logical_map on success
>> + * cpu_logical_map, the ACPI parking protocol, NUMA mapping
>> + * and the PMU interrupts on success
>> */
>> static void __init
>> -acpi_map_gic_cpu_interface(struct acpi_madt_generic_interrupt
>> *processor)
>> +acpi_verify_and_map_madt(struct acpi_madt_generic_interrupt *processor)
>
> Nit, MADT is a table includes multi type of table entries, we just
> need to map the the processor type, how about updating it to
> acpi_verify_and_map_madt_processor()?
The rename was originally proposed in a previous review comment because
the thought was that the code is now parsing more than just the GIC->CPU
information. That is even though the subtable type its parsing is
described as the "GIC CPU interface" in the ACPI specification.
So, in a way, I think the original gic_cpu_interface() name is more
descriptive than acpi_verify_and_map_madt_processor(), but I'm pretty
agnostic about what the name is. Particularly, since MADT itself is
misleading.
So, I don't see a need to respin this, simply to rename it, unless
someone has a strong opinion one way or the other. Primary, because I
would like to get this set merged and the right decision might just be
to drop this patch.
Thanks,
next prev parent reply other threads:[~2017-01-19 17:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 20:50 [PATCH v13 0/7] Enable PMUs in ACPI systems Jeremy Linton
2017-01-17 20:50 ` [PATCH v13 1/7] arm64: Rename the common MADT parse routine Jeremy Linton
2017-01-19 3:51 ` Hanjun Guo
2017-01-19 17:17 ` Jeremy Linton [this message]
2017-01-20 16:22 ` Lorenzo Pieralisi
2017-01-20 17:12 ` Jeremy Linton
2017-01-17 20:50 ` [PATCH v13 2/7] arm: arm64: Add routine to determine cpuid of other cpus Jeremy Linton
2017-01-17 20:50 ` [PATCH v13 3/7] arm64: pmu: Cache PMU interrupt numbers from MADT parse Jeremy Linton
2017-01-20 17:37 ` Lorenzo Pieralisi
2017-01-17 20:50 ` [PATCH v13 4/7] arm: arm64: pmu: Assign platform PMU CPU affinity Jeremy Linton
2017-01-17 20:50 ` [PATCH v13 5/7] arm64: pmu: Detect multiple generic PMUs and append counter Jeremy Linton
2017-01-17 20:50 ` [PATCH v13 6/7] arm64: pmu: Detect and enable multiple PMUs in an ACPI system Jeremy Linton
2017-01-17 20:50 ` [PATCH v13 7/7] arm: pmu: Add PMU definitions for cores not initially online Jeremy Linton
2017-01-19 3:57 ` [PATCH v13 0/7] Enable PMUs in ACPI systems Hanjun Guo
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=5aa277bd-b9ce-1adf-c1e9-3e76fd241175@arm.com \
--to=jeremy.linton@arm.com \
--cc=bamvor.zhangjian@linaro.org \
--cc=hanjun.guo@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=mlangsdorf@redhat.com \
--cc=msalter@redhat.com \
--cc=punit.agrawal@arm.com \
--cc=steve.capper@arm.com \
--cc=will.deacon@arm.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