From: Alireza Sanaee <alireza.sanaee@huawei.com>
To: <robh@kernel.org>, <mark.rutland@arm.com>, <devicetree@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <jonathan.cameron@Huawei.com>,
<linux-arm-kernel@lists.infradead.org>,
<shameerali.kolothum.thodi@huawei.com>, <zhao1.liu@intel.com>,
<yangyicong@hisilicon.com>, <rrendec@redhat.com>,
<catalin.marinas@arm.com>
Subject: [RFC PATCH v1 0/1] base/of/cacheinfo: support l1-cache entry in dt
Date: Fri, 24 Jan 2025 15:20:07 +0000 [thread overview]
Message-ID: <20250124152008.313-1-alireza.sanaee@huawei.com> (raw)
This RFC adds support for l1-cache entry in device tree. The changes are
based on the assumptions that nodes will have l1-cache to describe first
cache layer. This patch enable to describe shared caches for SMTs which
is not currently possible about which there were discussions already
[1,2,3].
The question that I am seeking feedback for is to see if this might be a
good way to go about solving this issue? Or instead using phandle and
index in CPU nodes is a better way to go according to prior discussion,
I have another patch this investigates this approach [2]. Apparently,
every single CPU will need to addressed in the cpu-map structure as per
Mark mentioned earlier [4].
Sample device tree:
cpu@0 {
next-level-cache = <0x800b>;
phandle = <0x800a>;
reg = <0x00>;
enable-method = "psci";
compatible = "arm,cortex-a57";
device_type = "cpu";
l1-cache {
next-level-cache = <0x8008>;
cache-level = <0x01>;
d-cache-sets = <0x100>;
d-cache-block-size = <0x40>;
d-cache-size = <0x10000>;
i-cache-sets = <0x100>;
i-cache-block-size = <0x40>;
i-cache-size = <0x10000>;
phandle = <0x800b>;
};
};
cpu@1 {
next-level-cache = <0x8009>;
phandle = <0x8007>;
reg = <0x01>;
enable-method = "psci";
compatible = "arm,cortex-a57";
device_type = "cpu";
l1-cache {
next-level-cache = <0x8008>;
cache-level = <0x01>;
d-cache-sets = <0x100>;
d-cache-block-size = <0x40>;
d-cache-size = <0x10000>;
i-cache-sets = <0x100>;
i-cache-block-size = <0x40>;
i-cache-size = <0x10000>;
phandle = <0x8009>;
};
l2-cache {
next-level-cache = <0x8002>;
cache-level = <0x02>;
cache-unified;
cache-sets = <0x800>;
cache-block-size = <0x40>;
cache-size = <0x100000>;
phandle = <0x8008>;
};
};
1) https://lore.kernel.org/linux-devicetree/CAL_JsqLGEvGBQ0W_B6+5cME1UEhuKXadBB-6=GoN1tmavw9K_w@mail.gmail.com/
2) https://lore.kernel.org/linux-arm-kernel/20250110161057.445-1-alireza.sanaee@huawei.com/
3) https://mail.gnu.org/archive/html/qemu-arm/2025-01/msg00014.html
4) https://lore.kernel.org/linux-arm-kernel/Z4FJZPRg75YIUR2l@J2N7QTR9R3/
Alireza Sanaee (1):
base/of/cacheinfo: support l1 entry in dt
drivers/base/cacheinfo.c | 54 +++++++++++++++++++++++++++-------------
1 file changed, 37 insertions(+), 17 deletions(-)
--
2.34.1
next reply other threads:[~2025-01-24 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 15:20 Alireza Sanaee [this message]
2025-01-24 15:20 ` [RFC PATCH v1 1/1] base/of/cacheinfo: support l1 " Alireza Sanaee
2025-01-27 12:11 ` Jonathan Cameron
2025-01-28 11:44 ` Alireza Sanaee
2025-01-27 16:24 ` Rob Herring
2025-01-28 11:48 ` Alireza Sanaee
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=20250124152008.313-1-alireza.sanaee@huawei.com \
--to=alireza.sanaee@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathan.cameron@Huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=rrendec@redhat.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=yangyicong@hisilicon.com \
--cc=zhao1.liu@intel.com \
/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
all inboxes | Powered by JetHome®