From: Reinette Chatre <reinette.chatre@intel.com>
To: Tony Luck <tony.luck@intel.com>, Fenghua Yu <fenghuay@nvidia.com>,
"Maciej Wieczor-Retman" <maciej.wieczor-retman@intel.com>,
Peter Newman <peternewman@google.com>,
James Morse <james.morse@arm.com>,
Babu Moger <babu.moger@amd.com>,
Drew Fustini <dfustini@baylibre.com>,
Dave Martin <Dave.Martin@arm.com>, Chen Yu <yu.c.chen@intel.com>
Cc: <x86@kernel.org>, <linux-kernel@vger.kernel.org>,
<patches@lists.linux.dev>, Sashiko <sashiko-bot@kernel.org>
Subject: Re: [PATCH v2] fs/resctrl: Ensure default group reports tasks on monitor-only systems
Date: Fri, 9 Oct 2026 14:19:58 -0700 [thread overview]
Message-ID: <659a5a5f-7892-42f7-a317-b0428423e554@intel.com> (raw)
In-Reply-To: <20261009193923.15498-1-tony.luck@intel.com>
On 10/9/26 12:39 PM, Tony Luck wrote:
> resctrl can be mounted on a system that supports monitoring but not allocation.
>
> On such a system reading the "tasks" file in the default group reports no
> tasks, even when there are tasks assigned to the default group. This problem
> occurs because the check for whether a task belongs to a CTRL_MON group is
> gated by a check for whether the system supports allocation.
>
> The resctrl_arch_alloc_capable() check in is_closid_match() breaks task
> reporting for the default group on monitor-only systems so remove this
> check. On systems that support allocation the check is redundant.
>
> Fixes: e6b2fac36fcc ("x86/resctrl: Use is_closid_match() in more places")
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Closes: https://sashiko.dev/#/patchset/20260831174421.13921-1-tony.luck%40intel.com?part=9
> Signed-off-by: Tony Luck <tony.luck@intel.com>
> ---
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Reinette
next prev parent reply other threads:[~2026-10-09 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 19:39 Tony Luck
2026-10-09 21:19 ` Reinette Chatre [this message]
2026-10-10 0:57 ` [tip: x86/cache] " tip-bot2 for Tony Luck
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=659a5a5f-7892-42f7-a317-b0428423e554@intel.com \
--to=reinette.chatre@intel.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=dfustini@baylibre.com \
--cc=fenghuay@nvidia.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.wieczor-retman@intel.com \
--cc=patches@lists.linux.dev \
--cc=peternewman@google.com \
--cc=sashiko-bot@kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yu.c.chen@intel.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
all inboxes | Powered by JetHome®