From: Reinette Chatre <reinette.chatre@intel.com>
To: "Drew Fustini" <fustini@kernel.org>,
"Adrien Ricciardi" <aricciardi@baylibre.com>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Atish Kumar Patra" <atishp@rivosinc.com>,
"Atish Patra" <atish.patra@linux.dev>,
"Babu Moger" <babu.moger@amd.com>,
"Ben Horgan" <ben.horgan@arm.com>,
"Borislav Petkov" <bp@alien8.de>,
"Chen Pei" <cp0613@linux.alibaba.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
"Conor Dooley" <conor+dt@kernel.org>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"Dave Martin" <Dave.Martin@arm.com>,
"Fenghua Yu" <fenghua.yu@intel.com>,
"Gong Shuai" <gong.shuai@sanechips.com.cn>,
"Gong Shuai" <gsh517@gmail.com>,
guo.wenjia23@zte.com.cn, "James Morse" <james.morse@arm.com>,
"Kornel Dulęba" <mindal@semihalf.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
liu.qingtao2@zte.com.cn,
"Liu Zhiwei" <zhiwei_liu@linux.alibaba.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Paul Walmsley" <pjw@kernel.org>,
"Peter Newman" <peternewman@google.com>,
"Radim Krčmář" <rkrcmar@ventanamicro.com>,
"Rob Herring" <robh@kernel.org>,
"Samuel Holland" <samuel.holland@sifive.com>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Tony Luck" <tony.luck@intel.com>,
"Vasudevan Srinivasan" <vasu@rivosinc.com>,
"Ved Shanbhogue" <ved@rivosinc.com>,
"Weiwei Li" <liwei1518@gmail.com>,
"yunhui cui" <cuiyunhui@bytedance.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<x86@kernel.org>, <devicetree@vger.kernel.org>,
<linux-rt-devel@lists.linux.dev>, <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v3 8/8] riscv_cbqri: Add CBQRI capacity allocation platform driver
Date: Tue, 7 Jul 2026 11:22:10 -0700 [thread overview]
Message-ID: <70c9d487-93e9-417a-8b2e-bd04f5e413fe@intel.com> (raw)
In-Reply-To: <ec899c62-35e3-47c1-8d42-47eff084d30f@intel.com>
Hi Drew,
Apologies, my reply ended up in the wrong version of this series. Please consider this as a reply to v4.
ok with me if you respond in v4.
Reinette
On 7/7/26 11:18 AM, Reinette Chatre wrote:
> Hi Drew,
>
> On 6/28/26 2:18 PM, Drew Fustini wrote:
>
> ...> diff --git a/drivers/resctrl/cbqri_capacity.c b/drivers/resctrl/cbqri_capacity.c
>> new file mode 100644
>> index 000000000000..2172432eb328
>> --- /dev/null
>> +++ b/drivers/resctrl/cbqri_capacity.c
>
> ...
>
>> +static int cbqri_capacity_probe(struct platform_device *pdev)
>> +{
>> + struct device *dev = &pdev->dev;
>> + struct cbqri_controller_info info = {};
>> + struct device_node *cache_np;
>> + cpumask_var_t cpu_mask;
>> + struct resource *res;
>> + u32 rcid_count, cache_level;
>> + int cache_id, cpu, ret;
>> +
>> + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>> + if (!res)
>> + return -EINVAL;
>> +
>> + ret = of_property_read_u32(dev->of_node, "riscv,cbqri-rcid", &rcid_count);
>> + if (ret) {
>> + dev_err(dev, "missing riscv,cbqri-rcid\n");
>> + return ret;
>> + }
>> +
>> + cache_np = of_parse_phandle(dev->of_node, "riscv,cbqri-cache", 0);
>> + if (!cache_np) {
>> + dev_err(dev, "missing riscv,cbqri-cache phandle\n");
>> + return -EINVAL;
>> + }
>> +
>> + ret = of_property_read_u32(cache_np, "cache-level", &cache_level);
>> + if (ret) {
>> + dev_err(dev, "%pOF: missing cache-level\n", cache_np);
>> + goto out_put;
>> + }
>> +
>> + if (!zalloc_cpumask_var(&cpu_mask, GFP_KERNEL)) {
>> + ret = -ENOMEM;
>> + goto out_put;
>> + }
>> +
>> + /*
>> + * Associate the controller with its cache instance via
>> + * cacheinfo. The matching cache provides the cache id and the
>> + * set of harts that share the cache.
>> + */
>> + cache_id = -1;
>> + cpus_read_lock();
>> + for_each_online_cpu(cpu) {
>> + struct cacheinfo *ci = get_cpu_cacheinfo_level(cpu, cache_level);
>> +
>> + if (ci && ci->fw_token == cache_np) {
>> + cache_id = ci->id;
>> + cpumask_copy(cpu_mask, &ci->shared_cpu_map);
>
> The way I understand cacheinfo::shared_cpu_map is that it only contains the online
> CPUs that share the cache with this CPU and if the CPU is offline then shared_cpu_map
> only contains the CPU self.
>
> It is thus not clear to me that this handles all the possible CPU online vs offline
> scenarios. For example, if all or some CPUs of a domain are offline during cbqri_capacity_probe()
> and then come online later. It is not clear to me whether cbqri_controller_info::cache_id,
> cbqri_controller::cache_controller::cache_id, or cbqri_controller::cache_controller::cpu_mask
> are needed. Could the cache ID associated with a CPU at the time it comes online to dynamically
> associate it with the resctrl domain that is indexed by the cache ID? This may simplify a couple
> of flows.
>
>> + break;
>> + }
>> + }
>> + cpus_read_unlock();
>> +
>> + if (cache_id < 0) {
>> + dev_err(dev, "%pOF: no online hart reports an L%u cache for this node\n",
>> + cache_np, cache_level);
>> + ret = -ENODEV;
>> + goto out_free;
>> + }
>> +
>> + info.type = CBQRI_CONTROLLER_TYPE_CAPACITY;
>> + info.addr = res->start;
>> + info.size = resource_size(res);
>> + info.rcid_count = rcid_count;
>> + info.cache_id = cache_id;
>> +
>> + ret = riscv_cbqri_register_cc_dt(&info, cache_level, cpu_mask);
>> + if (ret) {
>> + dev_err(dev, "failed to register capacity controller: %d\n", ret);
>> + goto out_free;
>> + }
>> +
>> + dev_info(dev, "registered L%u capacity controller at %pa (cache_id=%d, rcid=%u)\n",
>> + cache_level, &info.addr, cache_id, rcid_count);
>> +
>> +out_free:
>> + free_cpumask_var(cpu_mask);
>> +out_put:
>> + of_node_put(cache_np);
>> + return ret;
>> +}
> Reinette
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-07-07 18:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 21:18 [PATCH v3 0/8] riscv: Add Ssqosid and initial CBQRI resctrl support Drew Fustini
2026-06-28 21:18 ` [PATCH v3 1/8] dt-bindings: riscv: Add Ssqosid extension description Drew Fustini
2026-06-28 21:18 ` [PATCH v3 2/8] riscv: Detect the Ssqosid extension Drew Fustini
2026-06-28 21:18 ` [PATCH v3 3/8] riscv: Add support for srmcfg CSR from " Drew Fustini
[not found] ` <20260628212820.D0DD51F000E9@smtp.kernel.org>
2026-06-29 22:46 ` Drew Fustini
2026-06-28 21:18 ` [PATCH v3 4/8] riscv_cbqri: Add capacity controller probe and allocation device ops Drew Fustini
[not found] ` <20260628212810.05F6D1F00A3A@smtp.kernel.org>
2026-07-01 0:24 ` Drew Fustini
2026-06-28 21:18 ` [PATCH v3 5/8] riscv_cbqri: resctrl: Add cache allocation via capacity block mask Drew Fustini
2026-07-01 20:18 ` Fenghua Yu
2026-07-03 8:00 ` Drew Fustini
[not found] ` <20260628213426.EB9C01F000E9@smtp.kernel.org>
2026-07-06 16:59 ` Drew Fustini
2026-06-28 21:18 ` [PATCH v3 6/8] riscv: Enable resctrl filesystem for Ssqosid Drew Fustini
[not found] ` <20260628213007.AE2CD1F000E9@smtp.kernel.org>
2026-07-06 17:05 ` Drew Fustini
2026-06-28 21:18 ` [PATCH v3 7/8] dt-bindings: riscv: Add binding for CBQRI controllers Drew Fustini
2026-06-29 15:32 ` Conor Dooley
2026-06-28 21:18 ` [PATCH v3 8/8] riscv_cbqri: Add CBQRI capacity allocation platform driver Drew Fustini
[not found] ` <20260628212744.1AD731F000E9@smtp.kernel.org>
2026-07-06 17:09 ` Drew Fustini
2026-07-07 18:18 ` Reinette Chatre
2026-07-07 18:22 ` Reinette Chatre [this message]
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=70c9d487-93e9-417a-8b2e-bd04f5e413fe@intel.com \
--to=reinette.chatre@intel.com \
--cc=Dave.Martin@arm.com \
--cc=alex@ghiti.fr \
--cc=aricciardi@baylibre.com \
--cc=atish.patra@linux.dev \
--cc=atishp@rivosinc.com \
--cc=babu.moger@amd.com \
--cc=ben.horgan@arm.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=cp0613@linux.alibaba.com \
--cc=cuiyunhui@bytedance.com \
--cc=dave.hansen@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=fenghua.yu@intel.com \
--cc=fustini@kernel.org \
--cc=gong.shuai@sanechips.com.cn \
--cc=gsh517@gmail.com \
--cc=guo.wenjia23@zte.com.cn \
--cc=james.morse@arm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=liu.qingtao2@zte.com.cn \
--cc=liwei1518@gmail.com \
--cc=mindal@semihalf.com \
--cc=palmer@dabbelt.com \
--cc=peternewman@google.com \
--cc=pjw@kernel.org \
--cc=rkrcmar@ventanamicro.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tony.luck@intel.com \
--cc=vasu@rivosinc.com \
--cc=ved@rivosinc.com \
--cc=x86@kernel.org \
--cc=zhiwei_liu@linux.alibaba.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