[PATCH 3/5] arm_mpam: add MPAM-Fb MSC firmware access support
Ben Horgan
ben.horgan at arm.com
Thu May 14 02:30:35 PDT 2026
Hi Andre,
I'm just having another look to try and understand this a bit better.
On 4/29/26 15:13, Andre Przywara wrote:
> The Arm MPAM Firmware-backed (Fb) Profile document[1] describes an
> alternative way of accessing the "Memory System Components" (MSC) in an
> MPAM enabled system.
> Normally the MSCs are MMIO mapped, but in some implementations this
> might not be possible (MSC located outside of the local socket, MSC
> mapped secure-only) or desirable (direct MMIO access too slow or needs
> to be mediated through a control processor). MPAM-fb standardises a
> protocol to abstract MSC accesses, building on the SCMI protocol.
>
> Add functions that do an MSC read or write access by redirecting the
> request through a firmware interface. For now this done via an ACPI
> PCC shared memory and mailbox combination.
>
> Since the protocol used is only a small subset of the full SCMI spec,
> and the SCMI protocol has no full ACPI support anyway, open-code the
> SCMI message generation and handshake, for just the fields we need.
>
> [1] https://developer.arm.com/documentation/den0144/latest
>
> Signed-off-by: Andre Przywara <andre.przywara at arm.com>
> ---
> drivers/resctrl/Makefile | 2 +-
> drivers/resctrl/mpam_devices.c | 16 +++-
> drivers/resctrl/mpam_fb.c | 158 ++++++++++++++++++++++++++++++++
> drivers/resctrl/mpam_fb.h | 17 ++++
> drivers/resctrl/mpam_internal.h | 5 +
> include/linux/arm_mpam.h | 2 +-
> 6 files changed, 196 insertions(+), 4 deletions(-)
> create mode 100644 drivers/resctrl/mpam_fb.c
> create mode 100644 drivers/resctrl/mpam_fb.h
[...]
> static inline void _mpam_write_partsel_reg(struct mpam_msc *msc, u16 reg, u32 val)
> diff --git a/drivers/resctrl/mpam_fb.c b/drivers/resctrl/mpam_fb.c
> new file mode 100644
> index 000000000000..bfb5798c74b0
> --- /dev/null
> +++ b/drivers/resctrl/mpam_fb.c
[...]
> +
> +#define SCMI_CHANNEL_FREE true
> +#define SCMI_CHANNEL_BUSY false
> +static int mpam_fb_wait_for_channel(struct pcc_mbox_chan *chan,
> + bool free)
> +{
> + u32 status = free ? SCMI_CHAN_STATUS_FREE_BIT : 0;
> + u32 val;
> +
> + /*
> + * The channel should really be free always at this point, as we take
> + * a lock for every read or write request. Check the free bit anyway,
> + * for good measure and to catch corner cases.
> + */
> + return readl_poll_timeout(chan->shmem + SCMI_CHAN_STATUS_OFS, val,
> + (val & SCMI_CHAN_STATUS_FREE_BIT) == status,
> + 1, 10000);
> +}
What would be the reason to call mpam_fb_wait_for_channel() with
free=SCMI_CHANNEL_BUSY? I see that in this patch you always call it with
free=SCMI_CHANNEL_FREE.
Thanks,
Ben
> +
> +static int mpam_fb_send_request(struct mpam_msc *msc, u16 reg, u32 *result,
> + bool is_write)
> +{
> + unsigned int token = atomic_inc_return(&mpam_fb_token);
> + struct pcc_mbox_chan *chan = msc->pcc_chan;
> + u32 status;
> + int ret;
> +
> + guard(mutex)(&msc->pcc_chan_lock);
> + ret = mpam_fb_wait_for_channel(chan, SCMI_CHANNEL_FREE);
> + if (ret < 0)
> + return ret;
> +
> + /* Clear error bit and mark the channel as belonging to the callee */
> + writel(0, chan->shmem + SCMI_CHAN_STATUS_OFS);
> +
> + if (is_write)
> + ret = mpam_fb_build_write_message(msc->mpam_fb_msc_id, reg,
> + *result, token, chan->shmem);
> + else
> + ret = mpam_fb_build_read_message(msc->mpam_fb_msc_id, reg,
> + token, chan->shmem);
> + if (ret < 0)
> + return ret;
> +
> + ret = mbox_send_message(chan->mchan, NULL);
> + if (ret < 0)
> + return ret;
> +
> + ret = mpam_fb_wait_for_channel(chan, SCMI_CHANNEL_FREE);
> + if (ret)
> + return ret;
> +
> + status = readl(chan->shmem + SCMI_MSG_HEADER_OFS);
> + if (FIELD_GET(MPAM_MSC_TOKEN_MASK, status) != token)
> + return -ETIMEDOUT;
> +
> + ret = readl(chan->shmem + SCMI_MSG_PAYLOAD_OFS + 0x0);
> + if (ret < 0)
> + return ret;
> +
> + if (!is_write)
> + *result = readl(chan->shmem + SCMI_MSG_PAYLOAD_OFS + 0x4);
> +
> + return 0;
> +}
> +
> +int mpam_fb_send_read_request(struct mpam_msc *msc, u16 reg, u32 *result)
> +{
> + return mpam_fb_send_request(msc, reg, result, false);
> +}
> +
> +int mpam_fb_send_write_request(struct mpam_msc *msc, u16 reg, u32 value)
> +{
> + return mpam_fb_send_request(msc, reg, &value, true);
> +}
More information about the linux-arm-kernel
mailing list