From: Chen Pei <cp0613@linux.alibaba.com>
To: Drew Fustini <fustini@kernel.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 5/8] riscv_cbqri: resctrl: Add cache allocation via capacity block mask
Date: Wed, 2 Sep 2026 10:05:47 +0800 [thread overview]
Message-ID: <20260902095109.reply2.cp0613@linux.alibaba.com> (raw)
In-Reply-To: <apdMvKYegtdEWntp@gen8>
Hi Drew,
Thanks for the quick pointer.
To clarify our report: we were not testing the series on a new core. We
backported v6 onto a 6.6 LTS tree, whose resctrl core still predates
dbc58f7eec40 ("x86/resctrl: Generate default_ctrl instead of sharing
it"): struct rdt_resource still carries a default_ctrl member there and
resctrl_get_default_ctrl() merely returns that stored value, so an
uninitialized default_ctrl shows up as cbm_mask=0 / L3:0=0 exactly as
we observed.
> I think you may be looking at an older version. The function in this
> patch is:
>
> static void cbqri_resctrl_control_init(struct cbqri_resctrl_res *cbqri_res)
>
> struct rdt_resource no longer has a default_ctrl member. Commit
> dbc58f7eec40 ("x86/resctrl: Generate default_ctrl instead of sharing
> it") removed it and derives the value instead.
Right - on the new core the value is derived, so the series needs no
initialization. Our report came from a backport of v6 onto a 6.6 LTS
tree, whose older resctrl core still requires the driver to initialize
default_ctrl; that is a porting issue on our side and has been handled
in our tree. Sorry for the noise.
> I will send v7 today as I have now rebased on v7.3-rc1. It is already
> available as a branch [2]. Please give that a try and let me know of
> any problems.
We will give the v7 branch a try on our QEMU and on the FPGA board,
and report back with results. Thanks again for maintaining this series.
Best regards,
Pei
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-09-02 2:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 1:11 [PATCH v6 0/8] riscv: Add Ssqosid and initial CBQRI resctrl support Drew Fustini
2026-07-30 1:11 ` [PATCH v6 1/8] dt-bindings: riscv: Add Ssqosid extension description Drew Fustini
2026-08-05 2:46 ` Paul Walmsley
2026-07-30 1:11 ` [PATCH v6 2/8] riscv: Detect the Ssqosid extension Drew Fustini
2026-08-05 2:47 ` Paul Walmsley
2026-08-05 3:40 ` Drew Fustini
2026-07-30 1:11 ` [PATCH v6 3/8] riscv: Add support for srmcfg CSR from " Drew Fustini
[not found] ` <20260730012227.58F5C1F000E9@smtp.kernel.org>
2026-07-30 2:04 ` Drew Fustini
2026-08-05 18:54 ` Paul Walmsley
2026-08-05 20:50 ` Drew Fustini
2026-08-06 1:21 ` Paul Walmsley
2026-07-30 1:11 ` [PATCH v6 4/8] riscv_cbqri: Add capacity controller probe and allocation device ops Drew Fustini
2026-07-30 1:11 ` [PATCH v6 5/8] riscv_cbqri: resctrl: Add cache allocation via capacity block mask Drew Fustini
[not found] ` <20260730012722.A77E71F000E9@smtp.kernel.org>
2026-07-30 2:09 ` Drew Fustini
2026-08-31 2:16 ` Chen Pei
2026-09-01 22:07 ` Drew Fustini
2026-09-02 2:05 ` Chen Pei [this message]
2026-07-30 1:11 ` [PATCH v6 6/8] riscv: Enable resctrl filesystem for Ssqosid Drew Fustini
2026-07-30 1:11 ` [PATCH v6 7/8] dt-bindings: riscv: Add binding for CBQRI controllers Drew Fustini
2026-07-30 1:11 ` [PATCH v6 8/8] riscv_cbqri: Add CBQRI capacity allocation platform driver Drew Fustini
[not found] ` <20260730012125.2DA611F000E9@smtp.kernel.org>
2026-07-30 2:11 ` Drew Fustini
2026-08-05 3:00 ` [PATCH v6 0/8] riscv: Add Ssqosid and initial CBQRI resctrl support patchwork-bot+linux-riscv
2026-08-05 19:00 ` patchwork-bot+linux-riscv
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=20260902095109.reply2.cp0613@linux.alibaba.com \
--to=cp0613@linux.alibaba.com \
--cc=fustini@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@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