linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "David E. Box" <david.e.box@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	platform-driver-x86@vger.kernel.org,
	 srinivas.pandruvada@linux.intel.com,
	 Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	tony.luck@intel.com,  xi.pardee@linux.intel.com,
	Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH 09/15] docs: Add ABI documentation for intel_pmt feature directories
Date: Tue, 20 May 2025 17:51:44 +0300 (EEST)	[thread overview]
Message-ID: <faecf78c-ee7e-686b-ab1d-f040050c55d8@linux.intel.com> (raw)
In-Reply-To: <20250430212106.369208-10-david.e.box@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 6704 bytes --]

On Wed, 30 Apr 2025, David E. Box wrote:

> Add a new sysfs ABI documentation file describing the layout and content of
> the features-<PCI BDF>/ directory used by Intel PMT (Platform Monitoring
> Technology). This directory exposes telemetry and control feature details
> for a given PMT PCI device.
> 
> Signed-off-by: David E. Box <david.e.box@linux.intel.com>
> ---
>  .../testing/sysfs-class-intel_pmt-features    | 128 ++++++++++++++++++
>  MAINTAINERS                                   |   1 +
>  2 files changed, 129 insertions(+)
>  create mode 100644 Documentation/ABI/testing/sysfs-class-intel_pmt-features
> 
> diff --git a/Documentation/ABI/testing/sysfs-class-intel_pmt-features b/Documentation/ABI/testing/sysfs-class-intel_pmt-features
> new file mode 100644
> index 000000000000..6dfb9b4b30b5
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-class-intel_pmt-features
> @@ -0,0 +1,128 @@
> +What:          /sys/class/intel_pmt/features-<PCI BDF>/
> +Date:          2025-04-24
> +KernelVersion: 6.16
> +Contact:       david.e.box@linux.intel.com
> +Description:
> +               The `features-<PCI BDF>/` directory represents the "features"
> +               capability exposed by Intel PMT (Platform Monitoring Technology)
> +               for the given PCI device.
> +
> +               Each directory corresponds to a PMT feature and contains
> +               attributes describing the available telemetry, monitoring, or
> +               control functionalities.
> +
> +Directory Structure:
> +
> +  /sys/class/intel_pmt/features-<PCI BDF>/
> +  ├── accelerator_telemetry/		# Per-accelerator telemetry data
> +  ├── crash_log/			# Contains system crash telemetry logs
> +  ├── per_core_environment_telemetry/	# Environmental telemetry per core
> +  ├── per_core_performance_telemetry/	# Performance telemetry per core
> +  ├── per_rmid_energy_telemetry/	# Energy telemetry for RMIDs
> +  ├── per_rmid_perf_telemetry/		# Performance telemetry for RMIDs
> +  ├── tpmi_control/			# TPMI-related controls and telemetry
> +  ├── tracing/				# PMT tracing features
> +  └── uncore_telemetry/			# Uncore telemetry data
> +
> +Common Files (Present in all feature directories):
> +
> +  caps
> +    - Read-only
> +    - Lists available capabilities for this feature.
> +
> +  guids
> +    - Read-only
> +    - Lists GUIDs associated with this feature.
> +
> +Additional Attributes (Conditional Presence):
> +
> +  max_command_size
> +    - Read-only
> +    - Present if the feature supports out-of-band MCTP access.
> +    - Maximum supported MCTP command size for out-of-band PMT access (bytes).
> +
> +  max_stream_size
> +    - Read-only
> +    - Present if the feature supports out-of-band MCTP access.
> +    - Maximum supported MCTP stream size (bytes).
> +
> +  min_watcher_period_ms
> +    - Read-only
> +    - Present if the feature supports the watcher API.
> +    - Minimum supported time period for the watcher interface (milliseconds).
> +
> +  num_rmids
> +    - Read-only
> +    - Present if the feature supports RMID telemetry.
> +    - Maximum number of RMIDs tracked simultaneously.
> +
> +Example:
> +For a device with PCI BDF `0000:00:03.1`, the directory tree could look like:
> +
> +  /sys/class/intel_pmt/features-0000:00:03.1/
> +  ├── accelerator_telemetry/
> +  │   ├── caps
> +  │   ├── guids
> +  │   ├── max_command_size
> +  │   ├── max_stream_size
> +  │   ├── min_watcher_period_ms
> +  ├── crash_log/
> +  │   ├── caps
> +  │   ├── guids
> +  │   ├── max_command_size
> +  │   ├── max_stream_size
> +  ├── per_core_environment_telemetry/
> +  │   ├── caps
> +  │   ├── guids
> +  │   ├── max_command_size
> +  │   ├── max_stream_size
> +  │   ├── min_watcher_period_ms
> +  ├── per_rmid_energy_telemetry/
> +  │   ├── caps
> +  │   ├── guids
> +  │   ├── max_command_size
> +  │   ├── max_stream_size
> +  │   ├── min_watcher_period_ms
> +  │   ├── num_rmids
> +  ├── tpmi_control/
> +  │   ├── caps
> +  │   ├── guids
> +  ├── tracing/
> +  │   ├── caps
> +  │   ├── guids
> +  ├── uncore_telemetry/
> +  │   ├── caps
> +  │   ├── guids
> +  │   ├── max_command_size
> +  │   ├── max_stream_size
> +  │   ├── min_watcher_period_ms
> +
> +Notes:
> +  - Some attributes are only present if the corresponding feature supports
> +    the capability (e.g., `max_command_size` for MCTP-capable features).
> +  - Features supporting RMIDs include `num_rmids`.
> +  - Features supporting the watcher API include `min_watcher_period_ms`.
> +  - The `caps` file provides additional information about the functionality
> +    of the feature.
> +
> +Example 'caps' content for the 'tracing' feature:
> +
> +  /sys/class/intel_pmt/features-0000:00:03.1/
> +  ├── tracing/
> +  │   ├── caps
> +
> +	telemetry                                Available: No
> +	watcher                                  Available: Yes
> +	crashlog                                 Available: No
> +	streaming                                Available: No
> +	threashold                               Available: No
> +	window                                   Available: No
> +	config                                   Available: Yes
> +	tracing                                  Available: No
> +	inband                                   Available: Yes
> +	oob                                      Available: Yes
> +	secure_chan                              Available: No
> +	pmt_sp                                   Available: Yes
> +	PMT SP Policy                            Available: Yes
> +	mailbox                                  Available: Yes
> +	bios_lock                                Available: Yes

