linux-kernel - Re: [PATCH v10 05/10] fs/resctrl: Introduce interface to display "io

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c6afde47-2af2-4e13-ad2f-353625e2f708@intel.com>
Date: Fri, 24 Oct 2025 16:40:08 -0700
From: Reinette Chatre <reinette.chatre@...el.com>
To: Babu Moger <babu.moger@....com>, <tony.luck@...el.com>,
	<tglx@...utronix.de>, <mingo@...hat.com>, <bp@...en8.de>,
	<dave.hansen@...ux.intel.com>
CC: <corbet@....net>, <Dave.Martin@....com>, <james.morse@....com>,
	<x86@...nel.org>, <hpa@...or.com>, <akpm@...ux-foundation.org>,
	<paulmck@...nel.org>, <rdunlap@...radead.org>, <pmladek@...e.com>,
	<kees@...nel.org>, <arnd@...db.de>, <fvdl@...gle.com>, <seanjc@...gle.com>,
	<pawan.kumar.gupta@...ux.intel.com>, <xin@...or.com>,
	<thomas.lendacky@....com>, <sohil.mehta@...el.com>, <jarkko@...nel.org>,
	<chang.seok.bae@...el.com>, <ebiggers@...gle.com>,
	<elena.reshetova@...el.com>, <ak@...ux.intel.com>,
	<mario.limonciello@....com>, <perry.yuan@....com>,
	<linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<peternewman@...gle.com>
Subject: Re: [PATCH v10 05/10] fs/resctrl: Introduce interface to display
 "io_alloc" support

Hi Babu,

On 10/21/25 4:54 PM, Babu Moger wrote:
> Introduce the "io_alloc" resctrl file to the "info" area of a cache
> resource, for example /sys/fs/resctrl/info/L3/io_alloc. "io_alloc"
> indicates support for the "io_alloc" feature that allows direct insertion
> of data from I/O devices into the cache.
> 
> Restrict exposing support for "io_alloc" to the L3 resource that is the
> only resource where this feature can be backed by AMD's L3 Smart Data Cache
> Injection Allocation Enforcement (SDCIAE). With that, the "io_alloc" file
> is only visible to user space if the L3 resource supports "io_alloc". Doing
> so makes the file visible for all cache resources though, for example also
> L2 cache (if it supports cache allocation). As a consequence, add
> capability for file to report expected "enabled" and "disabled", as well as
> "not supported".
> 
> Signed-off-by: Babu Moger <babu.moger@....com>
> ---

Reviewed-by: Reinette Chatre <reinette.chatre@...el.com>

Reinette