From: Reinette Chatre <reinette.chatre@intel.com>
To: Babu Moger <babu.moger@amd.com>, <corbet@lwn.net>,
<tony.luck@intel.com>, <Dave.Martin@arm.com>,
<james.morse@arm.com>, <tglx@linutronix.de>, <mingo@redhat.com>,
<bp@alien8.de>, <dave.hansen@linux.intel.com>
Cc: <x86@kernel.org>, <hpa@zytor.com>, <akpm@linux-foundation.org>,
<paulmck@kernel.org>, <rostedt@goodmis.org>,
<Neeraj.Upadhyay@amd.com>, <david@redhat.com>, <arnd@arndb.de>,
<fvdl@google.com>, <seanjc@google.com>, <thomas.lendacky@amd.com>,
<pawan.kumar.gupta@linux.intel.com>, <yosry.ahmed@linux.dev>,
<sohil.mehta@intel.com>, <xin@zytor.com>, <kai.huang@intel.com>,
<xiaoyao.li@intel.com>, <peterz@infradead.org>, <me@mixaill.net>,
<mario.limonciello@amd.com>, <xin3.li@intel.com>,
<ebiggers@google.com>, <ak@linux.intel.com>,
<chang.seok.bae@intel.com>, <andrew.cooper3@citrix.com>,
<perry.yuan@amd.com>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7 04/10] x86,fs/resctrl: Implement "io_alloc" enable/disable handlers
Date: Mon, 21 Jul 2025 16:32:19 -0700 [thread overview]
Message-ID: <09d7e417-0482-4172-b110-417c12558481@intel.com> (raw)
In-Reply-To: <b7c61425e9da008add366958a26f7d8e75eef4a4.1752167718.git.babu.moger@amd.com>
Hi Babu,
On 7/10/25 10:16 AM, Babu Moger wrote:
> "io_alloc" enables direct insertion of data from I/O devices into the
> cache.
>
> On AMD systems, "io_alloc" feature is backed by L3 Smart Data Cache
> Injection Allocation Enforcement (SDCIAE). Change SDCIAE state by setting
> (to enable) or clearing (to disable) bit 1 of MSR L3_QOS_EXT_CFG on all
> logical processors within the cache domain.
>
> Introduce architecture-specific call to enable and disable the feature.
>
> The SDCIAE feature details are available in APM listed below [1].
> [1] AMD64 Architecture Programmer's Manual Volume 2: System Programming
> Publication # 24593 Revision 3.41 section 19.4.7 L3 Smart Data Cache
> Injection Allocation Enforcement (SDCIAE)
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=206537
> Signed-off-by: Babu Moger <babu.moger@amd.com>
> ---
...
>
> diff --git a/arch/x86/kernel/cpu/resctrl/rdtgroup.c b/arch/x86/kernel/cpu/resctrl/rdtgroup.c
> index 885026468440..c165ac333336 100644
> --- a/arch/x86/kernel/cpu/resctrl/rdtgroup.c
> +++ b/arch/x86/kernel/cpu/resctrl/rdtgroup.c
The code looks good to me but rdtgroup.c is becoming bloated by being the default place for
any resctrl changes. While I do know there are counter examples (and I admit I do
not have a clear understanding of original intent) ctrlmondata.c is documented and supported
by its content as the place for cache allocation code. Could you please move these changes
to arch/x86/kernel/cpu/resctrl/ctrlmondata.c? I will try to highlight the other places where
I believe the either fs/resctrl/ctrlmondata.c or arch/x86/kernel/cpu/resctrl/ctrlmondata.c is
more appropriate but please as a high level consider where appropriate to move the IO alloc
code to be with the rest of the cache allocation code. Looking at the series it will help keep
a couple of existing static functions static and keep data structures local to cache allocation
code.
Reinette
next prev parent reply other threads:[~2025-07-21 23:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 17:16 [PATCH v7 00/10] x86,fs/resctrl: Support L3 Smart Data Cache Injection Allocation Enforcement (SDCIAE) Babu Moger
2025-07-10 17:16 ` [PATCH v7 01/10] x86/cpufeatures: Add support for L3 Smart Data Cache Injection Allocation Enforcement Babu Moger
2025-07-10 23:26 ` Borislav Petkov
2025-07-21 23:28 ` Reinette Chatre
2025-07-10 17:16 ` [PATCH v7 02/10] x86/resctrl: Add SDCIAE feature in the command line options Babu Moger
2025-07-21 23:29 ` Reinette Chatre
2025-07-31 16:28 ` Moger, Babu
2025-07-10 17:16 ` [PATCH v7 03/10] x86,fs/resctrl: Detect io_alloc feature Babu Moger
2025-07-21 23:29 ` Reinette Chatre
2025-07-10 17:16 ` [PATCH v7 04/10] x86,fs/resctrl: Implement "io_alloc" enable/disable handlers Babu Moger
2025-07-21 23:32 ` Reinette Chatre [this message]
2025-07-31 17:40 ` Moger, Babu
2025-07-10 17:16 ` [PATCH v7 05/10] fs/resctrl: Update bit_usage to reflect io_alloc Babu Moger
2025-07-21 23:35 ` Reinette Chatre
2025-08-04 21:20 ` Moger, Babu
2025-07-10 17:16 ` [PATCH v7 06/10] fs/resctrl: Introduce interface to display "io_alloc" support Babu Moger
2025-07-21 23:36 ` Reinette Chatre
2025-07-31 18:51 ` Moger, Babu
2025-07-10 17:16 ` [PATCH v7 07/10] fs/resctrl: Add user interface to enable/disable io_alloc feature Babu Moger
2025-07-21 23:40 ` Reinette Chatre
2025-07-31 22:52 ` Moger, Babu
2025-08-04 16:07 ` Reinette Chatre
2025-08-04 17:14 ` Moger, Babu
2025-07-10 17:16 ` [PATCH v7 08/10] fs/resctrl: Introduce interface to display io_alloc CBMs Babu Moger
2025-07-21 23:42 ` Reinette Chatre
2025-08-04 18:14 ` Moger, Babu
2025-07-10 17:16 ` [PATCH v7 09/10] fs/resctrl: Modify rdt_parse_data to pass mode and CLOSID Babu Moger
2025-07-22 3:30 ` Reinette Chatre
2025-08-04 19:32 ` Moger, Babu
2025-07-10 17:16 ` [PATCH v7 10/10] fs/resctrl: Introduce interface to modify io_alloc Capacity Bit Masks Babu Moger
2025-07-22 3:32 ` Reinette Chatre
2025-08-04 21:01 ` Moger, Babu
2025-07-21 23:28 ` [PATCH v7 00/10] x86,fs/resctrl: Support L3 Smart Data Cache Injection Allocation Enforcement (SDCIAE) Reinette Chatre
2025-08-04 21:34 ` 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=09d7e417-0482-4172-b110-417c12558481@intel.com \
--to=reinette.chatre@intel.com \
--cc=Dave.Martin@arm.com \
--cc=Neeraj.Upadhyay@amd.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=arnd@arndb.de \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=ebiggers@google.com \
--cc=fvdl@google.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=kai.huang@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=me@mixaill.net \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=perry.yuan@amd.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=seanjc@google.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=xiaoyao.li@intel.com \
--cc=xin3.li@intel.com \
--cc=xin@zytor.com \
--cc=yosry.ahmed@linux.dev \
/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
Powered by JetHome