From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Revert arm64 cache geometry
Date: Fri, 30 Oct 2015 11:10:28 +0000 [thread overview]
Message-ID: <56335024.9090009@arm.com> (raw)
In-Reply-To: <20151030110010.GA2854@e104818-lin.cambridge.arm.com>
On 30/10/15 11:00, Catalin Marinas wrote:
> On Thu, Oct 29, 2015 at 11:03:27PM +0000, Alexander Van Brunt wrote:
[...]
> BTW, it looks like I don't get any cache information on Juno with
> 4.3-rc7, it says "Unable to detect cache hierarchy from DT for CPU
> 0". I thought the point of the patch you are trying to revert was to
> parse this information from the hardware registers. Sudeep, any
> idea?
>
Yes you need to have updated DT from the mainline. Since the
architecture doesn't provide any way of detecting the cpus sharing
particular cache, we get that information from DT.
If DT lacks that info we don't expose any information. It would be wrong
to say that a shared cache is shared by all the cpus in the system. DT
check was added explicitly to avoid that.
--
Regards,
Sudeep
next prev parent reply other threads:[~2015-10-30 11:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 21:43 [PATCH 0/3] Revert arm64 cache geometry Alex Van Brunt
2015-10-28 21:43 ` [PATCH 1/3] Revert "arm64: kernel: add support for cpu cache information" Alex Van Brunt
2015-10-28 21:43 ` [PATCH 2/3] Revert "arm64: don't flag non-aliasing VIPT I-caches as aliasing" Alex Van Brunt
2015-10-28 21:43 ` [PATCH 3/3] Revert "arm64: add helper functions to read I-cache attributes" Alex Van Brunt
2015-10-29 3:22 ` [PATCH 0/3] Revert arm64 cache geometry Ard Biesheuvel
2015-10-29 11:20 ` Mark Rutland
2015-10-29 12:26 ` Ard Biesheuvel
2015-10-29 15:43 ` Russell King - ARM Linux
2015-10-29 16:28 ` Ard Biesheuvel
2015-10-29 23:06 ` Alexander Van Brunt
2015-10-29 22:54 ` Alexander Van Brunt
2015-10-30 11:18 ` Will Deacon
2015-10-29 11:29 ` Mark Rutland
2015-10-29 11:43 ` Sudeep Holla
2015-10-29 11:40 ` Will Deacon
2015-10-29 23:03 ` Alexander Van Brunt
2015-10-30 11:00 ` Catalin Marinas
2015-10-30 11:10 ` Sudeep Holla [this message]
2015-10-30 11:57 ` Catalin Marinas
2015-10-30 12:27 ` Sudeep Holla
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=56335024.9090009@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).