It would be good to open RMID somewhere as I'm not sure if that acronym 
is well-known.

> diff --git a/MAINTAINERS b/MAINTAINERS
> index bd9f99585894..10338ea81667 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -12181,6 +12181,7 @@ INTEL PMT DRIVERS
>  M:	David E. Box <david.e.box@linux.intel.com>
>  S:	Supported
>  F:	Documentation/ABI/testing/sysfs-class-intel_pmt
> +F:	Documentation/ABI/testing/sysfs-class-intel_pmt-features
>  F:	drivers/platform/x86/intel/pmt/
>  
>  INTEL PRO/WIRELESS 2100, 2200BG, 2915ABG NETWORK CONNECTION SUPPORT
> 

-- 
 i.

  reply	other threads:[~2025-05-20 14:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-30 21:20 [PATCH 00/15] Intel VSEC/PMT: Introduce Discovery Driver David E. Box
2025-04-30 21:20 ` [PATCH 01/15] MAINTAINERS: Add link to documentation of Intel PMT ABI David E. Box
2025-04-30 21:20 ` [PATCH 02/15] platform/x86/intel/vsec: Add private data for per-device data David E. Box
2025-04-30 21:20 ` [PATCH 03/15] platform/x86/intel/vsec: Create wrapper to walk PCI config space David E. Box
2025-04-30 21:20 ` [PATCH 04/15] platform/x86/intel/vsec: Add device links to enforce dependencies David E. Box
2025-05-20 13:51   ` Ilpo Järvinen
2025-06-16 16:04     ` David E. Box
2025-04-30 21:20 ` [PATCH 05/15] platform/x86/intel/vsec: Skip absent features during initialization David E. Box
2025-04-30 21:20 ` [PATCH 06/15] platform/x86/intel/vsec: Skip driverless features David E. Box
2025-04-30 21:20 ` [PATCH 07/15] platform/x86/intel/vsec: Add new Discovery feature David E. Box
2025-05-20 14:01   ` Ilpo Järvinen
2025-04-30 21:20 ` [PATCH 08/15] platform/x86/intel/pmt: Add PMT Discovery driver David E. Box
2025-05-20 14:32   ` Ilpo Järvinen
2025-05-20 20:59     ` David E. Box
2025-04-30 21:20 ` [PATCH 09/15] docs: Add ABI documentation for intel_pmt feature directories David E. Box
2025-05-20 14:51   ` Ilpo Järvinen [this message]
2025-04-30 21:20 ` [PATCH 10/15] platform/x86/intel/tpmi: Relocate platform info to intel_vsec.h David E. Box
2025-05-20 14:54   ` Ilpo Järvinen
2025-04-30 21:21 ` [PATCH 11/15] platform/x86/intel/vsec: Set OOBMSM to CPU mapping David E. Box
2025-04-30 21:21 ` [PATCH 12/15] platform/x86/intel/tpmi: Get OOBMSM CPU mapping from TPMI David E. Box
2025-04-30 21:21 ` [PATCH 13/15] platform/x86/intel/pmt/discovery: Get telemetry attributes David E. Box
2025-04-30 21:21 ` [PATCH 14/15] platform/x86/intel/pmt/telemetry: Add API to retrieve telemetry regions by feature David E. Box
2025-05-20 15:05   ` Ilpo Järvinen
2025-04-30 21:21 ` [PATCH 15/15] platform/x86/intel/pmt: KUNIT test for PMT Enhanced Discovery API David E. Box
2025-05-16 15:30 ` [PATCH 00/15] Intel VSEC/PMT: Introduce Discovery Driver Luck, Tony
2025-05-19 17:22   ` Luck, Tony
2025-05-19 17:32     ` Ilpo Järvinen

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=faecf78c-ee7e-686b-ab1d-f040050c55d8@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=david.e.box@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=tony.luck@intel.com \
    --cc=xi.pardee@linux.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;
as well as URLs for NNTP newsgroup(s).