From: Ben Horgan <ben.horgan@arm.com>
To: Ping Li <leeonion.muyu@gmail.com>, james.morse@arm.com
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, reinette.chatre@intel.com,
fenghuay@nvidia.com
Subject: Re: [PATCH] arm_mpam: Warn when firmware leaves PARTIDs disabled
Date: Mon, 2 Nov 2026 10:02:02 +0000 [thread overview]
Message-ID: <c54e9853-b503-4aac-87cd-71c68ef4f7b3@arm.com> (raw)
In-Reply-To: <20261101025550.1633447-1-leeonion.muyu@gmail.com>
Hi Ping,
On 01/11/2026 02:55, Ping Li wrote:
> Hi Ben,
>
> Thanks for sharing the direction. I asked our hardware team why they
> implemented HAS_ENDIS: the motivation is power. Enabling PARTIDs that
> are never used does not affect performance, but costs leakage in the
> registers and combinational logic behind them - with e.g. 32 PARTIDs
> implemented and only a handful ever used, the unused portion is pure
> waste. Their expectation was that software would enable only the
> PARTIDs it needs at initialization time.
Thanks for this information. It may also be useful for getting data associated out of the cache
quickly once the associated PARTID is unused.
>
> For a general-purpose driver that cannot predict how many PARTIDs
> userspace will actually use, that is not something we can do. So what
> I plan to do is either enable all the PARTIDs from the driver, or ask
Enabling all the PARTIDs in the driver is a good first step to support hardware with ENDIS. However,
going forward I think we could actually make use of the feature by enabling PARTIDs when a control
group is created in resctrl and disabling them when a control group is deleted.
Thanks,
Ben
> the hardware team to drop the HAS_ENDIS feature.
>
> I am happy to drop this warning patch in favour of your driver-side
> enabling patch.
>
> Thanks,
> Ping
prev parent reply other threads:[~2026-11-02 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 8:35 Ping Li
2026-10-30 15:02 ` Ben Horgan
2026-11-01 2:55 ` Ping Li
2026-11-02 10:02 ` Ben Horgan [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=c54e9853-b503-4aac-87cd-71c68ef4f7b3@arm.com \
--to=ben.horgan@arm.com \
--cc=fenghuay@nvidia.com \
--cc=james.morse@arm.com \
--cc=leeonion.muyu@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@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®