From: Babu Moger <babu.moger@amd.com>
To: Reinette Chatre <reinette.chatre@intel.com>,
tony.luck@intel.com, Dave.Martin@arm.com, james.morse@arm.com,
bp@alien8.de, ben.horgan@arm.com
Cc: corbet@lwn.net, skhan@linuxfoundation.org, rdunlap@infradead.org,
tglx@kernel.org, mingo@redhat.com, dave.hansen@linux.intel.com,
hpa@zytor.com, fenghuay@nvidia.com, akpm@linux-foundation.org,
rppt@kernel.org, dapeng1.mi@linux.intel.com, elver@google.com,
jlayton@kernel.org, enelsonmoore@gmail.com, kuba@kernel.org,
ebiggers@kernel.org, seanjc@google.com, peterz@infradead.org,
chao.gao@intel.com, jmattson@google.com, naveen@kernel.org,
ricardo.neri-calderon@linux.intel.com, tiala@microsoft.com,
chang.seok.bae@intel.com, prathyushi.nangia@amd.com,
kim.phillips@amd.com, elena.reshetova@intel.com,
darwi@linutronix.de, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v5 03/16] x86/resctrl: Add PLZA configuration definitions and data structures
Date: Wed, 16 Sep 2026 15:53:17 -0500 [thread overview]
Message-ID: <869e48d2-f6be-48e4-95ea-31526d692be6@amd.com> (raw)
In-Reply-To: <bd1fb563-15b7-480f-b80c-823c006d91b5@intel.com>
Hi Reinette,
On 9/16/26 00:16, Reinette Chatre wrote:
> Hi Babu,
>
> On 8/26/26 12:32 PM, Babu Moger wrote:
>> diff --git a/arch/x86/kernel/cpu/resctrl/internal.h b/arch/x86/kernel/cpu/resctrl/internal.h
>> index e3cfa0c10e92..2f4c60487a5d 100644
>> --- a/arch/x86/kernel/cpu/resctrl/internal.h
>> +++ b/arch/x86/kernel/cpu/resctrl/internal.h
>> @@ -222,6 +222,53 @@ union l3_qos_abmc_cfg {
>> unsigned long full;
>> };
>>
>> +/*
>
> I understand that this is not specifically kernel-doc (since no /**)
> but it clearly follows the pattern and also needs to match the
> style used in this file. Considering this, please use custom that
> describes members first before the long description? With members
> described first the long description can then use @ when referring to
> the members.
Sure.
>
>> + * Privilege Level Zero Association (PLZA) is configured via
>> + * MSR_IA32_PQR_PLZA_ASSOC. This MSR must be programmed on every CPU in
>> + * a QoS domain. Each domain supports a single PLZA CLOSID and/or RMID
>> + * association, and all fields except PLZA_EN must be programmed
>> + * identically across the domain to ensure consistent behavior.
>> + *
>> + * RMID and CLOSID selection are controlled independently. When PLZA is
>> + * enabled (plza_en = 1), CPL0 uses CLOSID and RMID values from
>> + * MSR_IA32_PQR_PLZA_ASSOC depending on the corresponding enable bits.
>> + * When PLZA is disabled (plza_en = 0), the CLOSID and RMID are always
>> + * taken from MSR_IA32_PQR_ASSOC regardless of privilege level.
>> + *
>> + * - rmid_en = 1: use the RMID programmed in this MSR.
>
> "this MSR" -> "MSR_IA32_PQR_PLZA_ASSOC" or keeping text similar to the
> rmid_en = 0 scenario may make it easier to follow what the bit accomplishes:
> - @rmid_en = 1: use the RMID from MSR_IA32_PQR_PLZA_ASSOC if
> @plza_en = 1
Sure.
>
>> + * - rmid_en = 0: use the RMID from MSR_IA32_PQR_ASSOC.
>> + * - closid_en = 1: use the CLOSID programmed in this MSR.
>
> same comment as for rmid_en bit:
> - @closid_en = 1: use the CLOSID from MSR_IA32_PQR_PLZA_ASSOC
> if @plza_en = 1
>
Sure.
>> + * - closid_en = 0: use the CLOSID from MSR_IA32_PQR_ASSOC.
>> + *
>> + * This allows PLZA to override only RMID, only CLOSID, or both. If both
>> + * rmid_en and closid_en are clear, the effective behavior is the same as
>> + * when PLZA is disabled, with RMID and CLOSID derived from
>
> "derived from" -> "used from"?
>
Sure.
Thanks
Babu
next prev parent reply other threads:[~2026-09-16 20:53 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 19:32 [PATCH v5 00/16] x86/resctrl: Add kernel-mode (e.g., PLZA) support to the resctrl subsystem Babu Moger
2026-08-26 19:32 ` [PATCH v5 01/16] x86/cpufeatures: Support Privilege Level Zero Association (PLZA) Babu Moger
2026-09-16 5:12 ` Reinette Chatre
2026-09-16 20:45 ` Babu Moger
2026-09-17 15:04 ` Reinette Chatre
2026-08-26 19:32 ` [PATCH v5 02/16] x86/resctrl: Add PLZA support to command-line options Babu Moger
2026-09-16 5:12 ` Reinette Chatre
2026-09-16 20:45 ` Babu Moger
2026-08-26 19:32 ` [PATCH v5 03/16] x86/resctrl: Add PLZA configuration definitions and data structures Babu Moger
2026-09-16 5:16 ` Reinette Chatre
2026-09-16 20:53 ` Babu Moger [this message]
2026-08-26 19:32 ` [PATCH v5 04/16] fs/resctrl: Introduce kernel mode policy enum Babu Moger
2026-09-16 5:14 ` Reinette Chatre
2026-09-16 20:53 ` Babu Moger
2026-08-26 19:32 ` [PATCH v5 05/16] x86,fs/resctrl: Introduce architecture hooks to program kernel mode Babu Moger
2026-09-16 5:26 ` Reinette Chatre
2026-09-16 20:57 ` Babu Moger
2026-08-26 19:32 ` [PATCH v5 06/16] fs/resctrl: Introduce kernel mode states for resctrl Babu Moger
2026-09-16 5:28 ` Reinette Chatre
2026-09-17 14:05 ` Babu Moger
2026-08-26 19:32 ` [PATCH v5 07/16] fs/resctrl: Introduce resctrl_set_kmode_support() to register supported modes Babu Moger
2026-09-16 5:29 ` Reinette Chatre
2026-09-17 14:20 ` Babu Moger
2026-08-26 19:32 ` [PATCH v5 08/16] x86/resctrl: Expose assign_global_enable_per_cpu when PLZA is available Babu Moger
2026-08-26 19:32 ` [PATCH v5 09/16] fs/resctrl: Add interface to display supported and active kernel modes Babu Moger
2026-09-16 5:32 ` Reinette Chatre
2026-09-17 15:29 ` Babu Moger
2026-08-26 19:32 ` [PATCH v5 10/16] fs/resctrl: Add support for hidden resource group files Babu Moger
2026-09-16 5:33 ` Reinette Chatre
2026-08-26 19:32 ` [PATCH v5 11/16] fs/resctrl: Introduce kmode_cpus/kmode_cpus_list per rdtgroup Babu Moger
2026-09-16 5:34 ` Reinette Chatre
2026-08-26 19:32 ` [PATCH v5 12/16] fs/resctrl: Program kernel mode assignments on CPU hotplug Babu Moger
2026-09-16 5:35 ` Reinette Chatre
2026-08-26 19:32 ` [PATCH v5 13/16] fs/resctrl: Deactivate the kernel mode association when a group is removed Babu Moger
2026-09-16 5:36 ` Reinette Chatre
2026-08-26 19:32 ` [PATCH v5 14/16] fs/resctrl: Add interface to modify kernel mode via info/kernel_mode Babu Moger
2026-09-16 5:50 ` Reinette Chatre
2026-08-26 19:32 ` [PATCH v5 15/16] fs/resctrl: Allow user space to write kmode_cpus/kmode_cpus_list Babu Moger
2026-08-26 19:32 ` [PATCH v5 16/16] fs/resctrl: Add documentation on kernel_mode with example Babu Moger
2026-09-01 21:14 ` Luck, Tony
2026-09-01 23:28 ` Moger, Babu
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=869e48d2-f6be-48e4-95ea-31526d692be6@amd.com \
--to=babu.moger@amd.com \
--cc=Dave.Martin@arm.com \
--cc=akpm@linux-foundation.org \
--cc=ben.horgan@arm.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=chao.gao@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=fenghuay@nvidia.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=jlayton@kernel.org \
--cc=jmattson@google.com \
--cc=kim.phillips@amd.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=naveen@kernel.org \
--cc=peterz@infradead.org \
--cc=prathyushi.nangia@amd.com \
--cc=rdunlap@infradead.org \
--cc=reinette.chatre@intel.com \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=rppt@kernel.org \
--cc=seanjc@google.com \
--cc=skhan@linuxfoundation.org \
--cc=tglx@kernel.org \
--cc=tiala@microsoft.com \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/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®