From: Yin Li <yin.li@oss.qualcomm.com>
To: Ping Li <leeonion.muyu@gmail.com>,
robh@kernel.org, james.morse@arm.com, ben.horgan@arm.com,
sdonthineni@nvidia.com
Cc: andre.przywara@arm.com, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/6] arm-mpam: Add basic device tree support for resctrl
Date: Wed, 4 Nov 2026 16:46:24 +0800 [thread overview]
Message-ID: <9d370f12-9e4c-4b80-9d28-ff8085ce3aee@oss.qualcomm.com> (raw)
In-Reply-To: <20261104081302.304667-1-leeonion.muyu@gmail.com>
On 11/4/2026 4:13 PM, Ping Li wrote:
> Hi Yin, Rob,
>
>> Changes in v4:
>> - Drop memory controller MSC patch (no concrete platform user).
>
> We do have a concrete platform user for that patch.
>
> On our SoC we have implemented an MPAM 1.1 compliant MSC on the DDR
> egress path, which provides system-wide bandwidth QoS. The MSC is
> described in the device tree with the "arm,mpam-memory-controller-msc"
> and "arm,mpam-msc" compatibles, and this patch is what classifies it
> as MPAM_CLASS_MEMORY so that it can be used through resctrl.
>
> We have verified this on hardware with v3 of this series (patches
> 1-6) on top of a v7.4-rc1 based tree: the memory controller MSC
> probes correctly from DT, resctrl exposes the MB resource backed by
> it, and both bandwidth allocation (MPAMCFG_MBW_MAX) and the MBWU-based
> mbm_total_bytes monitoring work for it.
>
> So this patch is genuinely useful for us, and we would like to ask
> you to reconsider dropping it. We are happy to help with testing, or
> to provide more details of our DT description if that is useful.
>
Hi Ping,
Thank you for the feedback — it is great to hear that the memory
controller MSC support has a concrete user and has been verified on
hardware.
Could you share your DT description? That would help us understand
your use case and ensure the binding covers it correctly before we
decide on the next steps.
Thanks,
Yin
> Thanks,
> Ping Li
--
Thx and BRs,
Yin
next prev parent reply other threads:[~2026-11-04 8:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 11:45 Yin Li
2026-10-28 11:45 ` [PATCH v4 1/6] arm_mpam: Fix the RIS index range check in mpam_ris_create_locked Yin Li
2026-10-30 17:15 ` Srivathsa L Rao
2026-10-28 11:45 ` [PATCH v4 2/6] arm_mpam: Fix MSC MMIO window size off-by-one with resource_size() Yin Li
2026-10-29 8:12 ` Jinjie Ruan
2026-10-29 8:13 ` Jinjie Ruan
2026-10-29 12:02 ` Ilpo Järvinen
2026-10-30 17:18 ` Srivathsa L Rao
2026-10-28 11:45 ` [PATCH v4 3/6] dt-bindings: arm: Add MPAM MSC binding Yin Li
2026-10-28 11:45 ` [PATCH v4 4/6] cacheinfo: Expose the code to generate a cache-id from a device_node Yin Li
2026-10-28 11:45 ` [PATCH v4 5/6] arm_mpam: Add device tree support for MSC probing Yin Li
2026-10-28 11:45 ` [PATCH DNM v4 6/6] arm64: dts: qcom: kaanapali: Add MPAM MSC nodes for the L2 caches Yin Li
2026-11-04 8:13 ` [PATCH v4 0/6] arm-mpam: Add basic device tree support for resctrl Ping Li
2026-11-04 8:46 ` Yin Li [this message]
2026-11-05 5:53 ` Ping Li
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=9d370f12-9e4c-4b80-9d28-ff8085ce3aee@oss.qualcomm.com \
--to=yin.li@oss.qualcomm.com \
--cc=andre.przywara@arm.com \
--cc=ben.horgan@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=james.morse@arm.com \
--cc=krzk+dt@kernel.org \
--cc=leeonion.muyu@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sdonthineni@nvidia.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®