Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Drew Fustini <fustini@kernel.org>
To: Zhanpeng Zhang <zhangzhanpeng.jasper@bytedance.com>
Cc: joro@8bytes.org, palmer@dabbelt.com, tony.luck@intel.com,
	reinette.chatre@intel.com, tomasz.jeznach@linux.dev,
	will@kernel.org, robin.murphy@arm.com, pjw@kernel.org,
	aou@eecs.berkeley.edu, alex@ghiti.fr, Dave.Martin@arm.com,
	james.morse@arm.com, babu.moger@amd.com, corbet@lwn.net,
	shuah@kernel.org, jgg@ziepe.ca, kevin.tian@intel.com,
	cuiyunhui@bytedance.com, yuanzhu@bytedance.com,
	iommu@lists.linux.dev, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kselftest@vger.kernel.org, x86@kernel.org
Subject: Re: [RFC PATCH 3/7] resctrl: Add a devices file for external requester assignment
Date: Tue, 11 Aug 2026 19:19:06 -0700	[thread overview]
Message-ID: <anvYGuNF3MC//Q94@x1> (raw)
In-Reply-To: <20260714130657.46963-4-zhangzhanpeng.jasper@bytedance.com>

On Tue, Jul 14, 2026 at 09:06:53PM +0800, Zhanpeng Zhang wrote:
> Do not overload the resctrl tasks file with architecture-specific
> non-PID tokens. The tasks ABI remains a list of task IDs, while the new
> devices file carries external requesters assigned to a resctrl group.
> 
> Add architecture hooks for assigning and showing those external
> objects, and reject group removal, reparenting, or pseudo-lock setup
> while devices are still assigned. The teardown path performs a
> best-effort reset to the default group.
> 
> The devices file is an assignment interface only. It does not describe
> a new resource schema or domain; resource allocation and monitoring
> policy remain described by the existing schemata and info files.
> 
> Signed-off-by: Zhanpeng Zhang <zhangzhanpeng.jasper@bytedance.com>
> ---
>  Documentation/filesystems/resctrl.rst |  26 ++++
>  arch/Kconfig                          |   6 +
>  fs/resctrl/rdtgroup.c                 | 206 +++++++++++++++++++++++++-
>  include/linux/resctrl.h               |  45 ++++++
>  4 files changed, 280 insertions(+), 3 deletions(-)
[..]
> diff --git a/fs/resctrl/rdtgroup.c b/fs/resctrl/rdtgroup.c
> index af2cbab14497..2e424c911049 100644
> --- a/fs/resctrl/rdtgroup.c
> +++ b/fs/resctrl/rdtgroup.c
[..]
> @@ -2067,6 +2236,16 @@ static struct rftype res_common_files[] = {
>  		.seq_show	= rdtgroup_tasks_show,
>  		.fflags		= RFTYPE_BASE,
>  	},
> +#ifdef CONFIG_ARCH_HAS_RESCTRL_DEVICES
> +	{
> +		.name		= "devices",
> +		.mode		= 0644,
> +		.kf_ops		= &rdtgroup_kf_single_ops,
> +		.write		= rdtgroup_devices_write,
> +		.seq_show	= rdtgroup_devices_show,
> +		.fflags		= RFTYPE_BASE,

Once CONFIG_ARCH_HAS_RESCTRL_DEVICES is built in, the file shows up in
every resctrl group directory, even on hardware whose IOMMU does not
implement QOSID. I think it would be better to make fflags zero so
rdtgroup_add_files() skips it, and enable it at runtime from
resctrl_init().

Thanks,
Drew

  reply	other threads:[~2026-08-12  2:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 13:06 [RFC PATCH 0/7] riscv: iommu: Add QoS ID support for resctrl device assignment Zhanpeng Zhang
2026-07-14 13:06 ` [RFC PATCH 1/7] iommu: Add group lookup by ID Zhanpeng Zhang
2026-07-14 14:03   ` Jason Gunthorpe
2026-07-15  2:54     ` Zhanpeng Zhang
2026-07-15  2:55     ` Zhanpeng Zhang
2026-07-14 13:06 ` [RFC PATCH 2/7] iommu: Add checked group device update helper Zhanpeng Zhang
2026-07-14 13:06 ` [RFC PATCH 3/7] resctrl: Add a devices file for external requester assignment Zhanpeng Zhang
2026-08-12  2:19   ` Drew Fustini [this message]
2026-08-12  2:58     ` Zhanpeng Zhang
2026-07-14 13:06 ` [RFC PATCH 4/7] iommu/riscv: Program QoS IDs for assigned groups Zhanpeng Zhang
2026-08-08 17:07   ` Drew Fustini
2026-08-12  2:33     ` Zhanpeng Zhang
2026-07-14 13:06 ` [RFC PATCH 5/7] iommu/riscv: Expose global QoS IDs in sysfs Zhanpeng Zhang
2026-08-08 17:09   ` Drew Fustini
2026-08-12  2:38     ` Zhanpeng Zhang
2026-08-11 21:21   ` Drew Fustini
2026-08-12  2:42     ` Zhanpeng Zhang
2026-07-14 13:06 ` [RFC PATCH 6/7] riscv_cbqri: Assign IOMMU groups to resource groups Zhanpeng Zhang
2026-07-14 13:06 ` [RFC PATCH 7/7] selftests/iommu: Add RISC-V IOMMU QoS smoke test Zhanpeng Zhang
2026-08-06  5:23 ` [RFC PATCH 0/7] riscv: iommu: Add QoS ID support for resctrl device assignment Drew Fustini
2026-08-06  8:42   ` Ben Horgan
2026-08-09  4:13     ` [External] " Zhanpeng Zhang

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=anvYGuNF3MC//Q94@x1 \
    --to=fustini@kernel.org \
    --cc=Dave.Martin@arm.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=babu.moger@amd.com \
    --cc=corbet@lwn.net \
    --cc=cuiyunhui@bytedance.com \
    --cc=iommu@lists.linux.dev \
    --cc=james.morse@arm.com \
    --cc=jgg@ziepe.ca \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=robin.murphy@arm.com \
    --cc=shuah@kernel.org \
    --cc=tomasz.jeznach@linux.dev \
    --cc=tony.luck@intel.com \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    --cc=yuanzhu@bytedance.com \
    --cc=zhangzhanpeng.jasper@bytedance.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