From: "Moger, Babu" <bmoger@amd.com>
To: Reinette Chatre <reinette.chatre@intel.com>,
Babu Moger <babu.moger@amd.com>,
corbet@lwn.net, tony.luck@intel.com, Dave.Martin@arm.com,
james.morse@arm.com, tglx@kernel.org, bp@alien8.de,
ben.horgan@arm.com, fenghuay@nvidia.com
Cc: skhan@linuxfoundation.org, x86@kernel.org, mingo@redhat.com,
dave.hansen@linux.intel.com, hpa@zytor.com,
akpm@linux-foundation.org, rdunlap@infradead.org,
peterz@infradead.org, feng.tang@linux.alibaba.com,
dapeng1.mi@linux.intel.com, elver@google.com,
enelsonmoore@gmail.com, kuba@kernel.org, ebiggers@kernel.org,
lirongqing@baidu.com, seanjc@google.com, nikunj@amd.com,
xin@zytor.com, pawan.kumar.gupta@linux.intel.com,
tiala@microsoft.com, chang.seok.bae@intel.com,
kprateek.nayak@amd.com, prathyushi.nangia@amd.com,
kim.phillips@amd.com, naveen@kernel.org, darwi@linutronix.de,
elena.reshetova@intel.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, thomas.lendacky@amd.com,
eranian@google.com, peternewman@google.com,
qinyuntan@linux.alibaba.com
Subject: Re: [RESEND PATCH v4 03/15] x86/resctrl: Add data structures and definitions for PLZA configuration
Date: Wed, 12 Aug 2026 09:18:33 -0500 [thread overview]
Message-ID: <b94c742d-4b90-4c61-a86a-62df35ac5ff5@amd.com> (raw)
In-Reply-To: <0cc07711-3d81-4785-81dc-804178fb443c@intel.com>
Hi Reinette,
On 8/11/2026 6:51 PM, Reinette Chatre wrote:
> Hi Babu,
>
> On 8/11/26 2:10 PM, Babu Moger wrote:
>> On 8/10/26 21:58, Reinette Chatre wrote:
>>> On 7/7/26 2:50 PM, Babu Moger wrote:
>>>> Privilege Level Zero Association (PLZA) allows the kernel to use a
>>>> different CLOSID (and optionally RMID) than user mode on entry to kernel
>>>> mode. The CLOSID/RMID association is programmed per CPU via
>>>
>>> CLOSID is also optional, no? I am not able to recall now why this is not made
>>> optional in this implementation though. Could you please remind me and add
>>> it to the changelog for next time?
>>
>>
>> Yes, CLOSID is optional as well. Since PLZA was primarily focused on
>> allocation, I hadn't considered that use case initially. However,
>> there may be scenarios where a user wants to monitor kernel activity
>> without affecting or changing the existing allocation configuration.
>> That would introduce an additional operating mode(See below).
>
> ok.
>
> I think doing so will simplify supporting the different modes across systems
> that may not support allocation or monitoring.
Ack.
>> INHERIT_CTRL_AND_MON:
>> Kernel work inherits the allocation and monitoring from the user space
>> task. On x86 this means that kernel work shares the same CLOSID and
>> RMID as the user space task. This matches today's resctrl behavior.
>>
>> GLOBAL_ASSIGN_CTRL_INHERIT_MON_PER_CPU:
>> Kernel work uses a globally assigned allocation while monitoring is
>> inherited from the user space task. On x86 this means a CLOSID is
>> assigned for kernel work and the RMID is inherited from the user space
>> task. Default scope is all online CPUs; a subset may be selected via
>> the resctrl group interface. A CTRL_MON group is bound to this mode.
>>
>> GLOBAL_ASSIGN_CTRL_ASSIGN_MON_PER_CPU:
>> Kernel work uses globally assigned allocation and monitoring. On x86
>> this means both CLOSID and RMID are assigned for kernel work. Default
>> scope is all online CPUs; a subset may be selected via the resctrl
>> group interface. A CTRL_MON or MON group is bound to this mode.
>>
>> GLOBAL_INHERIT_CTRL_ASSIGN_MON_PER_CPU: <--- New mode
>> Kernel work inherits the allocation from user task and monitoring is
>> globally assigned for kernel work. On x86 this means that kernel
>> work shares the same CLOSID as user task and kernel work user
>> globally assigned RMID. A MON group is bound to this mode.
>
> I provided comments about this text in following patch. Apart from that,
> I think a CTRL_MON or MON group could be assigned to this mode?
>
Yes. It can be CTRL_MON or MON group.
thanks
Babu
next prev parent reply other threads:[~2026-08-12 14:19 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 21:50 [RESEND PATCH v4 00/15] x86/resctrl: Add kernel-mode (e.g., PLZA) support to the resctrl subsystem Babu Moger
2026-07-07 21:50 ` [RESEND PATCH v4 01/15] x86/resctrl: Support Privilege Level Zero Association (PLZA) Babu Moger
2026-07-07 22:01 ` Borislav Petkov
2026-07-08 14:51 ` Babu Moger
2026-07-08 17:27 ` Borislav Petkov
2026-07-08 16:55 ` Babu Moger
2026-07-08 23:28 ` Borislav Petkov
2026-07-09 0:00 ` Namhyung Kim
2026-07-09 0:12 ` Borislav Petkov
2026-07-10 0:55 ` Namhyung Kim
2026-07-10 1:46 ` Borislav Petkov
2026-08-11 2:51 ` Reinette Chatre
2026-08-11 20:02 ` Babu Moger
2026-07-07 21:50 ` [RESEND PATCH v4 02/15] x86/resctrl: Add PLZA support to command-line options Babu Moger
2026-07-08 17:39 ` Babu Moger
2026-08-11 2:53 ` Reinette Chatre
2026-08-11 20:03 ` Babu Moger
2026-07-07 21:50 ` [RESEND PATCH v4 03/15] x86/resctrl: Add data structures and definitions for PLZA configuration Babu Moger
2026-07-08 20:20 ` Babu Moger
2026-08-11 2:58 ` Reinette Chatre
2026-08-11 21:10 ` Babu Moger
2026-08-11 23:51 ` Reinette Chatre
2026-08-12 14:18 ` Moger, Babu [this message]
2026-07-07 21:50 ` [RESEND PATCH v4 04/15] fs/resctrl: Introduce kernel mode (kmode) data structures Babu Moger
2026-07-08 20:56 ` Babu Moger
2026-08-11 3:03 ` Reinette Chatre
2026-08-12 19:58 ` Moger, Babu
2026-08-12 23:28 ` Reinette Chatre
2026-07-07 21:50 ` [RESEND PATCH v4 05/15] x86,fs/resctrl: Introduce architecture hooks to program kernel-mode Babu Moger
2026-07-08 23:04 ` Moger, Babu
2026-08-11 3:14 ` Reinette Chatre
2026-08-12 22:11 ` Moger, Babu
2026-08-12 23:34 ` Reinette Chatre
2026-07-07 21:50 ` [RESEND PATCH v4 06/15] fs/resctrl: Introduce resctrl_set_kmode_support() to initialize supported modes Babu Moger
2026-08-11 3:16 ` Reinette Chatre
2026-08-12 22:28 ` Moger, Babu
2026-07-07 21:50 ` [RESEND PATCH v4 07/15] x86/resctrl: Expose the supported PLZA kernel-mode policies during init Babu Moger
2026-07-09 15:15 ` Babu Moger
2026-07-07 21:50 ` [RESEND PATCH v4 08/15] fs/resctrl: Add interface to display supported and active kernel-mode policy Babu Moger
2026-08-11 3:18 ` Reinette Chatre
2026-08-12 22:57 ` Moger, Babu
2026-08-12 23:38 ` Reinette Chatre
2026-07-07 21:50 ` [RESEND PATCH v4 09/15] fs/resctrl: Introduce kmode_cpus/kmode_cpus_list per rdtgroup Babu Moger
2026-08-11 3:20 ` Reinette Chatre
2026-07-07 21:50 ` [RESEND PATCH v4 10/15] fs/resctrl: Reset the kernel-mode binding when an rdtgroup is removed Babu Moger
2026-07-09 18:15 ` Babu Moger
2026-08-11 3:29 ` Reinette Chatre
2026-07-07 21:50 ` [RESEND PATCH v4 11/15] fs/resctrl: Program kernel-mode binding when CPU comes online Babu Moger
2026-07-09 20:01 ` Babu Moger
2026-07-07 21:50 ` [RESEND PATCH v4 12/15] fs/resctrl: Hide kmode_cpus[_list] on groups not bound to kernel-mode Babu Moger
2026-08-11 3:30 ` Reinette Chatre
2026-07-07 21:50 ` [RESEND PATCH v4 13/15] fs/resctrl: Add interface to modify kernel-mode via info/kernel_mode Babu Moger
2026-07-09 22:46 ` Moger, Babu
2026-08-11 3:40 ` Reinette Chatre
2026-07-07 21:50 ` [RESEND PATCH v4 14/15] fs/resctrl: Allow user space to write kmode_cpus/kmode_cpus_list Babu Moger
2026-07-09 23:14 ` Moger, Babu
2026-08-11 3:49 ` Reinette Chatre
2026-07-07 21:50 ` [RESEND PATCH v4 15/15] fs/resctrl: Add documentation on kernel_mode with example Babu Moger
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=b94c742d-4b90-4c61-a86a-62df35ac5ff5@amd.com \
--to=bmoger@amd.com \
--cc=Dave.Martin@arm.com \
--cc=akpm@linux-foundation.org \
--cc=babu.moger@amd.com \
--cc=ben.horgan@arm.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=corbet@lwn.net \
--cc=dapeng1.mi@linux.intel.com \
--cc=darwi@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=ebiggers@kernel.org \
--cc=elena.reshetova@intel.com \
--cc=elver@google.com \
--cc=enelsonmoore@gmail.com \
--cc=eranian@google.com \
--cc=feng.tang@linux.alibaba.com \
--cc=fenghuay@nvidia.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=kim.phillips@amd.com \
--cc=kprateek.nayak@amd.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=mingo@redhat.com \
--cc=naveen@kernel.org \
--cc=nikunj@amd.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peternewman@google.com \
--cc=peterz@infradead.org \
--cc=prathyushi.nangia@amd.com \
--cc=qinyuntan@linux.alibaba.com \
--cc=rdunlap@infradead.org \
--cc=reinette.chatre@intel.com \
--cc=seanjc@google.com \
--cc=skhan@linuxfoundation.org \
--cc=tglx@kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=tiala@microsoft.com \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=xin@zytor.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