From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-riscv@lists.infradead.org
Subject: [PATCH v8 07/13] drivers: base cacheinfo: Add support for ACPI based firmware tables
Date: Thu, 26 Apr 2018 12:05:56 +0100 [thread overview]
Message-ID: <c3306746-aacd-5ed8-95d6-a3186ec2089f@arm.com> (raw)
In-Reply-To: <20180425233121.13270-8-jeremy.linton@arm.com>
On 26/04/18 00:31, Jeremy Linton wrote:
> Call ACPI cache parsing routines from base cacheinfo code if ACPI
> is enable. Also stub out cache_setup_acpi() so that individual
> architectures can enable ACPI topology parsing.
>
[...]
> +#ifndef CONFIG_ACPI
> +static inline int acpi_find_last_cache_level(unsigned int cpu)
> +{
> + /* ACPI kernels should be built with PPTT support */
This sounds incorrect for x86. But I understand why you have it there.
Does it makes sense to change above to .. ?
#if !defined(CONFIG_ACPI) || (defined(CONFIG_ACPI) && !(CONFIG_ACPI_PPTT))
--
Regards,
Sudeep
next prev parent reply other threads:[~2018-04-26 11:05 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 23:31 [PATCH v8 00/13] Support PPTT for ARM64 Jeremy Linton
2018-04-25 23:31 ` [PATCH v8 01/13] drivers: base: cacheinfo: move cache_setup_of_node() Jeremy Linton
2018-04-25 23:31 ` [PATCH v8 02/13] drivers: base: cacheinfo: setup DT cache properties early Jeremy Linton
2018-04-25 23:31 ` [PATCH v8 03/13] cacheinfo: rename of_node to fw_token Jeremy Linton
2018-04-25 23:31 ` [PATCH v8 04/13] arm64/acpi: Create arch specific cpu to acpi id helper Jeremy Linton
2018-04-26 10:27 ` Sudeep Holla
2018-04-26 18:33 ` Jeremy Linton
2018-04-27 13:08 ` Sudeep Holla
2018-04-25 23:31 ` [PATCH v8 05/13] ACPI/PPTT: Add Processor Properties Topology Table parsing Jeremy Linton
2018-04-27 11:02 ` Rafael J. Wysocki
2018-04-27 16:20 ` Jeremy Linton
2018-04-30 7:59 ` Rafael J. Wysocki
2018-04-25 23:31 ` [PATCH v8 06/13] ACPI: Enable PPTT support on ARM64 Jeremy Linton
2018-04-25 23:31 ` [PATCH v8 07/13] drivers: base cacheinfo: Add support for ACPI based firmware tables Jeremy Linton
2018-04-26 11:05 ` Sudeep Holla [this message]
2018-04-26 18:57 ` Jeremy Linton
2018-04-27 12:49 ` Sudeep Holla
2018-04-25 23:31 ` [PATCH v8 08/13] arm64: " Jeremy Linton
2018-04-25 23:31 ` [PATCH v8 09/13] ACPI/PPTT: Add topology parsing code Jeremy Linton
2018-04-25 23:31 ` [PATCH v8 10/13] arm64: topology: rename cluster_id Jeremy Linton
2018-05-01 14:40 ` Sudeep Holla
2018-05-03 15:14 ` Morten Rasmussen
2018-04-25 23:31 ` [PATCH v8 11/13] arm64: topology: enable ACPI/PPTT based CPU topology Jeremy Linton
2018-05-01 14:46 ` Sudeep Holla
2018-05-02 8:24 ` Rafael J. Wysocki
2018-05-02 22:35 ` Jeremy Linton
2018-05-03 8:41 ` Rafael J. Wysocki
2018-05-03 15:15 ` Morten Rasmussen
2018-04-25 23:31 ` [PATCH v8 12/13] ACPI: Add PPTT to injectable table list Jeremy Linton
2018-04-25 23:31 ` [PATCH v8 13/13] arm64: topology: divorce MC scheduling domain from core_siblings Jeremy Linton
2018-05-01 14:33 ` Sudeep Holla
2018-05-02 11:49 ` Morten Rasmussen
2018-05-02 22:32 ` Jeremy Linton
2018-05-03 11:20 ` Morten Rasmussen
2018-05-02 22:34 ` Jeremy Linton
2018-05-03 15:12 ` Morten Rasmussen
2018-04-26 7:57 ` [PATCH v8 00/13] Support PPTT for ARM64 Ard Biesheuvel
2018-05-04 8:10 ` vkilari at codeaurora.org
2018-05-04 11:44 ` Sudeep Holla
2018-05-04 11:34 ` Xiongfeng Wang
2018-05-09 13:20 ` Tomasz Nowicki
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=c3306746-aacd-5ed8-95d6-a3186ec2089f@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-riscv@lists.infradead.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