From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: kernel: add support for cpu cache information
Date: Tue, 24 Feb 2015 18:23:11 +0000 [thread overview]
Message-ID: <54ECC18F.2080409@arm.com> (raw)
In-Reply-To: <20150223193621.GP8656@n2100.arm.linux.org.uk>
On 23/02/15 19:36, Russell King - ARM Linux wrote:
> On Mon, Feb 23, 2015 at 06:28:10PM +0000, Sudeep Holla wrote:
>> This patch adds support for cacheinfo on ARM platforms.
>
> These patches should carry with them the justification for exporting
> this information to userspace.
>
> "Because we can" is not a good reason; once exported, this
> information becomes a userspace API that we have to maintain, and
> thus it comes with a non-zero support cost going forward.
>
Agreed. So far I have got requests from GCC, JIT and graphics guys.
IIUC they need this to support cache flushing for user applications like
gcc trampolines and JIT compilers. I am also told that having knowledge
of cache architecture can help optimal code strategies, though I don't
have much details on that.
Though it's not a arguable reason, this feature is already supported on
x86 and other architecture and they are users interested in getting this
info on ARM/ARM64 systems too(especially in heterogeneous systems like
big-little, multi-cluster systems and even NUMA systems)
Regards,
Sudeep
next prev parent reply other threads:[~2015-02-24 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 18:28 [PATCH 1/2] ARM: kernel: add support for cpu cache information Sudeep Holla
2015-02-23 18:28 ` [PATCH 2/2] ARM: kernel: add outer cache support for cacheinfo implementation Sudeep Holla
2015-02-23 19:36 ` [PATCH 1/2] ARM: kernel: add support for cpu cache information Russell King - ARM Linux
2015-02-24 18:23 ` Sudeep Holla [this message]
2016-01-28 18:54 ` Florian Fainelli
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=54ECC18F.2080409@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).