[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aLGciannXznRgwsb@e133380.arm.com>
Date: Fri, 29 Aug 2025 13:26:49 +0100
From: Dave Martin <Dave.Martin@....com>
To: James Morse <james.morse@....com>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Shaopeng Tan <tan.shaopeng@...fujitsu.com>
Subject: Re: [PATCH] arm_mpam: Relax num_rmids parameter advertised to
userspace
Hi James,
On Wed, Aug 27, 2025 at 06:16:00PM +0100, James Morse wrote:
> Hi Dave,
>
> On 20/08/2025 14:15, Dave Martin wrote:
> > On MPAM systems, monitoring groups are identified in the hardware by a
> > (PARTID, PMG) pair. Two monitoring group identifiers are the same only
> > if the PARTIDs and PMGs both match. This means that the number of
> > monitoring groups that can be created in each control group is the same
> > as the number of distinct PMG values supported by the hardware. The
> > number of monitoring groups that exist in other control groups at the
> > same time makes no difference to this.
> >
> > Currently, the MPAM driver takes the cautious approach and always
> > num_rmids = 1.
> >
> > Relax this limit, by advertising the number of distinct PMG values
> > supported by the hardware.
> >
> > Code/Data Prioritization (CDP) makes no difference, since although this
> > doubles the number of (PARTID, PMG) pairs available to a control group,
> > each monitoring group now consumes two pairs instead of one.
>
> Thanks, I've picked this up. It may get squashed into the patch that adds these lines
> before going upstream...
>
>
> Thanks,
>
> James
Thanks for picking this up.
Will that be in the next snapshot?
Cheers
---Dave
>
Powered by blists - more mailing lists