From: Drew Fustini <fustini@kernel.org>
To: yunhui cui <cuiyunhui@bytedance.com>
Cc: "Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Conor Dooley" <conor@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Kornel Dulęba" <mindal@semihalf.com>,
"Adrien Ricciardi" <aricciardi@baylibre.com>,
"James Morse" <james.morse@arm.com>,
"Atish Kumar Patra" <atishp@rivosinc.com>,
"Atish Patra" <atish.patra@linux.dev>,
"Vasudevan Srinivasan" <vasu@rivosinc.com>,
"Conor Dooley" <conor.dooley@microchip.com>,
guo.wenjia23@zte.com.cn, liu.qingtao2@zte.com.cn,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [External] [PATCH v4 0/3] RISC-V: Detect Ssqosid extension and handle srmcfg CSR
Date: Fri, 10 Oct 2025 14:56:00 -0700 [thread overview]
Message-ID: <aOmA8DNt/y+WxT97@x1> (raw)
In-Reply-To: <CAEEQ3w=3pte5=CR9-R3rmCGFZ9ErJ9YcWS9i=JwPUb1Ty3ipwQ@mail.gmail.com>
On Fri, Oct 10, 2025 at 08:23:50PM +0800, yunhui cui wrote:
> Hi Drew,
[snip]
> > I think it makes sense to first focus on the detection of Ssqosid and
> > handling of srmcfg when switching tasks. It has been tested against a
> > QEMU branch that implements Ssqosid and CBQRI [6]. A test driver [7]
> > was used to set srmcfg for the current process. This allows switch_to
> > to be tested without resctrl.
>
> Could we consider submitting the entire QoS functionality as a single
> integrated patchset (indicating the upstream branch that the patchset
> is based on)? This should include the content from
> https://lore.kernel.org/linux-riscv/20230419111111.477118-1-dfustini@baylibre.com/
Thanks for the feedback. I had thought that submitting Ssqosid
separately would streamline the review of the parts that most affects
existing arch/riscv code (like switch_to.h) before adding code for CBQRI
and resctrl integration.
But I have gotten similar feedback from another person too. I can post a
complete series that adds Ssqosid and CBQRI support including the
resctrl interface. I have a cbqri branch [1] on top of riscv/for-next.
I need to clean up some of the code, and then I can send a series with
ssqosid+cbqri.
That cbqri branch just has device tree support in order to demonstrate
the resctrl functionality. However, I did also work on support for the
ACPI RQSC table earlier this year for a proof of concept [2]. I have
been thinking that I will hold back the ACPI support until after Ssqosid
and CBQRI support is reviewed. It also depends on some improvements
regarding the ACPI PPTT table that James Morse is currently working on for
ARM MPAM support [3].
Thanks,
Drew
[1] https://git.kernel.org/pub/scm/linux/kernel/git/fustini/linux.git/log/?h=b4/cbqri
[2] https://lf-rise.atlassian.net/wiki/spaces/HOME/pages/433291272/ACPI+RQSC+Proof+of+Concept
[3] https://lore.kernel.org/all/20250910204309.20751-1-james.morse@arm.com/
prev parent reply other threads:[~2025-10-10 21:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 6:21 [PATCH v4 0/3] RISC-V: Detect Ssqosid extension and handle srmcfg CSR Drew Fustini
2025-10-08 6:21 ` [PATCH v4 1/3] dt-bindings: riscv: Add Ssqosid extension description Drew Fustini
2025-10-08 6:21 ` [PATCH v4 2/3] RISC-V: Detect the Ssqosid extension Drew Fustini
2025-10-08 6:21 ` [PATCH v4 3/3] RISC-V: Add support for srmcfg CSR from Ssqosid ext Drew Fustini
2025-10-09 6:47 ` Radim Krčmář
2025-10-11 18:35 ` Drew Fustini
2025-10-13 9:06 ` Radim Krčmář
2025-11-07 17:44 ` Drew Fustini
2025-10-10 12:23 ` [External] [PATCH v4 0/3] RISC-V: Detect Ssqosid extension and handle srmcfg CSR yunhui cui
2025-10-10 21:56 ` Drew Fustini [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=aOmA8DNt/y+WxT97@x1 \
--to=fustini@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=aricciardi@baylibre.com \
--cc=atish.patra@linux.dev \
--cc=atishp@rivosinc.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=cuiyunhui@bytedance.com \
--cc=devicetree@vger.kernel.org \
--cc=guo.wenjia23@zte.com.cn \
--cc=james.morse@arm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=liu.qingtao2@zte.com.cn \
--cc=mindal@semihalf.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=vasu@rivosinc.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;
as well as URLs for NNTP newsgroup(s).