From: "tarumizu.kohei@fujitsu.com" <tarumizu.kohei@fujitsu.com>
To: 'Rob Herring' <robh@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
X86 ML <x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2 5/8] arm64: Create cache sysfs directory without ACPI PPTT for hardware prefetch control
Date: Mon, 4 Apr 2022 11:48:39 +0000 [thread overview]
Message-ID: <OSBPR01MB2037F1C72276FD4E4ECBF44A80E59@OSBPR01MB2037.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAL_Jsq+TvPMZLeBx5Xi4pUNKueGUG9pSTXO2DzWov401w4a6Qw@mail.gmail.com>
> What registers?
>> Hardware prefetch control driver need cache sysfs directory and cache
>> level/type information. In ARM processor, these information can be
>> obtained from the register even without PPTT.
This register mean CLIDR_EL1.
> CCSIDR register is no longer used. You must use DT or PPTT.
I know that commit "a8d4636f96ad" (arm64: cacheinfo: Remove CCSIDR-based
cache information probing) removed the code to read the CCSIDR from the
kernel.
Therefore, I only use level and type information that can be read from
CLIDR_EL1. Are there similar concerns when using only CLIDR_EL1
information?
next prev parent reply other threads:[~2022-04-04 11:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 10:19 [PATCH v2 0/8] Add hardware prefetch control driver for arm64 and x86 Kohei Tarumizu
2022-03-11 10:19 ` [PATCH v2 1/8] drivers: base: Add hardware prefetch control core driver Kohei Tarumizu
2022-03-11 10:19 ` [PATCH v2 2/8] drivers: base: Add Kconfig/Makefile to build " Kohei Tarumizu
2022-03-11 10:19 ` [PATCH v2 3/8] arm64: Add hardware prefetch control support for ARM64 Kohei Tarumizu
2022-03-30 22:11 ` Rob Herring
2022-04-04 11:56 ` tarumizu.kohei
2022-03-11 10:19 ` [PATCH v2 4/8] arm64: Add Kconfig/Makefile to build hardware prefetch control driver Kohei Tarumizu
2022-03-11 10:19 ` [PATCH v2 5/8] arm64: Create cache sysfs directory without ACPI PPTT for hardware prefetch control Kohei Tarumizu
2022-03-30 22:14 ` Rob Herring
2022-04-04 11:48 ` tarumizu.kohei [this message]
2022-03-11 10:19 ` [PATCH v2 6/8] x86: Add hardware prefetch control support for x86 Kohei Tarumizu
2022-03-14 21:05 ` Dave Hansen
2022-03-18 6:41 ` tarumizu.kohei
2022-03-11 10:19 ` [PATCH v2 7/8] x86: Add Kconfig/Makefile to build hardware prefetch control driver Kohei Tarumizu
2022-03-11 10:19 ` [PATCH v2 8/8] docs: ABI: Add sysfs documentation interface of " Kohei Tarumizu
2022-03-14 16:39 ` Jonathan Cameron
2022-03-16 12:56 ` tarumizu.kohei
2022-03-14 19:19 ` [PATCH v2 0/8] Add hardware prefetch control driver for arm64 and x86 Dave Hansen
2022-03-18 6:34 ` tarumizu.kohei
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=OSBPR01MB2037F1C72276FD4E4ECBF44A80E59@OSBPR01MB2037.jpnprd01.prod.outlook.com \
--to=tarumizu.kohei@fujitsu.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).