From: "Luck, Tony" <tony.luck@intel.com>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: 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>,
David E Box <david.e.box@intel.com>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>, <patches@lists.linux.dev>
Subject: Re: [PATCH v4 3/7] fs/resctrl: Add interface to disable a monitor event
Date: Mon, 6 Apr 2026 11:35:21 -0700 [thread overview]
Message-ID: <adP86aXVJONQCFc3@agluck-desk3> (raw)
In-Reply-To: <7fe71e6c-e447-4aac-aac8-30941e755209@intel.com>
Hi Reinette,
On Fri, Apr 03, 2026 at 05:03:28PM -0700, Reinette Chatre wrote:
> Hi Tony,
>
> On 3/30/26 2:43 PM, Tony Luck wrote:
> > Architecture code can ask file system code to enable events. But there
> > is no way to clean up and disable events.
>
> Missing why it is required to disable events.
Will add rationale.
> >
> > Add resctrl_disable_mon_event().
>
> (can be seen from patch)
Will drop this part of comment.
> > Adding/removing events is only
> > possible when the file system is not mounted. Add a WARN_ON() to
>
> While this is accurate that it should not be possible to enable/disable
> events while resctrl is mounted, this is *not* the *only* time when it
> should not be possible. Here it is unfortunately not straight forward
> since only some events require per-domain state which requires the event
> to be enabled before any domain comes online, potentially very early in
> initialization.
>
> To me the addition of this warning adds false security.
>
> Also, consider that resctrl_mounted is protected by rdtgroup_mutex and
> this addition gives architecture code free access without any protection.
This is a problem.
> To do this right resctrl may need to add more state to an event but how
> that may look is unclear since an architecture may require per-domain
> architectural state for an event while resctrl fs needs none.
The extra state for an event could be a pair of pointers to file system functions
to be used by resctrl_{en,disable}_mon_event() to allocate/clean up any state needed
by file system code for each event.
But this might lead to a rabbit hole of adding complexity. May someday
be useful if we ever make resctrl a loadable module.
> At this
> time these scenarios may just fall into the "architecture must do the
> right thing" category since it has best information on how state is
> managed for the events as they are enabled/disabled.
Are you suggesting to just drop the check for resctrl_mounted (as both
a locking issue, and an incomplete solution)?
> Reinette
-Tony
next prev parent reply other threads:[~2026-04-06 18:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 21:43 [PATCH v4 0/7] Allow AET to use PMT/TPMI as loadable modules Tony Luck
2026-03-30 21:43 ` [PATCH v4 1/7] platform/x86/intel/pmt: Export PMT enumeration functions as GPL Tony Luck
2026-04-04 0:00 ` Reinette Chatre
2026-04-06 18:07 ` David Box
2026-04-08 5:07 ` Christoph Hellwig
2026-04-08 17:01 ` Luck, Tony
2026-04-09 5:41 ` Christoph Hellwig
2026-03-30 21:43 ` [PATCH v4 2/7] x86/resctrl: Drop setting of event_group::force_off when insufficient RMIDs Tony Luck
2026-04-04 0:01 ` Reinette Chatre
2026-03-30 21:43 ` [PATCH v4 3/7] fs/resctrl: Add interface to disable a monitor event Tony Luck
2026-04-04 0:03 ` Reinette Chatre
2026-04-06 18:35 ` Luck, Tony [this message]
2026-04-06 21:13 ` Reinette Chatre
2026-04-07 18:40 ` Luck, Tony
2026-04-07 23:10 ` Reinette Chatre
2026-03-30 21:43 ` [PATCH v4 4/7] fs,x86/resctrl: Add architecture hooks for every mount/unmount Tony Luck
2026-04-04 0:52 ` Reinette Chatre
2026-04-06 20:35 ` Luck, Tony
2026-04-06 21:16 ` Reinette Chatre
2026-04-09 20:35 ` Luck, Tony
2026-04-10 15:16 ` Reinette Chatre
2026-04-10 18:59 ` Luck, Tony
2026-04-10 21:21 ` Reinette Chatre
2026-04-10 23:03 ` Luck, Tony
2026-03-30 21:43 ` [PATCH v4 5/7] x86/resctrl: Resolve PMT and TPMI symbols at runtime Tony Luck
2026-04-04 0:56 ` Reinette Chatre
2026-04-07 18:13 ` Luck, Tony
2026-04-07 18:40 ` Reinette Chatre
2026-04-07 20:33 ` Luck, Tony
2026-03-30 21:43 ` [PATCH v4 6/7] x86/resctrl: Delete intel_aet_exit() Tony Luck
2026-03-30 21:43 ` [PATCH v4 7/7] x86/resctrl: Downgrade dependency of AET on INTEL_PMT 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=adP86aXVJONQCFc3@agluck-desk3 \
--to=tony.luck@intel.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=david.e.box@intel.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=reinette.chatre@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