Archive-only list for patches
 help / color / mirror / Atom feed
From: Reinette Chatre <reinette.chatre@intel.com>
To: Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>
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>,
	<x86@kernel.org>, <linux-kernel@vger.kernel.org>,
	<patches@lists.linux.dev>
Subject: Re: [PATCH 13/32] x86,fs/resctrl: Add an architectural hook called for first mount
Date: Fri, 9 Jan 2026 07:28:25 -0800	[thread overview]
Message-ID: <f3a5f539-0843-4643-9b52-8bb7315441ed@intel.com> (raw)
In-Reply-To: <20260108174227.11307-2-tony.luck@intel.com>

Hi Tony,

On 1/8/26 9:42 AM, Tony Luck wrote:
> Enumeration of Intel telemetry events is an asynchronous process involving
> several mutually dependent drivers added as auxiliary devices during
> the device_initcall() phase of Linux boot. The process finishes after
> the probe functions of these drivers completes. But this happens after
> resctrl_arch_late_init() is executed.
> 
> Tracing the enumeration process shows that it does complete a full seven
> seconds before the earliest possible mount of the resctrl file system (when
> included in /etc/fstab for automatic mount by systemd).
> 
> Add a hook at the beginning of the mount code that will be used to check
> for telemetry events and initialize if any are found.
> 
> The hook is only called on the first mount of the resctrl file system as
> that is all that is needed for telemetry enumeration.

Needs imperative. "Only call the hook on the first mount ..."?
Although, to help with brevity, the last three sentences could be merged. For example:

	Add a hook for use by telemetry event enumeration and initialization and
	run it once at the beginning of resctrl mount without any locks held.
	Architecture is responsible for any required locking.

> 
> resctrl filesystem calls the hook with no locks held. Architecture code is
> responsible for any required locking.
> 
> Signed-off-by: Tony Luck <tony.luck@intel.com>
> ---

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

Reinette


  reply	other threads:[~2026-01-09 15:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08 17:42 [Updates to v17 PATCH 00/03] x86,fs/resctrl telemetry monitoring Tony Luck
2026-01-08 17:42 ` [PATCH 13/32] x86,fs/resctrl: Add an architectural hook called for first mount Tony Luck
2026-01-09 15:28   ` Reinette Chatre [this message]
2026-01-09 15:37     ` Borislav Petkov
2026-01-08 17:42 ` [PATCH 16/32] x86/resctrl: Discover hardware telemetry events Tony Luck
2026-01-08 17:42 ` [PATCH 29/32] x86/resctrl: Enable RDT_RESOURCE_PERF_PKG 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=f3a5f539-0843-4643-9b52-8bb7315441ed@intel.com \
    --to=reinette.chatre@intel.com \
    --cc=Dave.Martin@arm.com \
    --cc=babu.moger@amd.com \
    --cc=bp@alien8.de \
    --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=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