From: "David E. Box" <firstname.lastname@example.org> To: Andy Shevchenko <email@example.com>, Lee Jones <firstname.lastname@example.org> Cc: Darren Hart <email@example.com>, Andy Shevchenko <firstname.lastname@example.org>, Bjorn Helgaas <email@example.com>, Alexander Duyck <firstname.lastname@example.org>, Linux Kernel Mailing List <email@example.com>, Platform Driver <firstname.lastname@example.org>, linux-pci <email@example.com> Subject: Re: [PATCH V4 0/3] Intel Platform Monitoring Technology Date: Mon, 27 Jul 2020 09:29:00 -0700 Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CAHp75VftSf8pzSAYMjcKg-MSiy0T4xG=wiKpgY20_ZKOO0Tq0w@mail.gmail.com> On Mon, 2020-07-27 at 13:23 +0300, Andy Shevchenko wrote: > On Fri, Jul 17, 2020 at 10:05 PM David E. Box > <email@example.com> wrote: > > Intel Platform Monitoring Technology (PMT) is an architecture for > > enumerating and accessing hardware monitoring capabilities on a > > device. > > With customers increasingly asking for hardware telemetry, > > engineers not > > only have to figure out how to measure and collect data, but also > > how to > > deliver it and make it discoverable. The latter may be through some > > device > > specific method requiring device specific tools to collect the > > data. This > > in turn requires customers to manage a suite of different tools in > > order to > > collect the differing assortment of monitoring data on their > > systems. Even > > when such information can be provided in kernel drivers, they may > > require > > constant maintenance to update register mappings as they change > > with > > firmware updates and new versions of hardware. PMT provides a > > solution for > > discovering and reading telemetry from a device through a hardware > > agnostic > > framework that allows for updates to systems without requiring > > patches to > > the kernel or software tools. > > > > PMT defines several capabilities to support collecting monitoring > > data from > > hardware. All are discoverable as separate instances of the PCIE > > Designated > > Vendor extended capability (DVSEC) with the Intel vendor code. The > > DVSEC ID > > field uniquely identifies the capability. Each DVSEC also provides > > a BAR > > offset to a header that defines capability-specific attributes, > > including > > GUID, feature type, offset and length, as well as configuration > > settings > > where applicable. The GUID uniquely identifies the register space > > of any > > monitor data exposed by the capability. The GUID is associated with > > an XML > > file from the vendor that describes the mapping of the register > > space along > > with properties of the monitor data. This allows vendors to perform > > firmware updates that can change the mapping (e.g. add new metrics) > > without > > requiring any changes to drivers or software tools. The new mapping > > is > > confirmed by an updated GUID, read from the hardware, which > > software uses > > with a new XML. > > > > The current capabilities defined by PMT are Telemetry, Watcher, and > > Crashlog. The Telemetry capability provides access to a continuous > > block > > of read only data. The Watcher capability provides access to > > hardware > > sampling and tracing features. Crashlog provides access to device > > crash > > dumps. While there is some relationship between capabilities > > (Watcher can > > be configured to sample from the Telemetry data set) each exists as > > stand > > alone features with no dependency on any other. The design > > therefore splits > > them into individual, capability specific drivers. MFD is used to > > create > > platform devices for each capability so that they may be managed by > > their > > own driver. The PMT architecture is (for the most part) agnostic to > > the > > type of device it can collect from. Devices nodes are consequently > > generic > > in naming, e.g. /dev/telem<n> and /dev/smplr<n>. Each capability > > driver > > creates a class to manage the list of devices supporting > > it. Software can > > determine which devices support a PMT feature by searching through > > each > > device node entry in the sysfs class folder. It can additionally > > determine > > if a particular device supports a PMT feature by checking for a PMT > > class > > folder in the device folder. > > > > This patch set provides support for the PMT framework, along with > > support > > for Telemetry on Tiger Lake. > > > > I assume this goes thru MFD tree. Yes, looking for pull by MFD. Thanks Andy.
next prev parent reply index Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <firstname.lastname@example.org> 2020-05-05 1:32 ` [PATCH 1/3] pci: Add Designated Vendor Specific Capability David E. Box 2020-05-05 8:49 ` Andy Shevchenko 2020-05-05 15:00 ` David E. Box 2020-05-05 16:34 ` Bjorn Helgaas 2020-05-05 2:31 ` [PATCH 2/3] mfd: Intel Platform Monitoring Technology support David E. Box 2020-05-05 2:31 ` [PATCH 3/3] platform/x86: Intel PMT Telemetry capability driver David E. Box 2020-05-05 13:49 ` Andy Shevchenko 2020-05-05 21:09 ` David E. Box 2020-05-08 2:33 ` David E. Box 2020-05-05 2:53 ` [PATCH 2/3] mfd: Intel Platform Monitoring Technology support Randy Dunlap 2020-05-05 14:55 ` David E. Box 2020-05-05 9:02 ` Andy Shevchenko 2020-05-05 15:15 ` David E. Box 2020-05-08 2:18 ` [PATCH v2 0/3] Intel Platform Monitoring Technology David E. Box 2020-05-08 9:59 ` Andy Shevchenko 2020-07-14 6:23 ` [PATCH V3 " David E. Box 2020-07-17 19:06 ` [PATCH V4 " David E. Box 2020-07-27 10:23 ` Andy Shevchenko 2020-07-27 16:29 ` David E. Box [this message] 2020-07-29 21:37 ` [PATCH V5 " David E. Box 2020-08-10 14:15 ` David E. Box 2020-08-10 14:42 ` Umesh A 2020-08-11 8:04 ` Lee Jones 2020-08-11 14:50 ` David E. Box 2020-07-29 21:37 ` [PATCH V5 1/3] PCI: Add defines for Designated Vendor-Specific Extended Capability David E. Box 2020-07-29 21:37 ` [PATCH V5 2/3] mfd: Intel Platform Monitoring Technology support David E. Box 2020-07-29 21:37 ` [PATCH V5 3/3] platform/x86: Intel PMT Telemetry capability driver David E. Box 2020-07-17 19:06 ` [PATCH V4 1/3] PCI: Add defines for Designated Vendor-Specific Extended Capability David E. Box 2020-07-17 20:11 ` Andy Shevchenko 2020-07-17 19:06 ` [PATCH V4 2/3] mfd: Intel Platform Monitoring Technology support David E. Box 2020-07-28 7:58 ` Lee Jones 2020-07-28 20:35 ` David E. Box 2020-07-29 22:59 ` Mark D Rustad 2020-07-30 17:53 ` David E. Box 2020-07-31 6:19 ` Lee Jones 2020-07-17 19:06 ` [PATCH V4 3/3] platform/x86: Intel PMT Telemetry capability driver David E. Box 2020-07-14 6:23 ` [PATCH V3 1/3] PCI: Add defines for Designated Vendor-Specific Capability David E. Box 2020-07-14 8:40 ` Andy Shevchenko 2020-07-16 2:55 ` Randy Dunlap 2020-07-16 15:07 ` Bjorn Helgaas 2020-07-16 15:07 ` Randy Dunlap 2020-07-16 17:18 ` Alexander Duyck 2020-07-16 18:31 ` David E. Box 2020-07-14 6:23 ` [PATCH V3 2/3] mfd: Intel Platform Monitoring Technology support David E. Box 2020-07-14 6:23 ` [PATCH V3 3/3] platform/x86: Intel PMT Telemetry capability driver David E. Box 2020-07-14 8:51 ` Andy Shevchenko 2020-07-15 7:39 ` Alexey Budankov 2020-07-15 23:59 ` David E. Box 2020-07-16 5:57 ` Alexey Budankov 2020-07-16 2:57 ` Randy Dunlap 2020-05-08 2:18 ` [PATCH v2 1/3] PCI: Add defines for Designated Vendor-Specific Capability David E. Box 2020-05-08 2:18 ` [PATCH v2 2/3] mfd: Intel Platform Monitoring Technology support David E. Box 2020-05-08 9:15 ` Andy Shevchenko 2020-05-08 2:18 ` [PATCH v2 3/3] platform/x86: Intel PMT Telemetry capability driver David E. Box 2020-05-08 9:57 ` Andy Shevchenko 2020-05-09 16:27 ` David E. Box
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
Linux-PCI Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-pci/0 linux-pci/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-pci linux-pci/ https://lore.kernel.org/linux-pci \ firstname.lastname@example.org public-inbox-index linux-pci Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-pci AGPL code for this site: git clone https://public-inbox.org/public-inbox.git