From: David Daney <ddaney@caviumnetworks.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>, <linux-ia64@vger.kernel.org>,
David Daney <david.daney@cavium.com>,
Robert Moore <robert.moore@intel.com>,
Lv Zheng <lv.zheng@intel.com>, "H. Peter Anvin" <hpa@zytor.com>,
Frank Rowand <frowand.list@gmail.com>, <x86@kernel.org>,
<linux-acpi@vger.kernel.org>, Ingo Molnar <mingo@redhat.com>,
Grant Likely <grant.likely@linaro.org>,
Len Brown <lenb@kernel.org>, Fenghua Yu <fenghua.yu@intel.com>,
Marc Zyngier <Marc.Zyngier@arm.com>, Jon Masters <jcm@redhat.com>,
Robert Richter <rrichter@cavium.com>,
Rob Herring <robh+dt@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
<linux-arm-kernel@lists.infradead.org>, <devel@acpica.org>,
Tony Luck <tony.luck@intel.com>, <linux-kernel@vger.kernel.org>,
Hanjun Guo <hanjun.guo@linaro.org>,
Ganapatrao Kulkarni <gkulkarni@caviumnetworks.com>
Subject: Re: [PATCH v6 13/14] arm64, acpi, numa: NUMA support based on SRAT and SLIT
Date: Thu, 12 May 2016 13:40:24 -0700 [thread overview]
Message-ID: <5734EA38.2040206@caviumnetworks.com> (raw)
In-Reply-To: <20160512162449.GK11226@e104818-lin.cambridge.arm.com>
On 05/12/2016 09:24 AM, Catalin Marinas wrote:
> On Thu, May 12, 2016 at 08:27:08AM -0700, David Daney wrote:
>> On 05/12/2016 02:49 AM, Catalin Marinas wrote:
>>> On Wed, May 11, 2016 at 05:06:13PM -0700, David Daney wrote:
>>>> On 05/11/2016 03:39 AM, Catalin Marinas wrote:
>> [...]
>>>>>
>>>>> I wonder whether you could replace the get_mpidr_in_madt() function with
>>>>> something like acpi_get_phys_id(). It looks like get_mpidr_in_madt()
>>>>> duplicates functionality already available elsewhere.
>>>>
>>>> I just tried that, and it doesn't work.
>>>>
>>>> The problem is that this code is being run very early in the boot, and
>>>> kmalloc cannot be used. acpi_get_phys_id() and its ilk can only be used
>>>> once we have working kmalloc. We need to extract the NUMA information early
>>>> like this precisely because it is needed to initializing the slab system
>>>>
>>>> Notice that we are using early_acpi_os_unmap_memory() et al. in
>>>> get_mpidr_in_madt() explicitly for this reason.
>>>>
>>>> In summary: I don't think we need another revision of this patch, it is like
>>>> this for a good reason.
>>>
>>> Slightly confusing, in another reply you said you are going to address
>>> my comment. So, is it doable?
>>
>> I don't think so.
>>
>> My previous reply, to the thread in 0/14, was prematurely made with the
>> incorrect assumption that it was a simple change. Now, after really digging
>> in to the code, and attempting to do as you suggested, I have changed my
>> mind.
>
> Would the snippet below help with avoiding any kmalloc calls? At a quick
> look, it seems that it's only map_mat_entry() that ends up using
> kmalloc() calls. Alternatively, exporting map_madt_entry() may work as
> well.
I think making a non-static version of map_madt_entry() is the cleanest
solution. That works, so I will send a new version of the patch set
that does that instead.
David.
>
> diff --git a/drivers/acpi/processor_core.c b/drivers/acpi/processor_core.c
> index 33a38d604630..77af0a7df914 100644
> --- a/drivers/acpi/processor_core.c
> +++ b/drivers/acpi/processor_core.c
> @@ -152,6 +152,9 @@ static phys_cpuid_t map_mat_entry(acpi_handle handle, int type, u32 acpi_id)
> struct acpi_subtable_header *header;
> phys_cpuid_t phys_id = PHYS_CPUID_INVALID;
>
> + if (!acpi_gbl_permanent_mmap)
> + return phys_id;
> +
> if (ACPI_FAILURE(acpi_evaluate_object(handle, "_MAT", NULL, &buffer)))
> goto exit;
>
>
next prev parent reply other threads:[~2016-05-12 20:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 18:07 [PATCH v6 00/14] ACPI NUMA support for ARM64 David Daney
2016-04-27 18:07 ` [PATCH v6 01/14] acpi, numa: Use pr_fmt() instead of printk David Daney
2016-04-27 18:07 ` [PATCH v6 02/14] acpi, numa: Replace ACPI_DEBUG_PRINT() with pr_debug() David Daney
2016-04-27 18:07 ` [PATCH v6 03/14] acpi, numa: remove duplicate NULL check David Daney
2016-04-27 18:07 ` [PATCH v6 04/14] acpi, numa: Move acpi_numa_arch_fixup() to ia64 only David Daney
2016-04-27 18:07 ` [PATCH v6 05/14] acpi, numa: move acpi_numa_slit_init() to drivers/acpi/numa.c David Daney
2016-04-27 18:07 ` [PATCH v6 06/14] arm64, numa: rework numa_add_memblk() David Daney
2016-05-11 9:12 ` Catalin Marinas
2016-04-27 18:07 ` [PATCH v6 07/14] arm64, numa: Cleanup NUMA disabled messages David Daney
2016-05-11 9:12 ` Catalin Marinas
2016-04-27 18:07 ` [PATCH v6 08/14] x86, acpi, numa: cleanup acpi_numa_processor_affinity_init() David Daney
2016-04-27 18:07 ` [PATCH v6 09/14] acpi, numa: move bad_srat() and srat_disabled() to drivers/acpi/numa.c David Daney
2016-04-27 18:07 ` [PATCH v6 10/14] acpi, numa: remove unneeded acpi_numa=1 David Daney
2016-04-27 18:07 ` [PATCH v6 11/14] acpi, numa: Move acpi_numa_memory_affinity_init() to drivers/acpi/numa.c David Daney
2016-04-27 18:07 ` [PATCH v6 12/14] acpi, numa, srat: Improve SRAT error detection and add messages David Daney
2016-04-27 18:07 ` [PATCH v6 13/14] arm64, acpi, numa: NUMA support based on SRAT and SLIT David Daney
2016-05-11 10:39 ` Catalin Marinas
2016-05-12 0:06 ` David Daney
2016-05-12 1:03 ` Hanjun Guo
2016-05-12 9:49 ` Catalin Marinas
2016-05-12 15:27 ` David Daney
2016-05-12 16:24 ` Catalin Marinas
2016-05-12 20:40 ` David Daney [this message]
2016-04-27 18:07 ` [PATCH v6 14/14] acpi, numa: Enable ACPI based NUMA on ARM64 David Daney
2016-05-11 10:40 ` Catalin Marinas
2016-05-11 0:43 ` [PATCH v6 00/14] ACPI NUMA support for ARM64 Rafael J. Wysocki
2016-05-11 10:40 ` Will Deacon
2016-05-11 20:35 ` Rafael J. Wysocki
2016-05-11 21:08 ` David Daney
2016-05-11 21:22 ` Rafael J. Wysocki
2016-05-11 21:30 ` David Daney
2016-05-11 22:29 ` Rafael J. Wysocki
2016-05-12 8:56 ` Will Deacon
2016-05-12 12:54 ` Rafael J. Wysocki
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=5734EA38.2040206@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=Marc.Zyngier@arm.com \
--cc=catalin.marinas@arm.com \
--cc=david.daney@cavium.com \
--cc=devel@acpica.org \
--cc=fenghua.yu@intel.com \
--cc=frowand.list@gmail.com \
--cc=gkulkarni@caviumnetworks.com \
--cc=grant.likely@linaro.org \
--cc=hanjun.guo@linaro.org \
--cc=hpa@zytor.com \
--cc=jcm@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.com \
--cc=robh+dt@kernel.org \
--cc=rrichter@cavium.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=will.deacon@arm.com \
--cc=x86@kernel.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