mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Martin <Dave.Martin@arm.com>
To: James Morse <james.morse@arm.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Shaopeng Tan <tan.shaopeng@jp.fujitsu.com>
Subject: Re: [PATCH] arm_mpam: Relax num_rmids parameter advertised to userspace
Date: Fri, 29 Aug 2025 13:26:49 +0100	[thread overview]
Message-ID: <aLGciannXznRgwsb@e133380.arm.com> (raw)
In-Reply-To: <58eae4c3-51b3-48ad-b077-aefdff969119@arm.com>

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
> 

  reply	other threads:[~2025-08-29 12:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-20 13:15 Dave Martin
2025-08-27 17:16 ` James Morse
2025-08-29 12:26   ` Dave Martin [this message]
2025-09-08  8:31 ` Shaopeng Tan (Fujitsu)

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=aLGciannXznRgwsb@e133380.arm.com \
    --to=dave.martin@arm.com \
    --cc=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tan.shaopeng@jp.fujitsu.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®