x86,fs/resctrl telemetry monitoring
Subsystems (3)
Tony Luck
maintainerv8 cover x86,fs/resctrl telemetry monitoring
The prerequisite patch series to the Intel Telemetry code is now in upstream v6.17-rc1. So that's the basis for this series with no extra dependencies.
This patch series also available from the rdt-aet-v8 of:git://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux.git
Changes since v7 was posted here:
--- cover ---
Removed references to dependencies, there are none. Updated change log.
--- 1 ---
Added Reinette RB tag
--- 2 ---
No change
--- 3 ---
No change
--- 4 ---
No change
--- 5 ---
Improved problem/solution descriptions in commit comment.
--- 6 ---
Added "break" to default case in domain_add_cpu_mon()
Improved commit problem description. Dropped "function" when referring to name with "()".
--- 7 ---
Improve context statement in commit comment. Add a problem statement.
Apply suggestions to fix portion of commit comment.
--- 8 ---
In domain_remove_cpu_ctrl() s/&d->hdr.list/&hdr->list/
--- 9 ---
Avoid double WARN_ON_ONCE() in __mon_event_count() and mbm_bw_count(). Move domain_header_is_valid() in mkdir_mondata_subdir() to where it is needed before container_of().
Fix commit comment to use present tense for background information and imperative for the changes. Separate problem statement into its own paragraph.
--- 10 ---
Fix commit comment to use present tense for background information. Separate problem statement into own paragraph.
--- 11 ---
Move these renames here from patch 26:resctrl_mon_resource_init -> resctrl_mon_l3_resource_init() resctrl_mon_resource_exit() -> resctrl_mon_l3_resource_exit()
--- 12 ---
Clean up commit comment with problem statement in its own paragraph, and with better description.
Keep original kerneldoc for rmid_read::evt
--- 13 ---
Changed comment for cpu_on_correct_domain() as suggested. Move WARN_ON_ONCE() check for L3 resource from __mon_event_count to cpu_on_correct_domain().
Fix commit comments as suggested.
--- 14 ---
Break long line in declaration of resctrl_enable_mon_event() Reformat comments in print_event_value() use more horizontal space. s/binary_bit/binary_bits/. s/chosemn/chosen/
Commit comment cleanups to use present tense for background and imperative for solution.
--- 15 ---
Enumeration of telemetry features is performed by sub-drivers of the OOBMSM driver. These are loaded during device_init() time, but the probe functions are triggered by deferred_probe_work_func() which can happen after resctrl_init().
Tracing this procedure shows that it completes several seconds before the earliest possible mount of the resctrl file system.
Updated Kconfig dependencies to require INTEL_TPMI=y so that all drivers needed for enumeration are built in.
Fix commit to use imperative tone.
--- 16 ---
Drop "core" from Subject line.
s/these events/telemetry events/
Merge two solution paragraphs into one.
--- 17 --- s/CONFIG_X86_RESCTRL_CPU_INTEL_AET/CONFIG_X86_CPU_RESCTRL_INTEL_AET/ Make it depend on INTEL_PMT_TELEMETRY instead of INTEL_PMT_DISCOVERY. Defer addition of active_event_groups list until patch 19. Drop NUM_KNOWN_* macros and open code ARRAY_SIZE() at point of use. s/Try to use any with a known matching guid/
Try to use every telemetry aggregator with a known guid/ Change type of "ret" in get_pmt_feature() from bool to int. Rewrote commit changelog to provide more details on how telemetry aggregators are connected to MMIO regions and to event groups.
--- 18 ---
Move the "Sanity check" description in the commit message to before the "Scan the array" and rewrite to describe which regions are usable by Linux. s/package_id/package id/
Pull extra blank line in discover_events() into this patch from patch 19.
--- 19 ---
s/addresses of the telemetry regions used by each aggregator/ addresses of the telemetry regions/
Drop unneeded call to free_pkg_mmio_info((*peg)->pkginfo); s/for each aggregator/for each region/
s/struct mmio_info/struct pkg_mmio_info/
Change ascii art to note that we can support "M" aggregators in one package and "N" in another (which the code can support, but likely will not happen in practice).
Implement active_event_groups list (previously scattered between patches 16-20)
--- 20 ---
Moved stray list_add(&e->list, &active_event_groups); into patch 19 where it belongs.
Fixed kerneldoc comment for pmt_event::bin_bits to say this is number of bits in the fraction part of fixed-point.
Add closing quote around "energy" in commit comment.
--- 21 ---
s/passed/passes/ s/rmid/RMID/
Point out the explicit problem being solved with example of telemetry counters needing the offset in MMIO space.
--- 22 ---
Drop local "eventid" in discover_events(). Use e->evts[i].id directly. Change intel_aet_read_event() to return success if ANY aggregator has valid data instead on only when ALL are valid. This matches existing resctrl behaviour for providing a summed value for a CTRL_MON group together with all child MON groups.
Restructure commit message to include details of how events are enabled with an arch_priv pointer to the pmt_event.
--- 23 ---
Move setup_intel_aet_mon_domain() from arch/x86/kernel/cpu/resctrl/core.c to arch/x86/kernel/cpu/resctrl/intel_aet.c. Rename to intel_aet_setup_mon_domain() to match pattern of other functions. Add a stub to arch/x86/kernel/cpu/resctrl/internal.h for when CONFIG_X86_CPU_RESCTRL_INTEL_AET is not set. s/Intel-PMT-scoped/package scoped/
--- 24 ---
"that support is present" -> "that hardware support is present" s/option/feature/
--- 25 ---
In check_rmid_count() change test to "if (tr->num_rmids < e->num_rmids)" (i.e. if the number of hardware counters in the aggregator is fewer than the number of counter locations in the MMIO region). Eliminate the rdt_num_system_rmids variable.
"features" -> "feature's" (in comment for rdt_set_feature_disabled()) "h/w" -> "hardware" (three places in commit comment).
--- 26 ---
Function renames pulled into patch 11.
Drop the helper functions, just move the code to alloc/free closid_num_dirty_rmid[] inline intoresctrl_mon_l3_resource_init() and resctrl_mon_l3_resource_exit().
Fix leak of closid_num_dirty_rmid[] in resctrl_mon_l3_resource_init() when dom_data_init() fails.
Note in commit comment that this change is prep for moving the allocation rmid_ptrs[] to mount time.
--- 27 ---
Split into two parts:
0027:
Update resctrl_arch_system_num_rmid_idx() to compute minimum RMID across resources.
0028:
Better function names.
Rename: dom_data_init() -> setup_rmid_lru_list()
Rename: dom_data_exit() -> free_rmid_lru_list()
Move calls out of resctrl_mon_l3_resource_{init,exit}() and into
rdt_get_tree(), resctrl_exit()
Fix comment in setup_rmid_lru_list() about setup of rdtgroup_default.--- 28 ---
Add check that RDT_RESOURCE_PERF_PKG resource is mon_capable. Also set global rdt_mon_capable (to cover the case where there are no enabled L3 monitor events).
--- 29 ---
Move declaration of debugfs_resctrl_info next to debugfs_resctrl. s/debugs/debugfs/
Separate problem from context in commit comment.
--- 30 ---
Unchanged
--- 31 ---
Unchanged
Background
----------
On Intel systems that support per-RMID telemetry monitoring each logical processor keeps a local count for various events. When the IA32_PQR_ASSOC.RMID value for the logical processor changes (or when a two millisecond counter expires) these event counts are transmitted to an event aggregator on the same package as the processor together with the current RMID value. The event counters are reset to zero to begin counting again.
Each aggregator takes the incoming event counts and adds them to cumulative counts for each event for each RMID. Note that there can be multiple aggregators on each package with no architectural association between logical processors and an aggregator.
All of these aggregated counters can be read by an operating system from the MMIO space of the Out Of Band Management Service Module (OOBMSM) device(s) on a system. Any counter can be read from any logical processor.
Intel publishes details for each processor generation showing which events are counted by each logical processor and the offsets for each accumulated counter value within the MMIO space in XML files here:
https://github.com/intel/Intel-PMT.
For example there are two energy related telemetry events for the Clearwater Forest family of processors and the MMIO space looks like this:
Offset RMID Event ------ ---- ----- 0x0000 0 core_energy 0x0008 0 activity 0x0010 1 core_energy 0x0018 1 activity ... 0x23F0 575 core_energy 0x23F8 575 activity
In addition the XML file provides the units (Joules for core_energy, Farads for activity) and the type of data (fixed-point binary with bit 63 used to indicate the data is valid, and the low 18 bits as a binary fraction).
Finally, each XML file provides a 32-bit unique id (or guid) that is used as an index to find the correct XML description file for each telemetry implementation.
The INTEL_PMT_DISCOVERY driver provides intel_pmt_get_regions_by_feature() to enumerate the aggregator instances (also referred to as "telemetry regions" in this series) on a platform. It provides:
1) guid - so resctrl can determine which events are supported
2) MMIO base address of counters
3) package id
Resctrl accumulates counts from all aggregators on a package in order to provide a consistent user interface across processor generations.
Directory structure for the telemetry events looks like this:
$ tree /sys/fs/resctrl/mon_data/
/sys/fs/resctrl/mon_data/
mon_data
├── mon_PERF_PKG_00
│ ├── activity
│ └── core_energy
└── mon_PERF_PKG_01
├── activity
└── core_energyReading the "core_energy" file from some resctrl mon_data directory shows the cumulative energy (in Joules) used by all tasks that ran with the RMID associated with that directory on a given package. Note that "core_energy" reports only energy consumed by CPU cores (data processing units, L1/L2 caches, etc.). It does not include energy used in the "uncore" (L3 cache, on package devices, etc.), or used by memory or I/O devices.
Tony Luck (32):
x86,fs/resctrl: Consolidate monitor event descriptions x86,fs/resctrl: Replace architecture event enabled checks x86/resctrl: Remove 'rdt_mon_features' global variable x86,fs/resctrl: Prepare for more monitor events x86,fs/resctrl: Improve domain type checking
x86/resctrl: Move L3 initialization into new helper function x86,fs/resctrl: Refactor domain_remove_cpu_mon() ready for new domain
types
x86/resctrl: Clean up domain_remove_cpu_ctrl() x86,fs/resctrl: Use struct rdt_domain_hdr instead of struct
rdt_mon_domain
x86,fs/resctrl: Rename struct rdt_mon_domain and rdt_hw_mon_domain x86,fs/resctrl: Rename some L3 specific functions fs/resctrl: Make event details accessible to functions when reading
events
x86,fs/resctrl: Handle events that can be read from any CPU x86,fs/resctrl: Support binary fixed point event counters x86,fs/resctrl: Add an architectural hook called for each mount x86,fs/resctrl: Add and initialize rdt_resource for package scope
monitor
x86/resctrl: Discover hardware telemetry events x86/resctrl: Count valid telemetry aggregators per package x86/resctrl: Complete telemetry event enumeration x86,fs/resctrl: Fill in details of events for guid 0x26696143 and
0x26557651
x86,fs/resctrl: Add architectural event pointer x86/resctrl: Read telemetry events
x86/resctrl: Handle domain creation/deletion for RDT_RESOURCE_PERF_PKG x86/resctrl: Add energy/perf choices to rdt boot option x86/resctrl: Handle number of RMIDs supported by telemetry resources fs/resctrl: Move allocation/free of closid_num_dirty_rmid fs,x86/resctrl: Compute number of RMIDs as minimum across resources fs/resctrl: Move RMID initialization to first mount x86/resctrl: Enable RDT_RESOURCE_PERF_PKG
fs/resctrl: Provide interface to create architecture specific debugfs
area
x86/resctrl: Add debugfs files to show telemetry aggregator status x86,fs/resctrl: Update Documentation for package events
.../admin-guide/kernel-parameters.txt | 2 +- Documentation/filesystems/resctrl.rst | 85 +++- include/linux/resctrl.h | 89 +++- include/linux/resctrl_types.h | 26 +- arch/x86/include/asm/resctrl.h | 16 - arch/x86/kernel/cpu/resctrl/internal.h | 56 ++- fs/resctrl/internal.h | 68 ++- arch/x86/kernel/cpu/resctrl/core.c | 310 ++++++++---- arch/x86/kernel/cpu/resctrl/intel_aet.c | 448 ++++++++++++++++++ arch/x86/kernel/cpu/resctrl/monitor.c | 76 +-- fs/resctrl/ctrlmondata.c | 123 ++++- fs/resctrl/monitor.c | 310 ++++++------ fs/resctrl/rdtgroup.c | 272 +++++++---- arch/x86/Kconfig | 13 + arch/x86/kernel/cpu/resctrl/Makefile | 1 + 15 files changed, 1442 insertions(+), 453 deletions(-) create mode 100644 arch/x86/kernel/cpu/resctrl/intel_aet.c
base-commit: 8f5ae30d69d7543eee0d70083daf4de8fe15d585
Signature · 1 line
2.50.1
Tony Luck
maintainerPATCH v8 1/32 x86,fs/resctrl: Consolidate monitor event descriptions
There are currently only three monitor events, all associated with the RDT_RESOURCE_L3 resource. Growing support for additional events will be easier with some restructuring to have a single point in file system code where all attributes of all events are defined.
Place all event descriptions into an array mon_event_all[]. Doing this has the beneficial side effect of removing the need for rdt_resource::evt_list.
Add resctrl_event_id::QOS_FIRST_EVENT for a lower bound on range checks for event ids and as the starting index to scan mon_event_all[].
Drop the code that builds evt_list and change the two places where the list is scanned to scan mon_event_all[] instead using a new helper macro for_each_mon_event().
Architecture code now informs file system code which events are available with resctrl_enable_mon_event().
--- include/linux/resctrl.h | 4 +- include/linux/resctrl_types.h | 12 ++++-- fs/resctrl/internal.h | 13 ++++-- arch/x86/kernel/cpu/resctrl/core.c | 12 ++++-- fs/resctrl/monitor.c | 63 +++++++++++++++--------------- fs/resctrl/rdtgroup.c | 11 +++--- 6 files changed, 66 insertions(+), 49 deletions(-)
include/linux/resctrl.h +2 -2
@@ -269,7 +269,6 @@ enum resctrl_schema_fmt {* @mon_domains: RCU list of all monitor domains for this resource * @name: Name to use in "schemata" file. * @schema_fmt: Which format string and parser is used for this schema. -* @evt_list: List of monitoring events * @mbm_cfg_mask: Bandwidth sources that can be tracked when bandwidth * monitoring events can be configured. * @cdp_capable: Is the CDP feature available on this resource
@@ -287,7 +286,6 @@ struct rdt_resource {struct list_head mon_domains;char *name;enum resctrl_schema_fmt schema_fmt; -struct list_head evt_list;unsigned int mbm_cfg_mask;bool cdp_capable; };
@@ -372,6 +370,8 @@ u32 resctrl_arch_get_num_closid(struct rdt_resource *r);u32 resctrl_arch_system_num_rmid_idx (void );int resctrl_arch_update_domains (struct rdt_resource *r,u32 closid); +void resctrl_enable_mon_event (enum resctrl_event_id eventid); +bool resctrl_arch_is_evt_configurable (enum resctrl_event_id evt);/**
include/linux/resctrl_types.h +8 -4
@@ -34,11 +34,15 @@/* Max event bits supported */ #define MAX_EVT_CONFIG_BITS GENMASK(6, 0) -/* -* Event IDs, the values match those used to program IA32_QM_EVTSEL before -* reading IA32_QM_CTR on RDT systems. -*/ +/* Event IDs */ enum resctrl_event_id { +/* Must match value of first event below */ +QOS_FIRST_EVENT =0x01 , + +/* +* These values match those used to program IA32_QM_EVTSEL before +* reading IA32_QM_CTR on RDT systems. +*/ QOS_L3_OCCUP_EVENT_ID =0x01 ,QOS_L3_MBM_TOTAL_EVENT_ID =0x02 ,QOS_L3_MBM_LOCAL_EVENT_ID =0x03 ,
fs/resctrl/internal.h +10 -3
@@ -52,19 +52,26 @@ static inline struct rdt_fs_context *rdt_fc2context(struct fs_context *fc) }/** -* struct mon_evt - Entry in the event list of a resource +* struct mon_evt - Properties of a monitor event * @evtid: event id +* @rid: resource id for this event * @name: name of the event * @configurable: true if the event is configurable -* @list: entry in &rdt_resource->evt_list +* @enabled: true if the event is enabled */ struct mon_evt {enum resctrl_event_id evtid; +enum resctrl_res_level rid;char *name;bool configurable; -struct list_head list; +bool enabled; }; +extern struct mon_evt mon_event_all[QOS_NUM_EVENTS ]; + +#define for_each_mon_event (mevt) for (mevt = &mon_event_all[QOS_FIRST_EVENT]; \ + mevt < &mon_event_all[QOS_NUM_EVENTS]; mevt++) +/** * struct mon_data - Monitoring details for each event file. * @list: Member of the global @mon_data_kn_priv_list list.
arch/x86/kernel/cpu/resctrl/core.c +9 -3
@@ -864,12 +864,18 @@ static __init bool get_rdt_mon_resources(void) {struct rdt_resource *r = &rdt_resources_all[RDT_RESOURCE_L3 ].r_resctrl; -if (rdt_cpu_has (X86_FEATURE_CQM_OCCUP_LLC )) +if (rdt_cpu_has (X86_FEATURE_CQM_OCCUP_LLC )) { +resctrl_enable_mon_event (QOS_L3_OCCUP_EVENT_ID ); rdt_mon_features |= (1 <<QOS_L3_OCCUP_EVENT_ID ); -if (rdt_cpu_has (X86_FEATURE_CQM_MBM_TOTAL )) + } +if (rdt_cpu_has (X86_FEATURE_CQM_MBM_TOTAL )) { +resctrl_enable_mon_event (QOS_L3_MBM_TOTAL_EVENT_ID ); rdt_mon_features |= (1 <<QOS_L3_MBM_TOTAL_EVENT_ID ); -if (rdt_cpu_has (X86_FEATURE_CQM_MBM_LOCAL )) + } +if (rdt_cpu_has (X86_FEATURE_CQM_MBM_LOCAL )) { +resctrl_enable_mon_event (QOS_L3_MBM_LOCAL_EVENT_ID ); rdt_mon_features |= (1 <<QOS_L3_MBM_LOCAL_EVENT_ID ); + }if (!rdt_mon_features)return false;
fs/resctrl/monitor.c +31 -32
84 lines not on this page · raw message
fs/resctrl/rdtgroup.c +6 -5
@@ -1152,7 +1152,9 @@ static int rdt_mon_features_show(struct kernfs_open_file *of,struct rdt_resource *r =rdt_kn_parent_priv (of->kn);struct mon_evt *mevt; -list_for_each_entry (mevt, &r->evt_list, list) { +for_each_mon_event (mevt) { +if (mevt->rid != r->rid || !mevt->enabled) +continue ;seq_printf (seq,"%s\n" , mevt->name);if (mevt->configurable)seq_printf (seq,"%s_config\n" , mevt->name);
@@ -3057,10 +3059,9 @@ static int mon_add_all_files(struct kernfs_node *kn, struct rdt_mon_domain *d,struct mon_evt *mevt;int ret, domid; -if (WARN_ON (list_empty (&r->evt_list))) -return -EPERM ; - -list_for_each_entry (mevt, &r->evt_list, list) { +for_each_mon_event (mevt) { +if (mevt->rid != r->rid || !mevt->enabled) +continue ; domid = do_sum ? d->ci_id : d->hdr.id; priv =mon_get_kn_priv (r->rid, domid, mevt, do_sum);if (WARN_ON_ONCE (!priv))
Signature · 1 line
2.50.1
Tony Luck
maintainerPATCH v8 2/32 x86,fs/resctrl: Replace architecture event enabled checks
In reply to Tony LuckThe resctrl file system now has complete knowledge of the status of every event. So there is no need for per-event function calls to check.
Replace each of the resctrl_arch_is_{event}enabled() calls with resctrl_is_mon_event_enabled(QOS_{EVENT}).
No functional change.
--- include/linux/resctrl.h | 2 ++ arch/x86/include/asm/resctrl.h | 15 --------------- arch/x86/kernel/cpu/resctrl/core.c | 4 ++-- arch/x86/kernel/cpu/resctrl/monitor.c | 4 ++-- fs/resctrl/ctrlmondata.c | 4 ++-- fs/resctrl/monitor.c | 16 +++++++++++----- fs/resctrl/rdtgroup.c | 18 +++++++++--------- 7 files changed, 28 insertions(+), 35 deletions(-)
include/linux/resctrl.h +2 -0
@@ -372,6 +372,8 @@ int resctrl_arch_update_domains(struct rdt_resource *r, u32 closid);void resctrl_enable_mon_event (enum resctrl_event_id eventid); +bool resctrl_is_mon_event_enabled (enum resctrl_event_id eventid); +bool resctrl_arch_is_evt_configurable (enum resctrl_event_id evt);/**
arch/x86/include/asm/resctrl.h +0 -15
@@ -84,21 +84,6 @@ static inline void resctrl_arch_disable_mon(void)static_branch_dec_cpuslocked (&rdt_enable_key); } -static inline bool resctrl_arch_is_llc_occupancy_enabled (void ) -{ -return (rdt_mon_features & (1 <<QOS_L3_OCCUP_EVENT_ID )); -} - -static inline bool resctrl_arch_is_mbm_total_enabled (void ) -{ -return (rdt_mon_features & (1 <<QOS_L3_MBM_TOTAL_EVENT_ID )); -} - -static inline bool resctrl_arch_is_mbm_local_enabled (void ) -{ -return (rdt_mon_features & (1 <<QOS_L3_MBM_LOCAL_EVENT_ID )); -} -/* * __resctrl_sched_in() - Writes the task's CLOSid/RMID to IA32_PQR_MSR *
arch/x86/kernel/cpu/resctrl/core.c +2 -2
@@ -402,13 +402,13 @@ static int arch_domain_mbm_alloc(u32 num_rmid, struct rdt_hw_mon_domain *hw_dom) {size_t tsize; -if (resctrl_arch_is_mbm_total_enabled ()) { +if (resctrl_is_mon_event_enabled (QOS_L3_MBM_TOTAL_EVENT_ID )) { tsize =sizeof (*hw_dom->arch_mbm_total); hw_dom->arch_mbm_total =kcalloc (num_rmid, tsize,GFP_KERNEL );if (!hw_dom->arch_mbm_total)return -ENOMEM ; } -if (resctrl_arch_is_mbm_local_enabled ()) { +if (resctrl_is_mon_event_enabled (QOS_L3_MBM_LOCAL_EVENT_ID )) { tsize =sizeof (*hw_dom->arch_mbm_local); hw_dom->arch_mbm_local =kcalloc (num_rmid, tsize,GFP_KERNEL );if (!hw_dom->arch_mbm_local) {
arch/x86/kernel/cpu/resctrl/monitor.c +2 -2
@@ -207,11 +207,11 @@ void resctrl_arch_reset_rmid_all(struct rdt_resource *r, struct rdt_mon_domain * {struct rdt_hw_mon_domain *hw_dom =resctrl_to_arch_mon_dom (d); -if (resctrl_arch_is_mbm_total_enabled ()) +if (resctrl_is_mon_event_enabled (QOS_L3_MBM_TOTAL_EVENT_ID ))memset (hw_dom->arch_mbm_total,0 ,sizeof (*hw_dom->arch_mbm_total) * r->num_rmid); -if (resctrl_arch_is_mbm_local_enabled ()) +if (resctrl_is_mon_event_enabled (QOS_L3_MBM_LOCAL_EVENT_ID ))memset (hw_dom->arch_mbm_local,0 ,sizeof (*hw_dom->arch_mbm_local) * r->num_rmid); }
fs/resctrl/ctrlmondata.c +2 -2
@@ -473,12 +473,12 @@ ssize_t rdtgroup_mba_mbps_event_write(struct kernfs_open_file *of,rdt_last_cmd_clear ();if (!strcmp (buf,"mbm_local_bytes" )) { -if (resctrl_arch_is_mbm_local_enabled ()) +if (resctrl_is_mon_event_enabled (QOS_L3_MBM_LOCAL_EVENT_ID )) rdtgrp->mba_mbps_event =QOS_L3_MBM_LOCAL_EVENT_ID ;else ret = -EINVAL ; }else if (!strcmp (buf,"mbm_total_bytes" )) { -if (resctrl_arch_is_mbm_total_enabled ()) +if (resctrl_is_mon_event_enabled (QOS_L3_MBM_TOTAL_EVENT_ID )) rdtgrp->mba_mbps_event =QOS_L3_MBM_TOTAL_EVENT_ID ;else ret = -EINVAL ;
fs/resctrl/monitor.c +11 -5
@@ -336,7 +336,7 @@ void free_rmid(u32 closid, u32 rmid) entry =__rmid_entry (idx); -if (resctrl_arch_is_llc_occupancy_enabled ()) +if (resctrl_is_mon_event_enabled (QOS_L3_OCCUP_EVENT_ID ))add_rmid_to_limbo (entry);else list_add_tail (&entry->list, &rmid_free_lru);
@@ -637,10 +637,10 @@ static void mbm_update(struct rdt_resource *r, struct rdt_mon_domain *d,* This is protected from concurrent reads from user as both * the user and overflow handler hold the global mutex. */ -if (resctrl_arch_is_mbm_total_enabled ()) +if (resctrl_is_mon_event_enabled (QOS_L3_MBM_TOTAL_EVENT_ID ))mbm_update_one_event (r, d, closid, rmid,QOS_L3_MBM_TOTAL_EVENT_ID ); -if (resctrl_arch_is_mbm_local_enabled ()) +if (resctrl_is_mon_event_enabled (QOS_L3_MBM_LOCAL_EVENT_ID ))mbm_update_one_event (r, d, closid, rmid,QOS_L3_MBM_LOCAL_EVENT_ID ); }
@@ -879,6 +879,12 @@ void resctrl_enable_mon_event(enum resctrl_event_id eventid) mon_event_all[eventid].enabled = true; } +bool resctrl_is_mon_event_enabled (enum resctrl_event_id eventid) +{ +return eventid >=QOS_FIRST_EVENT && eventid <QOS_NUM_EVENTS && + mon_event_all[eventid].enabled; +} +/** * resctrl_mon_resource_init() - Initialise global monitoring structures. *
@@ -914,9 +920,9 @@ int resctrl_mon_resource_init(void) RFTYPE_MON_INFO | RFTYPE_RES_CACHE); } -if (resctrl_arch_is_mbm_local_enabled ()) +if (resctrl_is_mon_event_enabled (QOS_L3_MBM_LOCAL_EVENT_ID )) mba_mbps_default_event =QOS_L3_MBM_LOCAL_EVENT_ID ; -else if (resctrl_arch_is_mbm_total_enabled ()) +else if (resctrl_is_mon_event_enabled (QOS_L3_MBM_TOTAL_EVENT_ID )) mba_mbps_default_event =QOS_L3_MBM_TOTAL_EVENT_ID ;return 0 ;
fs/resctrl/rdtgroup.c +9 -9
@@ -123,8 +123,8 @@ void rdt_staged_configs_clear(void)static bool resctrl_is_mbm_enabled (void ) { -return (resctrl_arch_is_mbm_total_enabled () || -resctrl_arch_is_mbm_local_enabled ()); +return (resctrl_is_mon_event_enabled (QOS_L3_MBM_TOTAL_EVENT_ID ) || +resctrl_is_mon_event_enabled (QOS_L3_MBM_LOCAL_EVENT_ID )); }static bool resctrl_is_mbm_event (int e)
@@ -196,7 +196,7 @@ static int closid_alloc(void)lockdep_assert_held (&rdtgroup_mutex);if (IS_ENABLED (CONFIG_RESCTRL_RMID_DEPENDS_ON_CLOSID ) && -resctrl_arch_is_llc_occupancy_enabled ()) { +resctrl_is_mon_event_enabled (QOS_L3_OCCUP_EVENT_ID )) { cleanest_closid =resctrl_find_cleanest_closid ();if (cleanest_closid <0 )return cleanest_closid;
@@ -4051,7 +4051,7 @@ void resctrl_offline_mon_domain(struct rdt_resource *r, struct rdt_mon_domain *dif (resctrl_is_mbm_enabled ())cancel_delayed_work (&d->mbm_over); -if (resctrl_arch_is_llc_occupancy_enabled () &&has_busy_rmid (d)) { +if (resctrl_is_mon_event_enabled (QOS_L3_OCCUP_EVENT_ID ) &&has_busy_rmid (d)) {/* * When a package is going down, forcefully * decrement rmid->ebusy. There is no way to know
@@ -4087,12 +4087,12 @@ static int domain_setup_mon_state(struct rdt_resource *r, struct rdt_mon_domainu32 idx_limit =resctrl_arch_system_num_rmid_idx ();size_t tsize; -if (resctrl_arch_is_llc_occupancy_enabled ()) { +if (resctrl_is_mon_event_enabled (QOS_L3_OCCUP_EVENT_ID )) { d->rmid_busy_llc =bitmap_zalloc (idx_limit,GFP_KERNEL );if (!d->rmid_busy_llc)return -ENOMEM ; } -if (resctrl_arch_is_mbm_total_enabled ()) { +if (resctrl_is_mon_event_enabled (QOS_L3_MBM_TOTAL_EVENT_ID )) { tsize =sizeof (*d->mbm_total); d->mbm_total =kcalloc (idx_limit, tsize,GFP_KERNEL );if (!d->mbm_total) {
@@ -4100,7 +4100,7 @@ static int domain_setup_mon_state(struct rdt_resource *r, struct rdt_mon_domainreturn -ENOMEM ; } } -if (resctrl_arch_is_mbm_local_enabled ()) { +if (resctrl_is_mon_event_enabled (QOS_L3_MBM_LOCAL_EVENT_ID )) { tsize =sizeof (*d->mbm_local); d->mbm_local =kcalloc (idx_limit, tsize,GFP_KERNEL );if (!d->mbm_local) {
@@ -4145,7 +4145,7 @@ int resctrl_online_mon_domain(struct rdt_resource *r, struct rdt_mon_domain *d) RESCTRL_PICK_ANY_CPU); } -if (resctrl_arch_is_llc_occupancy_enabled ()) +if (resctrl_is_mon_event_enabled (QOS_L3_OCCUP_EVENT_ID ))INIT_DELAYED_WORK (&d->cqm_limbo, cqm_handle_limbo);/*
@@ -4220,7 +4220,7 @@ void resctrl_offline_cpu(unsigned int cpu)cancel_delayed_work (&d->mbm_over);mbm_setup_overflow_handler (d,0 , cpu); } -if (resctrl_arch_is_llc_occupancy_enabled () && +if (resctrl_is_mon_event_enabled (QOS_L3_OCCUP_EVENT_ID ) && cpu == d->cqm_work_cpu &&has_busy_rmid (d)) {cancel_delayed_work (&d->cqm_limbo);cqm_setup_limbo_handler (d,0 , cpu);
Signature · 1 line
2.50.1
Tony Luck
maintainerPATCH v8 3/32 x86/resctrl: Remove 'rdt_mon_features' global variable
In reply to Tony Luckrdt_mon_features is used as a bitmask of enabled monitor events. A monitor event's status is now maintained in mon_evt::enabled with all monitor events' mon_evt structures found in the filesystem's mon_event_all[] array.
Remove the remaining uses of rdt_mon_features.
--- arch/x86/include/asm/resctrl.h | 1 - arch/x86/kernel/cpu/resctrl/core.c | 9 +++++---- arch/x86/kernel/cpu/resctrl/monitor.c | 5 ----- 3 files changed, 5 insertions(+), 10 deletions(-)
arch/x86/include/asm/resctrl.h +0 -1
@@ -44,7 +44,6 @@ DECLARE_PER_CPU(struct resctrl_pqr_state, pqr_state);extern bool rdt_alloc_capable;extern bool rdt_mon_capable; -extern unsigned int rdt_mon_features;DECLARE_STATIC_KEY_FALSE (rdt_enable_key);DECLARE_STATIC_KEY_FALSE (rdt_alloc_enable_key);
arch/x86/kernel/cpu/resctrl/core.c +5 -4
@@ -863,21 +863,22 @@ static __init bool get_rdt_alloc_resources(void)static __init bool get_rdt_mon_resources (void ) {struct rdt_resource *r = &rdt_resources_all[RDT_RESOURCE_L3 ].r_resctrl; +bool ret = false;if (rdt_cpu_has (X86_FEATURE_CQM_OCCUP_LLC )) {resctrl_enable_mon_event (QOS_L3_OCCUP_EVENT_ID ); - rdt_mon_features |= (1 <<QOS_L3_OCCUP_EVENT_ID ); + ret = true; }if (rdt_cpu_has (X86_FEATURE_CQM_MBM_TOTAL )) {resctrl_enable_mon_event (QOS_L3_MBM_TOTAL_EVENT_ID ); - rdt_mon_features |= (1 <<QOS_L3_MBM_TOTAL_EVENT_ID ); + ret = true; }if (rdt_cpu_has (X86_FEATURE_CQM_MBM_LOCAL )) {resctrl_enable_mon_event (QOS_L3_MBM_LOCAL_EVENT_ID ); - rdt_mon_features |= (1 <<QOS_L3_MBM_LOCAL_EVENT_ID ); + ret = true; } -if (!rdt_mon_features) +if (!ret)return false;return !rdt_get_mon_l3_config (r);
arch/x86/kernel/cpu/resctrl/monitor.c +0 -5
@@ -31,11 +31,6 @@*/ bool rdt_mon_capable; -/* -* Global to indicate which monitoring events are enabled. -*/ -unsigned int rdt_mon_features; -#define CF (cf) ((unsigned long)(1048576 * (cf) + 0.5))static int snc_nodes_per_l3_cache =1 ;
Signature · 1 line
2.50.1
Tony Luck
maintainerPATCH v8 4/32 x86,fs/resctrl: Prepare for more monitor events
In reply to Tony LuckThere's a rule in computer programming that objects appear zero, once, or many times. So code accordingly.
There are two MBM events and resctrl is coded with a lot of
if (local)
do one thing
if (total)
do a different thing
Change the rdt_mon_domain and rdt_hw_mon_domain structures to hold arrays of pointers to per event data instead of explicit fields for total and local bandwidth.
Simplify by coding for many events using loops on which are enabled.
Move resctrl_is_mbm_event() to <linux/resctrl.h> so it can be used more widely. Also provide a for_each_mbm_event_id() helper macro.
Cleanup variable names in functions touched to consistently use "eventid" for those with type enum resctrl_event_id.
--- include/linux/resctrl.h | 23 +++++++++--- include/linux/resctrl_types.h | 3 ++ arch/x86/kernel/cpu/resctrl/internal.h | 8 ++--- arch/x86/kernel/cpu/resctrl/core.c | 40 +++++++++++---------- arch/x86/kernel/cpu/resctrl/monitor.c | 36 +++++++++---------- fs/resctrl/monitor.c | 13 ++++--- fs/resctrl/rdtgroup.c | 50 +++++++++++++------------- 7 files changed, 96 insertions(+), 77 deletions(-)
include/linux/resctrl.h +19 -4
@@ -161,8 +161,9 @@ struct rdt_ctrl_domain {* @hdr: common header for different domain types * @ci_id: cache info id for this domain * @rmid_busy_llc: bitmap of which limbo RMIDs are above threshold -* @mbm_total: saved state for MBM total bandwidth -* @mbm_local: saved state for MBM local bandwidth +* @mbm_states: Per-event pointer to the MBM event's saved state. +* An MBM event's state is an array of struct mbm_state +* indexed by RMID on x86 or combined CLOSID, RMID on Arm. * @mbm_over: worker to periodically read MBM h/w counters * @cqm_limbo: worker to periodically read CQM h/w counters * @mbm_work_cpu: worker CPU for MBM h/w counters
@@ -172,8 +173,7 @@ struct rdt_mon_domain {struct rdt_domain_hdr hdr;unsigned int ci_id;unsigned long *rmid_busy_llc; -struct mbm_state *mbm_total; -struct mbm_state *mbm_local; +struct mbm_state *mbm_states[QOS_NUM_L3_MBM_EVENTS ];struct delayed_work mbm_over;struct delayed_work cqm_limbo;int mbm_work_cpu;
@@ -376,6 +376,21 @@ bool resctrl_is_mon_event_enabled(enum resctrl_event_id eventid);bool resctrl_arch_is_evt_configurable (enum resctrl_event_id evt); +static inline bool resctrl_is_mbm_event (enum resctrl_event_id eventid) +{ +return (eventid >=QOS_L3_MBM_TOTAL_EVENT_ID && + eventid <=QOS_L3_MBM_LOCAL_EVENT_ID ); +} + +/* Iterate over all memory bandwidth events */ +#define for_each_mbm_event_id (eventid) \ + for (eventid = QOS_L3_MBM_TOTAL_EVENT_ID; \ + eventid <= QOS_L3_MBM_LOCAL_EVENT_ID; eventid++) + +/* Iterate over memory bandwidth arrays in domain structures */ +#define for_each_mbm_idx (idx) \ + for (idx = 0; idx < QOS_NUM_L3_MBM_EVENTS; idx++) +/** * resctrl_arch_mon_event_config_write() - Write the config for an event. * @config_info: struct resctrl_mon_config_info describing the resource, domain
include/linux/resctrl_types.h +3 -0
@@ -51,4 +51,7 @@ enum resctrl_event_id { QOS_NUM_EVENTS, }; +#define QOS_NUM_L3_MBM_EVENTS (QOS_L3_MBM_LOCAL_EVENT_ID - QOS_L3_MBM_TOTAL_EVENT_ID + 1) +#define MBM_STATE_IDX (evt) ((evt) - QOS_L3_MBM_TOTAL_EVENT_ID) +#endif /* __LINUX_RESCTRL_TYPES_H */
arch/x86/kernel/cpu/resctrl/internal.h +4 -4
@@ -54,15 +54,15 @@ struct rdt_hw_ctrl_domain {* struct rdt_hw_mon_domain - Arch private attributes of a set of CPUs that share * a resource for a monitor function * @d_resctrl: Properties exposed to the resctrl file system -* @arch_mbm_total: arch private state for MBM total bandwidth -* @arch_mbm_local: arch private state for MBM local bandwidth +* @arch_mbm_states: Per-event pointer to the MBM event's saved state. +* An MBM event's state is an array of struct arch_mbm_state +* indexed by RMID on x86. * * Members of this structure are accessed via helpers that provide abstraction. */ struct rdt_hw_mon_domain {struct rdt_mon_domain d_resctrl; -struct arch_mbm_state *arch_mbm_total; -struct arch_mbm_state *arch_mbm_local; +struct arch_mbm_state *arch_mbm_states[QOS_NUM_L3_MBM_EVENTS ]; };static inline struct rdt_hw_ctrl_domain *resctrl_to_arch_ctrl_dom (struct rdt_ctrl_domain *r)
arch/x86/kernel/cpu/resctrl/core.c +22 -18
@@ -365,8 +365,10 @@ static void ctrl_domain_free(struct rdt_hw_ctrl_domain *hw_dom)static void mon_domain_free (struct rdt_hw_mon_domain *hw_dom) { -kfree (hw_dom->arch_mbm_total); -kfree (hw_dom->arch_mbm_local); +int idx; + +for_each_mbm_idx (idx) +kfree (hw_dom->arch_mbm_states[idx]);kfree (hw_dom); }
@@ -400,25 +402,27 @@ static int domain_setup_ctrlval(struct rdt_resource *r, struct rdt_ctrl_domain **/ static int arch_domain_mbm_alloc (u32 num_rmid,struct rdt_hw_mon_domain *hw_dom) { -size_t tsize; - -if (resctrl_is_mon_event_enabled (QOS_L3_MBM_TOTAL_EVENT_ID )) { - tsize =sizeof (*hw_dom->arch_mbm_total); - hw_dom->arch_mbm_total =kcalloc (num_rmid, tsize,GFP_KERNEL ); -if (!hw_dom->arch_mbm_total) -return -ENOMEM ; - } -if (resctrl_is_mon_event_enabled (QOS_L3_MBM_LOCAL_EVENT_ID )) { - tsize =sizeof (*hw_dom->arch_mbm_local); - hw_dom->arch_mbm_local =kcalloc (num_rmid, tsize,GFP_KERNEL ); -if (!hw_dom->arch_mbm_local) { -kfree (hw_dom->arch_mbm_total); - hw_dom->arch_mbm_total =NULL ; -return -ENOMEM ; - } +size_t tsize =sizeof (*hw_dom->arch_mbm_states[0 ]); +enum resctrl_event_id eventid; +int idx; + +for_each_mbm_event_id (eventid) { +if (!resctrl_is_mon_event_enabled (eventid)) +continue ; + idx =MBM_STATE_IDX (eventid); + hw_dom->arch_mbm_states[idx] =kcalloc (num_rmid, tsize,GFP_KERNEL ); +if (!hw_dom->arch_mbm_states[idx]) + goto cleanup; }return 0 ; +cleanup: +for_each_mbm_idx (idx) { +kfree (hw_dom->arch_mbm_states[idx]); + hw_dom->arch_mbm_states[idx] =NULL ; + } + +return -ENOMEM ; }static int get_domain_id_from_scope (int cpu,enum resctrl_scope scope)
arch/x86/kernel/cpu/resctrl/monitor.c +17 -19
@@ -161,18 +161,14 @@ static struct arch_mbm_state *get_arch_mbm_state(struct rdt_hw_mon_domain *hw_dou32 rmid, enum resctrl_event_id eventid) { - switch (eventid) { - case QOS_L3_OCCUP_EVENT_ID: - return NULL; -case QOS_L3_MBM_TOTAL_EVENT_ID : -return &hw_dom->arch_mbm_total[rmid]; -case QOS_L3_MBM_LOCAL_EVENT_ID : -return &hw_dom->arch_mbm_local[rmid]; -default : -/* Never expect to get here */ -WARN_ON_ONCE (1 ); + struct arch_mbm_state *state; + +if (!resctrl_is_mbm_event (eventid))return NULL ; - } + + state = hw_dom->arch_mbm_states[MBM_STATE_IDX (eventid)]; + +return state ? &state[rmid] :NULL ; } void resctrl_arch_reset_rmid(struct rdt_resource *r, struct rdt_mon_domain *d,
@@ -201,14 +197,16 @@ void resctrl_arch_reset_rmid(struct rdt_resource *r, struct rdt_mon_domain *d,void resctrl_arch_reset_rmid_all (struct rdt_resource *r,struct rdt_mon_domain *d) {struct rdt_hw_mon_domain *hw_dom =resctrl_to_arch_mon_dom (d); - -if (resctrl_is_mon_event_enabled (QOS_L3_MBM_TOTAL_EVENT_ID )) -memset (hw_dom->arch_mbm_total,0 , -sizeof (*hw_dom->arch_mbm_total) * r->num_rmid); - -if (resctrl_is_mon_event_enabled (QOS_L3_MBM_LOCAL_EVENT_ID )) -memset (hw_dom->arch_mbm_local,0 , -sizeof (*hw_dom->arch_mbm_local) * r->num_rmid); +enum resctrl_event_id eventid; +int idx; + +for_each_mbm_event_id (eventid) { +if (!resctrl_is_mon_event_enabled (eventid)) +continue ; + idx =MBM_STATE_IDX (eventid); +memset (hw_dom->arch_mbm_states[idx],0 , +sizeof (*hw_dom->arch_mbm_states[0 ]) * r->num_rmid); + } }static u64 mbm_overflow_count (u64 prev_msr,u64 cur_msr,unsigned int width)
fs/resctrl/monitor.c +6 -7
@@ -346,15 +346,14 @@ static struct mbm_state *get_mbm_state(struct rdt_mon_domain *d, u32 closid, u32 rmid, enum resctrl_event_id evtid) { u32 idx = resctrl_arch_rmid_idx_encode(closid, rmid); +struct mbm_state *state; -switch (evtid) { -case QOS_L3_MBM_TOTAL_EVENT_ID : -return &d->mbm_total[idx]; -case QOS_L3_MBM_LOCAL_EVENT_ID : -return &d->mbm_local[idx]; -default : +if (!resctrl_is_mbm_event (evtid))return NULL ; - } + + state = d->mbm_states[MBM_STATE_IDX (evtid)]; + +return state ? &state[idx] :NULL ; }static int __mon_event_count (u32 closid,u32 rmid,struct rmid_read *rr)
fs/resctrl/rdtgroup.c +25 -25
78 lines not on this page · raw message
Signature · 1 line
2.50.1
Tony Luck
maintainerPATCH v8 5/32 x86,fs/resctrl: Improve domain type checking
In reply to Tony LuckThe rdt_domain_hdr structure is used in both control and monitor domain structures to provide common methods for operations such as adding a CPU to a domain, removing a CPU from a domain, accessing the mask of all CPUs in a domain.
The "type" field provides a simple check whether a domain is a control or monitor domain so that programming errors operating on domains will be quickly caught. This is insufficient to catch errors when other resources besides L3 support monitor events.
Add a new rdt_domain_hdr::rid field that is initialized when domain structures are allocated. Call domain_header_is_valid() to sanity check both the type and resource id before using container_of() to get a pointer to the associated domain.
--- include/linux/resctrl.h | 9 +++++++++ arch/x86/kernel/cpu/resctrl/core.c | 10 ++++++---- fs/resctrl/ctrlmondata.c | 2 +- 3 files changed, 16 insertions(+), 5 deletions(-)
include/linux/resctrl.h +9 -0
@@ -131,15 +131,24 @@ enum resctrl_domain_type {* @list: all instances of this resource * @id: unique id for this instance * @type: type of this instance +* @rid: resource id for this instance * @cpu_mask: which CPUs share this resource */ struct rdt_domain_hdr {struct list_head list;int id;enum resctrl_domain_type type; +enum resctrl_res_level rid;struct cpumask cpu_mask; }; +static inline bool domain_header_is_valid (struct rdt_domain_hdr *hdr, +enum resctrl_domain_type type, +enum resctrl_res_level rid) +{ +return !WARN_ON_ONCE (hdr->type != type || hdr->rid != rid); +} +/** * struct rdt_ctrl_domain - group of CPUs sharing a resctrl control resource * @hdr: common header for different domain types
arch/x86/kernel/cpu/resctrl/core.c +6 -4
@@ -459,7 +459,7 @@ static void domain_add_cpu_ctrl(int cpu, struct rdt_resource *r) hdr =resctrl_find_domain (&r->ctrl_domains, id, &add_pos);if (hdr) { -if (WARN_ON_ONCE (hdr->type !=RESCTRL_CTRL_DOMAIN )) +if (!domain_header_is_valid (hdr,RESCTRL_CTRL_DOMAIN , r->rid))return ; d = container_of(hdr, struct rdt_ctrl_domain, hdr);
@@ -476,6 +476,7 @@ static void domain_add_cpu_ctrl(int cpu, struct rdt_resource *r) d = &hw_dom->d_resctrl; d->hdr.id = id; d->hdr.type =RESCTRL_CTRL_DOMAIN ; + d->hdr.rid = r->rid;cpumask_set_cpu (cpu, &d->hdr.cpu_mask);rdt_domain_reconfigure_cdp (r);
@@ -515,7 +516,7 @@ static void domain_add_cpu_mon(int cpu, struct rdt_resource *r) hdr =resctrl_find_domain (&r->mon_domains, id, &add_pos);if (hdr) { -if (WARN_ON_ONCE (hdr->type !=RESCTRL_MON_DOMAIN )) +if (!domain_header_is_valid (hdr,RESCTRL_MON_DOMAIN , r->rid))return ; d = container_of(hdr, struct rdt_mon_domain, hdr);
@@ -530,6 +531,7 @@ static void domain_add_cpu_mon(int cpu, struct rdt_resource *r) d = &hw_dom->d_resctrl; d->hdr.id = id; d->hdr.type =RESCTRL_MON_DOMAIN ; + d->hdr.rid = r->rid; ci =get_cpu_cacheinfo_level (cpu,RESCTRL_L3_CACHE );if (!ci) {pr_warn_once ("Can't find L3 cache for CPU:%d resource %s\n" , cpu, r->name);
@@ -586,7 +588,7 @@ static void domain_remove_cpu_ctrl(int cpu, struct rdt_resource *r)return ; } -if (WARN_ON_ONCE (hdr->type !=RESCTRL_CTRL_DOMAIN )) +if (!domain_header_is_valid (hdr,RESCTRL_CTRL_DOMAIN , r->rid))return ; d = container_of(hdr, struct rdt_ctrl_domain, hdr);
@@ -632,7 +634,7 @@ static void domain_remove_cpu_mon(int cpu, struct rdt_resource *r)return ; } -if (WARN_ON_ONCE (hdr->type !=RESCTRL_MON_DOMAIN )) +if (!domain_header_is_valid (hdr,RESCTRL_MON_DOMAIN , r->rid))return ; d = container_of(hdr, struct rdt_mon_domain, hdr);
fs/resctrl/ctrlmondata.c +1 -1
@@ -643,7 +643,7 @@ int rdtgroup_mondata_show(struct seq_file *m, void *arg)* the resource to find the domain with "domid". */ hdr =resctrl_find_domain (&r->mon_domains, domid,NULL ); -if (!hdr ||WARN_ON_ONCE (hdr->type !=RESCTRL_MON_DOMAIN )) { +if (!hdr || !domain_header_is_valid (hdr,RESCTRL_MON_DOMAIN , resid)) { ret = -ENOENT ; goto out; }
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 05/32] x86,fs/resctrl: Improve domain type checking
Hi Tony,
Quoted 6 lines · Tony Luck
The
rdt_domain_hdrstructure is used in both control and monitor domain structures to provide common methods for operations such as adding a CPU to a domain, removing a CPU from a domain, accessing the mask of all CPUs in a domain.The "type" field provides a simple check whether a domain is a
"The "type" field provides" -> "rdt_domain_hdr::type provides"
Quoted 7 lines
control or monitor domain so that programming errors operating on domains will be quickly caught. This is insufficient to catch errors when other resources besides L3 support monitor events.
Add a new
rdt_domain_hdr::ridfield that is initialized when domain structures are allocated. Calldomain_header_is_valid()to sanity
Needs imperative. For example (please feel free to improve ... this and any other suggestion I may have):
"Add rdt_domain_hdr::rid to contain the resource id and initialize it as part of domain structure allocation done by CPU online handler. Call ..."
Quoted 3 lines
check both the type and resource id before using
container_of()to get a pointer to the associated domain.
(sidenote: The last sentence above is very important since it establishes a requirement that domain_header_is_valid() should always be used before container_of(). This does not seem to be consistently followed by this series. I will point out the ones I noticed, please double check the final result to confirm that this pattern is consistently used as intended.)
Quoted 2 lines
Signed-off-by Tony Luck <[email protected]>---
| Reviewed-by: Reinette Chatre <[email protected]>
Reinette
Tony Luck
maintainerPATCH v8 6/32 x86/resctrl: Move L3 initialization into new helper function
In reply to Tony LuckAll resctrl monitor events are associated with the L3 resource, but this is about to change.
To prepare for additional types of monitoring domains, move open coded L3 resource monitoring domain initialization from domain_add_cpu_mon() into a new helper l3_mon_domain_setup() called by domain_add_cpu_mon().
--- arch/x86/kernel/cpu/resctrl/core.c | 56 ++++++++++++++++++------------ 1 file changed, 34 insertions(+), 22 deletions(-)
arch/x86/kernel/cpu/resctrl/core.c +34 -22
@@ -496,34 +496,13 @@ static void domain_add_cpu_ctrl(int cpu, struct rdt_resource *r) } } -static void domain_add_cpu_mon (int cpu,struct rdt_resource *r) +static void l3_mon_domain_setup (int cpu,int id,struct rdt_resource *r,struct list_head *add_pos) { -int id =get_domain_id_from_scope (cpu, r->mon_scope); -struct list_head *add_pos =NULL ;struct rdt_hw_mon_domain *hw_dom; -struct rdt_domain_hdr *hdr;struct rdt_mon_domain *d;struct cacheinfo *ci;int err; -lockdep_assert_held (&domain_list_lock); - -if (id <0 ) { -pr_warn_once ("Can't find monitor domain id for CPU:%d scope:%d for resource %s\n" , - cpu, r->mon_scope, r->name); -return ; - } - - hdr =resctrl_find_domain (&r->mon_domains, id, &add_pos); -if (hdr) { -if (!domain_header_is_valid (hdr,RESCTRL_MON_DOMAIN , r->rid)) -return ; - d = container_of(hdr, struct rdt_mon_domain, hdr); - -cpumask_set_cpu (cpu, &d->hdr.cpu_mask); -return ; - } - hw_dom =kzalloc_node (sizeof (*hw_dom),GFP_KERNEL ,cpu_to_node (cpu));if (!hw_dom)return ;
@@ -558,6 +537,39 @@ static void domain_add_cpu_mon(int cpu, struct rdt_resource *r) } } +static void domain_add_cpu_mon (int cpu,struct rdt_resource *r) +{ +int id =get_domain_id_from_scope (cpu, r->mon_scope); +struct list_head *add_pos =NULL ; +struct rdt_domain_hdr *hdr; + +lockdep_assert_held (&domain_list_lock); + +if (id <0 ) { +pr_warn_once ("Can't find monitor domain id for CPU:%d scope:%d for resource %s\n" , + cpu, r->mon_scope, r->name); +return ; + } + + hdr =resctrl_find_domain (&r->mon_domains, id, &add_pos); +if (hdr) { +if (!domain_header_is_valid (hdr,RESCTRL_MON_DOMAIN , r->rid)) +return ; +cpumask_set_cpu (cpu, &hdr->cpu_mask); + +return ; + } + +switch (r->rid) { +case RDT_RESOURCE_L3 : +l3_mon_domain_setup (cpu, id, r, add_pos); +break ; +default : +WARN_ON_ONCE (1 ); +break ; + } +} +static void domain_add_cpu (int cpu,struct rdt_resource *r) {if (r->alloc_capable)
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 06/32] x86/resctrl: Move L3 initialization into new helper function
Hi Tony,
Quoted 19 lines · Tony Luck
arch/x86/kernel/cpu/resctrl/core.c +19
-0+static void domain_add_cpu_mon (int cpu,struct rdt_resource *r) +{ +int id =get_domain_id_from_scope (cpu, r->mon_scope); +struct list_head *add_pos =NULL ; +struct rdt_domain_hdr *hdr; + +lockdep_assert_held (&domain_list_lock); + +if (id <0 ) { +pr_warn_once ("Can't find monitor domain id for CPU:%d scope:%d for resource %s\n" , + cpu, r->mon_scope, r->name); +return ; + } + + hdr =resctrl_find_domain (&r->mon_domains, id, &add_pos); +if (hdr) { +if (!domain_header_is_valid (hdr,RESCTRL_MON_DOMAIN , r->rid)) +return ; +cpumask_set_cpu (cpu, &hdr->cpu_mask);
arch/x86/kernel/cpu/resctrl/core.c static void domain_add_cpu_mon(int cpu, struct rdt_resource *r) · line 568
Quoted 10 lines
arch/x86/kernel/cpu/resctrl/core.c +10
-0+ +return ; + } + +switch (r->rid) { +case RDT_RESOURCE_L3 : +l3_mon_domain_setup (cpu, id, r, add_pos); +break ; +default : +WARN_ON_ONCE (1 );
As mentioned in v7 feedback [1] this change is inconsistent with similar change to partner function domain_remove_cpu_mon(). Since you did not respond I expected the code to be consistent in this version. Specifically, this can be:
pr_warn_once("Unknown resource rid=%d\n", r->rid);Reinette
Tony Luck
maintainerPATCH v8 7/32 x86,fs/resctrl: Refactor domain_remove_cpu_mon() ready for new domain types
In reply to Tony LuckAll monitoring events are associated with the L3 resource.
The RDT_RESOURCE_L3 resource carries a lot of state in the domain structures which needs to be dealt with when a domain is taken offline by removing the last CPU in the domain.
New telemetry events will be associated with a new package scoped resource with new domain structures.
Refactor domain_remove_cpu_mon() so all the L3 processing is separated from general actions of clearing the CPU bit in the mask and removing sub-directories from the mon_data directory.
resctrl_offline_mon_domain() continues to remove domain specific directories and files from the "mon_data" directories, but can skip the L3 resource specific cleanup when called for other resource types.
--- arch/x86/kernel/cpu/resctrl/core.c | 17 +++++++++++------ fs/resctrl/rdtgroup.c | 5 ++++- 2 files changed, 15 insertions(+), 7 deletions(-)
arch/x86/kernel/cpu/resctrl/core.c +11 -6
@@ -649,17 +649,22 @@ static void domain_remove_cpu_mon(int cpu, struct rdt_resource *r)if (!domain_header_is_valid (hdr,RESCTRL_MON_DOMAIN , r->rid))return ; - d = container_of(hdr, struct rdt_mon_domain, hdr); - hw_dom =resctrl_to_arch_mon_dom (d); +cpumask_clear_cpu (cpu, &hdr->cpu_mask); +if (!cpumask_empty (&hdr->cpu_mask)) +return ; -cpumask_clear_cpu (cpu, &d->hdr.cpu_mask); -if (cpumask_empty (&d->hdr.cpu_mask)) { +switch (r->rid) { +case RDT_RESOURCE_L3 : + d = container_of(hdr, struct rdt_mon_domain, hdr); + hw_dom =resctrl_to_arch_mon_dom (d);resctrl_offline_mon_domain (r, d);list_del_rcu (&d->hdr.list);synchronize_rcu ();mon_domain_free (hw_dom); - -return ; +break ; +default : +pr_warn_once ("Unknown resource rid=%d\n" , r->rid); +break ; } }
fs/resctrl/rdtgroup.c +4 -1
@@ -4047,6 +4047,9 @@ void resctrl_offline_mon_domain(struct rdt_resource *r, struct rdt_mon_domain *dif (resctrl_mounted &&resctrl_arch_mon_capable ())rmdir_mondata_subdir_allrdtgrp (r, d); +if (r->rid !=RDT_RESOURCE_L3 ) + goto out_unlock; +if (resctrl_is_mbm_enabled ())cancel_delayed_work (&d->mbm_over);if (resctrl_is_mon_event_enabled (QOS_L3_OCCUP_EVENT_ID ) &&has_busy_rmid (d)) {
@@ -4063,7 +4066,7 @@ void resctrl_offline_mon_domain(struct rdt_resource *r, struct rdt_mon_domain *d }domain_destroy_mon_state (d); - +out_unlock:mutex_unlock (&rdtgroup_mutex); }
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 07/32] x86,fs/resctrl: Refactor domain_remove_cpu_mon() ready for new domain types
Hi Tony,
Quoted 10 lines · Tony Luck
All monitoring events are associated with the L3 resource.
The
RDT_RESOURCE_L3resource carries a lot of state in the domain structures which needs to be dealt with when a domain is taken offline by removing the last CPU in the domain.New telemetry events will be associated with a new package scoped resource with new domain structures.
Refactor
domain_remove_cpu_mon()so all the L3 processing is separated
"separated" -> "separate"
Quoted 5 lines
from general actions of clearing the CPU bit in the mask and removing sub-directories from the
mon_datadirectory.
resctrl_offline_mon_domain()continues to remove domain specific directories and files from the "mon_data" directories, but can skip the
"can skip" -> "skips"
Quoted 13 lines
L3 resource specific cleanup when called for other resource types.
Signed-off-by Tony Luck <[email protected]>--- arch/x86/kernel/cpu/resctrl/core.c | 17 +++++++++++------ fs/resctrl/rdtgroup.c | 5 ++++- 2 files changed, 15 insertions(+), 7 deletions(-)arch/x86/kernel/cpu/resctrl/core.c +0
-0
arch/x86/kernel/cpu/resctrl/core.c static void domain_remove_cpu_mon(int cpu, struct rdt_resource *r) · line 652
Quoted 4 lines
arch/x86/kernel/cpu/resctrl/core.c +0
-1@@ -649,17 +649,22 @@ static void domain_remove_cpu_mon(int cpu, struct rdt_resource *r)if (!domain_header_is_valid (hdr,RESCTRL_MON_DOMAIN , r->rid))return ; - d = container_of(hdr, struct rdt_mon_domain, hdr);
This is an example where the requirement introduced in patch #5 to use domain_header_is_valid() before container_of() is broken. The container_of() is moved but its sanity check does not follow.
I think the domain_header_is_valid() should also move to be right before the container_of() and when doing so the resource id should be hardcoded to be RDT_RESOURCE_L3.
arch/x86/kernel/cpu/resctrl/core.c static void domain_remove_cpu_mon(int cpu, struct rdt_resource *r) · line 661
Quoted 13 lines
arch/x86/kernel/cpu/resctrl/core.c +7
-3- hw_dom =resctrl_to_arch_mon_dom (d); +cpumask_clear_cpu (cpu, &hdr->cpu_mask); +if (!cpumask_empty (&hdr->cpu_mask)) +return ; -cpumask_clear_cpu (cpu, &d->hdr.cpu_mask); -if (cpumask_empty (&d->hdr.cpu_mask)) { +switch (r->rid) { +case RDT_RESOURCE_L3 : + d = container_of(hdr, struct rdt_mon_domain, hdr); + hw_dom =resctrl_to_arch_mon_dom (d);resctrl_offline_mon_domain (r, d);list_del_rcu (&d->hdr.list);
When making a change please check if same change can be applied to other parts of the code so that the code remains consistent. Like here where hdr can be referenced directly that is now done in domain_remove_cpu_ctrl() and will make these two functions consistent. (oh ... but that change did not actually make it into the next patch even though the cover letter states that it did ...? )
Reinette
Tony Luck
maintainerPATCH v8 8/32 x86/resctrl: Clean up domain_remove_cpu_ctrl()
In reply to Tony LuckFor symmetry with domain_remove_cpu_mon() refactor to take an early return when removing a CPU does not empty the domain.
--- arch/x86/kernel/cpu/resctrl/core.c | 29 ++++++++++++++--------------- 1 file changed, 14 insertions(+), 15 deletions(-)
arch/x86/kernel/cpu/resctrl/core.c +14 -15
@@ -603,25 +603,24 @@ static void domain_remove_cpu_ctrl(int cpu, struct rdt_resource *r)if (!domain_header_is_valid (hdr,RESCTRL_CTRL_DOMAIN , r->rid))return ; +cpumask_clear_cpu (cpu, &hdr->cpu_mask); +if (!cpumask_empty (&hdr->cpu_mask)) +return ; + d = container_of(hdr, struct rdt_ctrl_domain, hdr); hw_dom =resctrl_to_arch_ctrl_dom (d); -cpumask_clear_cpu (cpu, &d->hdr.cpu_mask); -if (cpumask_empty (&d->hdr.cpu_mask)) { -resctrl_offline_ctrl_domain (r, d); -list_del_rcu (&d->hdr.list); -synchronize_rcu (); - -/* -* rdt_ctrl_domain "d" is going to be freed below, so clear -* its pointer from pseudo_lock_region struct. -*/ -if (d->plr) - d->plr->d =NULL ; -ctrl_domain_free (hw_dom); +resctrl_offline_ctrl_domain (r, d); +list_del_rcu (&d->hdr.list); +synchronize_rcu (); -return ; - } +/* +* rdt_ctrl_domain "d" is going to be freed below, so clear +* its pointer from pseudo_lock_region struct. +*/ +if (d->plr) + d->plr->d =NULL ; +ctrl_domain_free (hw_dom); }static void domain_remove_cpu_mon (int cpu,struct rdt_resource *r)
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 08/32] x86/resctrl: Clean up domain_remove_cpu_ctrl()
Hi Tony,
Quoted 2 lines · Tony Luck
For symmetry with
domain_remove_cpu_mon()refactor to take an early return when removing a CPU does not empty the domain.
"refactor" -> "refactor domain_remove_cpu_ctrl()"
so that changelog stands on its own and is not continuation of subject.
Quoted 11 lines
Signed-off-by Tony Luck <[email protected]>--- arch/x86/kernel/cpu/resctrl/core.c | 29 ++++++++++++++--------------- 1 file changed, 14 insertions(+), 15 deletions(-)arch/x86/kernel/cpu/resctrl/core.c +0
-0
arch/x86/kernel/cpu/resctrl/core.c static void domain_remove_cpu_ctrl(int cpu, struct rdt_resource *r) · line 609
Quoted 7 lines
arch/x86/kernel/cpu/resctrl/core.c +4
-0@@ -603,25 +603,24 @@ static void domain_remove_cpu_ctrl(int cpu, struct rdt_resource *r)if (!domain_header_is_valid (hdr,RESCTRL_CTRL_DOMAIN , r->rid))return ; +cpumask_clear_cpu (cpu, &hdr->cpu_mask); +if (!cpumask_empty (&hdr->cpu_mask)) +return ; +
Here is another instance where the domain_header_is_valid() checking is moved away from the subsequent container_of() that it is intended to protect.
Quoted 8 lines
arch/x86/kernel/cpu/resctrl/core.c +0
-5d = container_of(hdr, struct rdt_ctrl_domain, hdr); hw_dom =resctrl_to_arch_ctrl_dom (d); -cpumask_clear_cpu (cpu, &d->hdr.cpu_mask); -if (cpumask_empty (&d->hdr.cpu_mask)) { -resctrl_offline_ctrl_domain (r, d); -list_del_rcu (&d->hdr.list); -synchronize_rcu ();
arch/x86/kernel/cpu/resctrl/core.c static void domain_remove_cpu_ctrl(int cpu, struct rdt_resource *r) · line 614
Quoted 10 lines
arch/x86/kernel/cpu/resctrl/core.c +2
-8- -/* -* rdt_ctrl_domain "d" is going to be freed below, so clear -* its pointer from pseudo_lock_region struct. -*/ -if (d->plr) - d->plr->d =NULL ; -ctrl_domain_free (hw_dom); +resctrl_offline_ctrl_domain (r, d); +list_del_rcu (&d->hdr.list);
Missing the change mentioned in cover letter.
Quoted 4 lines
arch/x86/kernel/cpu/resctrl/core.c +1
-2+synchronize_rcu (); -return ; - }
arch/x86/kernel/cpu/resctrl/core.c static void domain_remove_cpu_ctrl(int cpu, struct rdt_resource *r) · line 626
Quoted 10 lines
arch/x86/kernel/cpu/resctrl/core.c +7
-0+/* +* rdt_ctrl_domain "d" is going to be freed below, so clear +* its pointer from pseudo_lock_region struct. +*/ +if (d->plr) + d->plr->d =NULL ; +ctrl_domain_free (hw_dom); }static void domain_remove_cpu_mon (int cpu,struct rdt_resource *r)
Reinette
Tony Luck
maintainerPATCH v8 9/32 x86,fs/resctrl: Use struct rdt_domain_hdr instead of struct rdt_mon_domain
In reply to Tony LuckAll monitoring events are associated with the L3 resource and it made sense to use the L3 specific "struct rdt_mon_domain *" arguments to functions manipulating domains.
But the addition of monitor events tied to other resources changes this assumption.
Change the calling sequence to use the generic struct rdt_domain_hdr for domain addition and deletion to preserve as much common code as possible. This will simplify enabling of enumeration of domains for events in other resources.
Make the same change to allow reading events in other resources. In this case the code flow passes from mon_event_read() via smp_call*() eventually to __mon_event_count() so the rmid_read::d field is replaced with the new rmid_read::hdr field.
The mon_data structure is unchanged, but documentation is updated to note that mon_data::sum is only used for RDT_RESOURCE_L3.
--- include/linux/resctrl.h | 8 +- fs/resctrl/internal.h | 14 ++-- arch/x86/kernel/cpu/resctrl/core.c | 6 +- arch/x86/kernel/cpu/resctrl/monitor.c | 18 ++++- fs/resctrl/ctrlmondata.c | 14 ++-- fs/resctrl/monitor.c | 30 +++++--- fs/resctrl/rdtgroup.c | 103 ++++++++++++++++++-------- 7 files changed, 129 insertions(+), 64 deletions(-)
include/linux/resctrl.h +4 -4
@@ -452,9 +452,9 @@ int resctrl_arch_update_one(struct rdt_resource *r, struct rdt_ctrl_domain *d,u32 resctrl_arch_get_config (struct rdt_resource *r,struct rdt_ctrl_domain *d,u32 closid,enum resctrl_conf_type type);int resctrl_online_ctrl_domain (struct rdt_resource *r,struct rdt_ctrl_domain *d); -int resctrl_online_mon_domain (struct rdt_resource *r,struct rdt_mon_domain *d); +int resctrl_online_mon_domain (struct rdt_resource *r,struct rdt_domain_hdr *hdr);void resctrl_offline_ctrl_domain (struct rdt_resource *r,struct rdt_ctrl_domain *d); -void resctrl_offline_mon_domain (struct rdt_resource *r,struct rdt_mon_domain *d); +void resctrl_offline_mon_domain (struct rdt_resource *r,struct rdt_domain_hdr *hdr);void resctrl_online_cpu (unsigned int cpu);void resctrl_offline_cpu (unsigned int cpu);
@@ -462,7 +462,7 @@ void resctrl_offline_cpu(unsigned int cpu);* resctrl_arch_rmid_read() - Read the eventid counter corresponding to rmid * for this resource and domain. * @r: resource that the counter should be read from. -* @d: domain that the counter should be read from. +* @hdr: Header of domain that the counter should be read from. * @closid: closid that matches the rmid. Depending on the architecture, the * counter may match traffic of both @closid and @rmid, or @rmid * only.
@@ -483,7 +483,7 @@ void resctrl_offline_cpu(unsigned int cpu);* Return: * 0 on success, or -EIO, -EINVAL etc on error. */ -int resctrl_arch_rmid_read (struct rdt_resource *r,struct rdt_mon_domain *d, +int resctrl_arch_rmid_read (struct rdt_resource *r,struct rdt_domain_hdr *hdr,u32 closid,u32 rmid,enum resctrl_event_id eventid,u64 *val,void *arch_mon_ctx);
fs/resctrl/internal.h +7 -7
@@ -77,8 +77,8 @@ extern struct mon_evt mon_event_all[QOS_NUM_EVENTS];* @list: Member of the global @mon_data_kn_priv_list list. * @rid: Resource id associated with the event file. * @evtid: Event id associated with the event file. -* @sum: Set when event must be summed across multiple -* domains. +* @sum: Set for RDT_RESOURCE_L3 when event must be summed +* across multiple domains. * @domid: When @sum is zero this is the domain to which * the event file belongs. When @sum is one this * is the id of the L3 cache that all domains to be
@@ -101,22 +101,22 @@ struct mon_data {* resource group then its event count is summed with the count from all * its child resource groups. * @r: Resource describing the properties of the event being read. -* @d: Domain that the counter should be read from. If NULL then sum all +* @hdr: Header of domain that the counter should be read from. If NULL then sum all * domains in @r sharing L3 @ci.id * @evtid: Which monitor event to read. * @first: Initialize MBM counter when true. -* @ci_id: Cacheinfo id for L3. Only set when @d is NULL. Used when summing domains. +* @ci_id: Cacheinfo id for L3. Only set when @hdr is NULL. Used when summing domains. * @err: Error encountered when reading counter. * @val: Returned value of event counter. If @rgrp is a parent resource group, * @val includes the sum of event counts from its child resource groups. -* If @d is NULL, @val includes the sum of all domains in @r sharing @ci.id, +* If @hdr is NULL, @val includes the sum of all domains in @r sharing @ci.id, * (summed across child resource groups if @rgrp is a parent resource group). * @arch_mon_ctx: Hardware monitor allocated for this read request (MPAM only). */ struct rmid_read {struct rdtgroup *rgrp;struct rdt_resource *r; -struct rdt_mon_domain *d; +struct rdt_domain_hdr *hdr;enum resctrl_event_id evtid;bool first;unsigned int ci_id;
@@ -352,7 +352,7 @@ void mon_event_count(void *info);int rdtgroup_mondata_show (struct seq_file *m,void *arg);void mon_event_read (struct rmid_read *rr,struct rdt_resource *r, -struct rdt_mon_domain *d,struct rdtgroup *rdtgrp, +struct rdt_domain_hdr *hdr,struct rdtgroup *rdtgrp,cpumask_t *cpumask,int evtid,int first);int resctrl_mon_resource_init (void );
arch/x86/kernel/cpu/resctrl/core.c +3 -3
@@ -529,7 +529,7 @@ static void l3_mon_domain_setup(int cpu, int id, struct rdt_resource *r, structlist_add_tail_rcu (&d->hdr.list, add_pos); - err =resctrl_online_mon_domain (r, d); + err =resctrl_online_mon_domain (r, &d->hdr);if (err) {list_del_rcu (&d->hdr.list);synchronize_rcu ();
@@ -611,7 +611,7 @@ static void domain_remove_cpu_ctrl(int cpu, struct rdt_resource *r) hw_dom =resctrl_to_arch_ctrl_dom (d);resctrl_offline_ctrl_domain (r, d); -list_del_rcu (&d->hdr.list); +list_del_rcu (&hdr->list);synchronize_rcu ();/*
@@ -656,7 +656,7 @@ static void domain_remove_cpu_mon(int cpu, struct rdt_resource *r)case RDT_RESOURCE_L3 : d = container_of(hdr, struct rdt_mon_domain, hdr); hw_dom =resctrl_to_arch_mon_dom (d); -resctrl_offline_mon_domain (r, d); +resctrl_offline_mon_domain (r, hdr);list_del_rcu (&d->hdr.list);synchronize_rcu ();mon_domain_free (hw_dom);
arch/x86/kernel/cpu/resctrl/monitor.c +14 -4
@@ -217,20 +217,30 @@ static u64 mbm_overflow_count(u64 prev_msr, u64 cur_msr, unsigned int width)return chunks >> shift; } -int resctrl_arch_rmid_read (struct rdt_resource *r,struct rdt_mon_domain *d, +int resctrl_arch_rmid_read (struct rdt_resource *r,struct rdt_domain_hdr *hdr,u32 unused,u32 rmid,enum resctrl_event_id eventid,u64 *val,void *ignored) { -struct rdt_hw_mon_domain *hw_dom =resctrl_to_arch_mon_dom (d); -struct rdt_hw_resource *hw_res =resctrl_to_arch_res (r); -int cpu =cpumask_any (&d->hdr.cpu_mask); +int cpu =cpumask_any (&hdr->cpu_mask); +struct rdt_hw_mon_domain *hw_dom; +struct rdt_hw_resource *hw_res;struct arch_mbm_state *am; +struct rdt_mon_domain *d;u64 msr_val, chunks;u32 prmid;int ret;resctrl_arch_rmid_read_context_check (); +if (r->rid !=RDT_RESOURCE_L3 ) +return -EINVAL ; + +if (!domain_header_is_valid (hdr,RESCTRL_MON_DOMAIN ,RDT_RESOURCE_L3 )) +return -EINVAL ; + + d = container_of(hdr, struct rdt_mon_domain, hdr); + hw_dom =resctrl_to_arch_mon_dom (d); + hw_res =resctrl_to_arch_res (r); prmid =logical_rmid_to_physical_rmid (cpu, rmid); ret =__rmid_read_phys (prmid, eventid, &msr_val);if (ret)
fs/resctrl/ctrlmondata.c +9 -5
@@ -547,7 +547,7 @@ struct rdt_domain_hdr *resctrl_find_domain(struct list_head *h, int id, }void mon_event_read (struct rmid_read *rr,struct rdt_resource *r, -struct rdt_mon_domain *d,struct rdtgroup *rdtgrp, +struct rdt_domain_hdr *hdr,struct rdtgroup *rdtgrp,cpumask_t *cpumask,int evtid,int first) {int cpu;
@@ -561,7 +561,7 @@ void mon_event_read(struct rmid_read *rr, struct rdt_resource *r, rr->rgrp = rdtgrp; rr->evtid = evtid; rr->r = r; - rr->d = d; + rr->hdr = hdr; rr->first = first; rr->arch_mon_ctx =resctrl_arch_mon_ctx_alloc (r, evtid);if (IS_ERR (rr->arch_mon_ctx)) {
@@ -592,7 +592,6 @@ int rdtgroup_mondata_show(struct seq_file *m, void *arg)enum resctrl_event_id evtid;struct rdt_domain_hdr *hdr;struct rmid_read rr = {0 }; -struct rdt_mon_domain *d;struct rdtgroup *rdtgrp;int domid, cpu, ret =0 ;struct rdt_resource *r;
@@ -617,6 +616,12 @@ int rdtgroup_mondata_show(struct seq_file *m, void *arg) r =resctrl_arch_get_resource (resid);if (md->sum) { +struct rdt_mon_domain *d; + +if (WARN_ON_ONCE (resid !=RDT_RESOURCE_L3 )) { + ret = -EIO ; + goto out; + }/* * This file requires summing across all domains that share * the L3 cache id that was provided in the "domid" field of the
@@ -647,8 +652,7 @@ int rdtgroup_mondata_show(struct seq_file *m, void *arg) ret = -ENOENT ; goto out; } - d = container_of(hdr, struct rdt_mon_domain, hdr); -mon_event_read (&rr, r, d, rdtgrp, &d->hdr.cpu_mask, evtid, false); +mon_event_read (&rr, r, hdr, rdtgrp, &hdr->cpu_mask, evtid, false); } checkresult:
fs/resctrl/monitor.c +20 -10
@@ -159,7 +159,7 @@ void __check_limbo(struct rdt_mon_domain *d, bool force_free)break ; entry =__rmid_entry (idx); -if (resctrl_arch_rmid_read (r, d, entry->closid, entry->rmid, +if (resctrl_arch_rmid_read (r, &d->hdr, entry->closid, entry->rmid,QOS_L3_OCCUP_EVENT_ID , &val, arch_mon_ctx)) { rmid_dirty = true;
@@ -365,19 +365,22 @@ static int __mon_event_count(u32 closid, u32 rmid, struct rmid_read *rr)int err, ret;u64 tval =0 ; -if (rr->first) { -resctrl_arch_reset_rmid (rr->r, rr->d, closid, rmid, rr->evtid); - m =get_mbm_state (rr->d, closid, rmid, rr->evtid); +if (rr->r->rid ==RDT_RESOURCE_L3 && rr->first) { +if (!domain_header_is_valid (rr->hdr,RESCTRL_MON_DOMAIN ,RDT_RESOURCE_L3 )) +return -EINVAL ; + d = container_of(rr->hdr, struct rdt_mon_domain, hdr); +resctrl_arch_reset_rmid (rr->r, d, closid, rmid, rr->evtid); + m =get_mbm_state (d, closid, rmid, rr->evtid);if (m)memset (m,0 ,sizeof (struct mbm_state ));return 0 ; } -if (rr->d) { +if (rr->hdr) {/* Reading a single domain, must be on a CPU in that domain. */ -if (!cpumask_test_cpu (cpu, &rr->d->hdr.cpu_mask)) +if (!cpumask_test_cpu (cpu, &rr->hdr->cpu_mask))return -EINVAL ; - rr->err =resctrl_arch_rmid_read (rr->r, rr->d, closid, rmid, + rr->err =resctrl_arch_rmid_read (rr->r, rr->hdr, closid, rmid, rr->evtid, &tval, rr->arch_mon_ctx);if (rr->err)return rr->err;
@@ -387,6 +390,9 @@ static int __mon_event_count(u32 closid, u32 rmid, struct rmid_read *rr)return 0 ; } +if (WARN_ON_ONCE (rr->r->rid !=RDT_RESOURCE_L3 )) +return -EINVAL ; +/* Summing domains that share a cache, must be on a CPU for that cache. */ ci =get_cpu_cacheinfo_level (cpu,RESCTRL_L3_CACHE );if (!ci || ci->id != rr->ci_id)
@@ -403,7 +409,7 @@ static int __mon_event_count(u32 closid, u32 rmid, struct rmid_read *rr)list_for_each_entry (d, &rr->r->mon_domains, hdr.list) {if (d->ci_id != rr->ci_id)continue ; - err =resctrl_arch_rmid_read (rr->r, d, closid, rmid, + err =resctrl_arch_rmid_read (rr->r, &d->hdr, closid, rmid, rr->evtid, &tval, rr->arch_mon_ctx);if (!err) { rr->val += tval;
@@ -432,9 +438,13 @@ static int __mon_event_count(u32 closid, u32 rmid, struct rmid_read *rr)static void mbm_bw_count (u32 closid,u32 rmid,struct rmid_read *rr) {u64 cur_bw, bytes, cur_bytes; +struct rdt_mon_domain *d;struct mbm_state *m; - m =get_mbm_state (rr->d, closid, rmid, rr->evtid); +if (!domain_header_is_valid (rr->hdr,RESCTRL_MON_DOMAIN ,RDT_RESOURCE_L3 )) +return ; + d = container_of(rr->hdr, struct rdt_mon_domain, hdr); + m =get_mbm_state (d, closid, rmid, rr->evtid);if (WARN_ON_ONCE (!m))return ;
@@ -608,7 +618,7 @@ static void mbm_update_one_event(struct rdt_resource *r, struct rdt_mon_domain *struct rmid_read rr = {0 }; rr.r = r; - rr.d = d; + rr.hdr = &d->hdr; rr.evtid = evtid; rr.arch_mon_ctx =resctrl_arch_mon_ctx_alloc (rr.r, rr.evtid);if (IS_ERR (rr.arch_mon_ctx)) {
fs/resctrl/rdtgroup.c +72 -31
244 lines not on this page · raw message
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 09/32] x86,fs/resctrl: Use struct rdt_domain_hdr instead of struct rdt_mon_domain
Hi Tony,
Quoted 6 lines · Tony Luck
All monitoring events are associated with the L3 resource and it made sense to use the L3 specific "struct
rdt_mon_domain*" arguments to functions manipulating domains.But the addition of monitor events tied to other resources changes this assumption.
What assumption?
How about:
"Telemetry events will be tied to another resource. This requires the
functions that manipulate domains to not be L3 specific."
Quoted 9 lines
Change the calling sequence to use the generic struct
rdt_domain_hdrfor domain addition and deletion to preserve as much common code as possible. This will simplify enabling of enumeration of domains for events in other resources.Make the same change to allow reading events in other resources. In this case the code flow passes from
mon_event_read()via smp_call*() eventually to__mon_event_count()so thermid_read::dfield is replaced
"so the rmid_read::d field is replaced" -> "so replace the L3 specific domain pointer rmid_read::d with rmid_read::hdr that points to the generic domain header"
(switch to imperative and remove unnecessary "field" term)
Quoted 4 lines
with the new
rmid_read::hdrfield.The
mon_datastructure is unchanged, but documentation is updated to note thatmon_data::sumis only used forRDT_RESOURCE_L3.
wait ... this looks familiar ... (looks at v7 feedback) ... same feedback here as in v7 :(
Quoted 3 lines
Signed-off-by Tony Luck <[email protected]>---
...
Quoted 14 lines
arch/x86/kernel/cpu/resctrl/core.c +1
-1@@ -529,7 +529,7 @@ static void l3_mon_domain_setup(int cpu, int id, struct rdt_resource *r, structlist_add_tail_rcu (&d->hdr.list, add_pos); - err =resctrl_online_mon_domain (r, d); + err =resctrl_online_mon_domain (r, &d->hdr);if (err) {list_del_rcu (&d->hdr.list);synchronize_rcu ();
arch/x86/kernel/cpu/resctrl/core.c static void domain_remove_cpu_ctrl(int cpu, struct rdt_resource *r) · line 616
Quoted 7 lines
arch/x86/kernel/cpu/resctrl/core.c +1
-1@@ -611,7 +611,7 @@ static void domain_remove_cpu_ctrl(int cpu, struct rdt_resource *r) hw_dom =resctrl_to_arch_ctrl_dom (d);resctrl_offline_ctrl_domain (r, d); -list_del_rcu (&d->hdr.list); +list_del_rcu (&hdr->list);synchronize_rcu ();
Looks like the change intended for patch #8 landed here instead.
arch/x86/kernel/cpu/resctrl/core.c static void domain_remove_cpu_ctrl(int cpu, struct rdt_resource *r) · line 617
Quoted 1 line
arch/x86/kernel/cpu/resctrl/core.c +0
-0/*
Reinette
Tony Luck
maintainerPATCH v8 10/32 x86,fs/resctrl: Rename struct rdt_mon_domain and rdt_hw_mon_domain
In reply to Tony LuckAll monitoring events are associated with the L3 resource.
This will change when support for telemetry events is added.
The structures to track monitor domains of the L3 resource at both the file system and architecture level have generic names. This may cause confusion when support for monitoring events in other resources is added.
Rename by adding "l3_" into the names:rdt_mon_domain -> rdt_l3_mon_domainrdt_hw_mon_domain -> rdt_hw_l3_mon_domain
No functional change.
--- include/linux/resctrl.h | 16 ++++++------ arch/x86/kernel/cpu/resctrl/internal.h | 16 ++++++------ fs/resctrl/internal.h | 8 +++--- arch/x86/kernel/cpu/resctrl/core.c | 14 +++++----- arch/x86/kernel/cpu/resctrl/monitor.c | 18 ++++++------- fs/resctrl/ctrlmondata.c | 2 +- fs/resctrl/monitor.c | 34 ++++++++++++------------ fs/resctrl/rdtgroup.c | 36 +++++++++++++------------- 8 files changed, 72 insertions(+), 72 deletions(-)
include/linux/resctrl.h +8 -8
@@ -166,7 +166,7 @@ struct rdt_ctrl_domain { };/** -* struct rdt_mon_domain - group of CPUs sharing a resctrl monitor resource +* struct rdt_l3_mon_domain - group of CPUs sharing a resctrl monitor resource * @hdr: common header for different domain types * @ci_id: cache info id for this domain * @rmid_busy_llc: bitmap of which limbo RMIDs are above threshold
@@ -178,7 +178,7 @@ struct rdt_ctrl_domain {* @mbm_work_cpu: worker CPU for MBM h/w counters * @cqm_work_cpu: worker CPU for CQM h/w counters */ -struct rdt_mon_domain { +struct rdt_l3_mon_domain {struct rdt_domain_hdr hdr;unsigned int ci_id;unsigned long *rmid_busy_llc;
@@ -334,10 +334,10 @@ struct resctrl_cpu_defaults { };struct resctrl_mon_config_info { -struct rdt_resource *r; -struct rdt_mon_domain *d; -u32 evtid; -u32 mon_config; +struct rdt_resource *r; +struct rdt_l3_mon_domain *d; +u32 evtid; +u32 mon_config; };/**
@@ -530,7 +530,7 @@ struct rdt_domain_hdr *resctrl_find_domain(struct list_head *h, int id,* * This can be called from any CPU. */ -void resctrl_arch_reset_rmid (struct rdt_resource *r,struct rdt_mon_domain *d, +void resctrl_arch_reset_rmid (struct rdt_resource *r,struct rdt_l3_mon_domain *d,u32 closid,u32 rmid,enum resctrl_event_id eventid);
@@ -543,7 +543,7 @@ void resctrl_arch_reset_rmid(struct rdt_resource *r, struct rdt_mon_domain *d,* * This can be called from any CPU. */ -void resctrl_arch_reset_rmid_all (struct rdt_resource *r,struct rdt_mon_domain *d); +void resctrl_arch_reset_rmid_all (struct rdt_resource *r,struct rdt_l3_mon_domain *d);/** * resctrl_arch_reset_all_ctrls() - Reset the control for each CLOSID to its
arch/x86/kernel/cpu/resctrl/internal.h +8 -8
@@ -51,17 +51,17 @@ struct rdt_hw_ctrl_domain { };/** -* struct rdt_hw_mon_domain - Arch private attributes of a set of CPUs that share -* a resource for a monitor function -* @d_resctrl: Properties exposed to the resctrl file system +* struct rdt_hw_l3_mon_domain - Arch private attributes of a set of CPUs that share +* a resource for a monitor function +* @d_resctrl: Properties exposed to the resctrl file system * @arch_mbm_states: Per-event pointer to the MBM event's saved state. * An MBM event's state is an array of struct arch_mbm_state * indexed by RMID on x86. * * Members of this structure are accessed via helpers that provide abstraction. */ -struct rdt_hw_mon_domain { -struct rdt_mon_domain d_resctrl; +struct rdt_hw_l3_mon_domain { +struct rdt_l3_mon_domain d_resctrl;struct arch_mbm_state *arch_mbm_states[QOS_NUM_L3_MBM_EVENTS ]; };
@@ -70,9 +70,9 @@ static inline struct rdt_hw_ctrl_domain *resctrl_to_arch_ctrl_dom(struct rdt_ctr return container_of(r, struct rdt_hw_ctrl_domain, d_resctrl); } -static inline struct rdt_hw_mon_domain *resctrl_to_arch_mon_dom (struct rdt_mon_domain *r) +static inline struct rdt_hw_l3_mon_domain *resctrl_to_arch_mon_dom (struct rdt_l3_mon_domain *r) { - return container_of(r, struct rdt_hw_mon_domain, d_resctrl); + return container_of(r, struct rdt_hw_l3_mon_domain, d_resctrl); }/**
@@ -124,7 +124,7 @@ static inline struct rdt_hw_resource *resctrl_to_arch_res(struct rdt_resource *rextern struct rdt_hw_resource rdt_resources_all[]; -void arch_mon_domain_online (struct rdt_resource *r,struct rdt_mon_domain *d); +void arch_mon_domain_online (struct rdt_resource *r,struct rdt_l3_mon_domain *d);/* CPUID.(EAX=10H, ECX=ResID=1).EAX */ union cpuid_0x10_1_eax {
fs/resctrl/internal.h +4 -4
@@ -357,7 +357,7 @@ void mon_event_read(struct rmid_read *rr, struct rdt_resource *r,int resctrl_mon_resource_init (void ); -void mbm_setup_overflow_handler (struct rdt_mon_domain *dom, +void mbm_setup_overflow_handler (struct rdt_l3_mon_domain *dom,unsigned long delay_ms,int exclude_cpu);
@@ -365,14 +365,14 @@ void mbm_handle_overflow(struct work_struct *work);bool is_mba_sc (struct rdt_resource *r); -void cqm_setup_limbo_handler (struct rdt_mon_domain *dom,unsigned long delay_ms, +void cqm_setup_limbo_handler (struct rdt_l3_mon_domain *dom,unsigned long delay_ms,int exclude_cpu);void cqm_handle_limbo (struct work_struct *work); -bool has_busy_rmid (struct rdt_mon_domain *d); +bool has_busy_rmid (struct rdt_l3_mon_domain *d); -void __check_limbo (struct rdt_mon_domain *d,bool force_free); +void __check_limbo (struct rdt_l3_mon_domain *d,bool force_free);void resctrl_file_fflags_init (const char *config,unsigned long fflags);
arch/x86/kernel/cpu/resctrl/core.c +7 -7
@@ -363,7 +363,7 @@ static void ctrl_domain_free(struct rdt_hw_ctrl_domain *hw_dom)kfree (hw_dom); } -static void mon_domain_free (struct rdt_hw_mon_domain *hw_dom) +static void mon_domain_free (struct rdt_hw_l3_mon_domain *hw_dom) {int idx;
@@ -400,7 +400,7 @@ static int domain_setup_ctrlval(struct rdt_resource *r, struct rdt_ctrl_domain ** @num_rmid: The size of the MBM counter array * @hw_dom: The domain that owns the allocated arrays */ -static int arch_domain_mbm_alloc (u32 num_rmid,struct rdt_hw_mon_domain *hw_dom) +static int arch_domain_mbm_alloc (u32 num_rmid,struct rdt_hw_l3_mon_domain *hw_dom) {size_t tsize =sizeof (*hw_dom->arch_mbm_states[0 ]);enum resctrl_event_id eventid;
@@ -498,8 +498,8 @@ static void domain_add_cpu_ctrl(int cpu, struct rdt_resource *r)static void l3_mon_domain_setup (int cpu,int id,struct rdt_resource *r,struct list_head *add_pos) { -struct rdt_hw_mon_domain *hw_dom; -struct rdt_mon_domain *d; +struct rdt_hw_l3_mon_domain *hw_dom; +struct rdt_l3_mon_domain *d;struct cacheinfo *ci;int err;
@@ -626,9 +626,9 @@ static void domain_remove_cpu_ctrl(int cpu, struct rdt_resource *r)static void domain_remove_cpu_mon (int cpu,struct rdt_resource *r) {int id =get_domain_id_from_scope (cpu, r->mon_scope); -struct rdt_hw_mon_domain *hw_dom; +struct rdt_hw_l3_mon_domain *hw_dom; +struct rdt_l3_mon_domain *d;struct rdt_domain_hdr *hdr; -struct rdt_mon_domain *d;lockdep_assert_held (&domain_list_lock);
@@ -654,7 +654,7 @@ static void domain_remove_cpu_mon(int cpu, struct rdt_resource *r)switch (r->rid) {case RDT_RESOURCE_L3 : - d = container_of(hdr, struct rdt_mon_domain, hdr); + d = container_of(hdr, struct rdt_l3_mon_domain, hdr); hw_dom =resctrl_to_arch_mon_dom (d);resctrl_offline_mon_domain (r, hdr);list_del_rcu (&d->hdr.list);
arch/x86/kernel/cpu/resctrl/monitor.c +9 -9
@@ -157,7 +157,7 @@ static int __rmid_read_phys(u32 prmid, enum resctrl_event_id eventid, u64 *val)return 0 ; } -static struct arch_mbm_state *get_arch_mbm_state (struct rdt_hw_mon_domain *hw_dom, +static struct arch_mbm_state *get_arch_mbm_state (struct rdt_hw_l3_mon_domain *hw_dom,u32 rmid,enum resctrl_event_id eventid) {
@@ -171,11 +171,11 @@ static struct arch_mbm_state *get_arch_mbm_state(struct rdt_hw_mon_domain *hw_doreturn state ? &state[rmid] :NULL ; } -void resctrl_arch_reset_rmid (struct rdt_resource *r,struct rdt_mon_domain *d, +void resctrl_arch_reset_rmid (struct rdt_resource *r,struct rdt_l3_mon_domain *d,u32 unused,u32 rmid,enum resctrl_event_id eventid) { -struct rdt_hw_mon_domain *hw_dom =resctrl_to_arch_mon_dom (d); +struct rdt_hw_l3_mon_domain *hw_dom =resctrl_to_arch_mon_dom (d);int cpu =cpumask_any (&d->hdr.cpu_mask);struct arch_mbm_state *am;u32 prmid;
@@ -194,9 +194,9 @@ void resctrl_arch_reset_rmid(struct rdt_resource *r, struct rdt_mon_domain *d,* Assumes that hardware counters are also reset and thus that there is * no need to record initial non-zero counts. */ -void resctrl_arch_reset_rmid_all (struct rdt_resource *r,struct rdt_mon_domain *d) +void resctrl_arch_reset_rmid_all (struct rdt_resource *r,struct rdt_l3_mon_domain *d) { -struct rdt_hw_mon_domain *hw_dom =resctrl_to_arch_mon_dom (d); +struct rdt_hw_l3_mon_domain *hw_dom =resctrl_to_arch_mon_dom (d);enum resctrl_event_id eventid;int idx;
@@ -222,10 +222,10 @@ int resctrl_arch_rmid_read(struct rdt_resource *r, struct rdt_domain_hdr *hdr, u64 *val, void *ignored) {int cpu =cpumask_any (&hdr->cpu_mask); -struct rdt_hw_mon_domain *hw_dom; +struct rdt_hw_l3_mon_domain *hw_dom;struct rdt_hw_resource *hw_res; +struct rdt_l3_mon_domain *d;struct arch_mbm_state *am; -struct rdt_mon_domain *d;u64 msr_val, chunks;u32 prmid;int ret;
@@ -238,7 +238,7 @@ int resctrl_arch_rmid_read(struct rdt_resource *r, struct rdt_domain_hdr *hdr,if (!domain_header_is_valid (hdr,RESCTRL_MON_DOMAIN ,RDT_RESOURCE_L3 ))return -EINVAL ; - d = container_of(hdr, struct rdt_mon_domain, hdr); + d = container_of(hdr, struct rdt_l3_mon_domain, hdr); hw_dom =resctrl_to_arch_mon_dom (d); hw_res =resctrl_to_arch_res (r); prmid =logical_rmid_to_physical_rmid (cpu, rmid);
@@ -275,7 +275,7 @@ int resctrl_arch_rmid_read(struct rdt_resource *r, struct rdt_domain_hdr *hdr,* must adjust RMID counter numbers based on SNC node. See * logical_rmid_to_physical_rmid() for code that does this. */ -void arch_mon_domain_online (struct rdt_resource *r,struct rdt_mon_domain *d) +void arch_mon_domain_online (struct rdt_resource *r,struct rdt_l3_mon_domain *d) {if (snc_nodes_per_l3_cache >1 )msr_clear_bit (MSR_RMID_SNC_CONFIG ,0 );
fs/resctrl/ctrlmondata.c +1 -1
@@ -616,7 +616,7 @@ int rdtgroup_mondata_show(struct seq_file *m, void *arg) r =resctrl_arch_get_resource (resid);if (md->sum) { -struct rdt_mon_domain *d; +struct rdt_l3_mon_domain *d;if (WARN_ON_ONCE (resid !=RDT_RESOURCE_L3 )) { ret = -EIO ;
fs/resctrl/monitor.c +17 -17
@@ -130,7 +130,7 @@ static void limbo_release_entry(struct rmid_entry *entry)* decrement the count. If the busy count gets to zero on an RMID, we * free the RMID */ -void __check_limbo (struct rdt_mon_domain *d,bool force_free) +void __check_limbo (struct rdt_l3_mon_domain *d,bool force_free) {struct rdt_resource *r =resctrl_arch_get_resource (RDT_RESOURCE_L3 );u32 idx_limit =resctrl_arch_system_num_rmid_idx ();
@@ -188,7 +188,7 @@ void __check_limbo(struct rdt_mon_domain *d, bool force_free)resctrl_arch_mon_ctx_free (r,QOS_L3_OCCUP_EVENT_ID , arch_mon_ctx); } -bool has_busy_rmid (struct rdt_mon_domain *d) +bool has_busy_rmid (struct rdt_l3_mon_domain *d) {u32 idx_limit =resctrl_arch_system_num_rmid_idx ();
@@ -289,7 +289,7 @@ int alloc_rmid(u32 closid)static void add_rmid_to_limbo (struct rmid_entry *entry) {struct rdt_resource *r =resctrl_arch_get_resource (RDT_RESOURCE_L3 ); -struct rdt_mon_domain *d; +struct rdt_l3_mon_domain *d;u32 idx;lockdep_assert_held (&rdtgroup_mutex);
@@ -342,7 +342,7 @@ void free_rmid(u32 closid, u32 rmid)list_add_tail (&entry->list, &rmid_free_lru); } -static struct mbm_state *get_mbm_state (struct rdt_mon_domain *d,u32 closid, +static struct mbm_state *get_mbm_state (struct rdt_l3_mon_domain *d,u32 closid,u32 rmid,enum resctrl_event_id evtid) {u32 idx =resctrl_arch_rmid_idx_encode (closid, rmid);
@@ -359,7 +359,7 @@ static struct mbm_state *get_mbm_state(struct rdt_mon_domain *d, u32 closid,static int __mon_event_count (u32 closid,u32 rmid,struct rmid_read *rr) {int cpu =smp_processor_id (); -struct rdt_mon_domain *d; +struct rdt_l3_mon_domain *d;struct cacheinfo *ci;struct mbm_state *m;int err, ret;
@@ -368,7 +368,7 @@ static int __mon_event_count(u32 closid, u32 rmid, struct rmid_read *rr)if (rr->r->rid ==RDT_RESOURCE_L3 && rr->first) {if (!domain_header_is_valid (rr->hdr,RESCTRL_MON_DOMAIN ,RDT_RESOURCE_L3 ))return -EINVAL ; - d = container_of(rr->hdr, struct rdt_mon_domain, hdr); + d = container_of(rr->hdr, struct rdt_l3_mon_domain, hdr);resctrl_arch_reset_rmid (rr->r, d, closid, rmid, rr->evtid); m =get_mbm_state (d, closid, rmid, rr->evtid);if (m)
@@ -438,12 +438,12 @@ static int __mon_event_count(u32 closid, u32 rmid, struct rmid_read *rr)static void mbm_bw_count (u32 closid,u32 rmid,struct rmid_read *rr) {u64 cur_bw, bytes, cur_bytes; -struct rdt_mon_domain *d; +struct rdt_l3_mon_domain *d;struct mbm_state *m;if (!domain_header_is_valid (rr->hdr,RESCTRL_MON_DOMAIN ,RDT_RESOURCE_L3 ))return ; - d = container_of(rr->hdr, struct rdt_mon_domain, hdr); + d = container_of(rr->hdr, struct rdt_l3_mon_domain, hdr); m =get_mbm_state (d, closid, rmid, rr->evtid);if (WARN_ON_ONCE (!m))return ;
@@ -544,7 +544,7 @@ static struct rdt_ctrl_domain *get_ctrl_domain_from_cpu(int cpu,* throttle MSRs already have low percentage values. To avoid * unnecessarily restricting such rdtgroups, we also increase the bandwidth. */ -static void update_mba_bw (struct rdtgroup *rgrp,struct rdt_mon_domain *dom_mbm) +static void update_mba_bw (struct rdtgroup *rgrp,struct rdt_l3_mon_domain *dom_mbm) {u32 closid, rmid, cur_msr_val, new_msr_val;struct mbm_state *pmbm_data, *cmbm_data;
@@ -612,7 +612,7 @@ static void update_mba_bw(struct rdtgroup *rgrp, struct rdt_mon_domain *dom_mbm)resctrl_arch_update_one (r_mba, dom_mba, closid,CDP_NONE , new_msr_val); } -static void mbm_update_one_event (struct rdt_resource *r,struct rdt_mon_domain *d, +static void mbm_update_one_event (struct rdt_resource *r,struct rdt_l3_mon_domain *d,u32 closid,u32 rmid,enum resctrl_event_id evtid) {struct rmid_read rr = {0 };
@@ -639,7 +639,7 @@ static void mbm_update_one_event(struct rdt_resource *r, struct rdt_mon_domain *resctrl_arch_mon_ctx_free (rr.r, rr.evtid, rr.arch_mon_ctx); } -static void mbm_update (struct rdt_resource *r,struct rdt_mon_domain *d, +static void mbm_update (struct rdt_resource *r,struct rdt_l3_mon_domain *d,u32 closid,u32 rmid) {/*
@@ -660,12 +660,12 @@ static void mbm_update(struct rdt_resource *r, struct rdt_mon_domain *d,void cqm_handle_limbo (struct work_struct *work) {unsigned long delay =msecs_to_jiffies (CQM_LIMBOCHECK_INTERVAL ); -struct rdt_mon_domain *d; +struct rdt_l3_mon_domain *d;cpus_read_lock ();mutex_lock (&rdtgroup_mutex); - d = container_of(work, struct rdt_mon_domain, cqm_limbo.work); + d = container_of(work, struct rdt_l3_mon_domain, cqm_limbo.work);__check_limbo (d, false);
@@ -688,7 +688,7 @@ void cqm_handle_limbo(struct work_struct *work)* @exclude_cpu: Which CPU the handler should not run on, * RESCTRL_PICK_ANY_CPU to pick any CPU. */ -void cqm_setup_limbo_handler (struct rdt_mon_domain *dom,unsigned long delay_ms, +void cqm_setup_limbo_handler (struct rdt_l3_mon_domain *dom,unsigned long delay_ms,int exclude_cpu) {unsigned long delay =msecs_to_jiffies (delay_ms);
@@ -705,7 +705,7 @@ void mbm_handle_overflow(struct work_struct *work) {unsigned long delay =msecs_to_jiffies (MBM_OVERFLOW_INTERVAL );struct rdtgroup *prgrp, *crgrp; -struct rdt_mon_domain *d; +struct rdt_l3_mon_domain *d;struct list_head *head;struct rdt_resource *r;
@@ -720,7 +720,7 @@ void mbm_handle_overflow(struct work_struct *work) goto out_unlock; r =resctrl_arch_get_resource (RDT_RESOURCE_L3 ); - d = container_of(work, struct rdt_mon_domain, mbm_over.work); + d = container_of(work, struct rdt_l3_mon_domain, mbm_over.work);list_for_each_entry (prgrp, &rdt_all_groups, rdtgroup_list) {mbm_update (r, d, prgrp->closid, prgrp->mon.rmid);
@@ -754,7 +754,7 @@ void mbm_handle_overflow(struct work_struct *work)* @exclude_cpu: Which CPU the handler should not run on, * RESCTRL_PICK_ANY_CPU to pick any CPU. */ -void mbm_setup_overflow_handler (struct rdt_mon_domain *dom,unsigned long delay_ms, +void mbm_setup_overflow_handler (struct rdt_l3_mon_domain *dom,unsigned long delay_ms,int exclude_cpu) {unsigned long delay =msecs_to_jiffies (delay_ms);
fs/resctrl/rdtgroup.c +18 -18
@@ -1617,7 +1617,7 @@ static void mondata_config_read(struct resctrl_mon_config_info *mon_info)static int mbm_config_show (struct seq_file *s,struct rdt_resource *r,u32 evtid) {struct resctrl_mon_config_info mon_info; -struct rdt_mon_domain *dom; +struct rdt_l3_mon_domain *dom;bool sep = false;cpus_read_lock ();
@@ -1665,7 +1665,7 @@ static int mbm_local_bytes_config_show(struct kernfs_open_file *of, }static void mbm_config_write_domain (struct rdt_resource *r, -struct rdt_mon_domain *d,u32 evtid,u32 val) +struct rdt_l3_mon_domain *d,u32 evtid,u32 val) {struct resctrl_mon_config_info mon_info = {0 };
@@ -1706,8 +1706,8 @@ static void mbm_config_write_domain(struct rdt_resource *r,static int mon_config_write (struct rdt_resource *r,char *tok,u32 evtid) {char *dom_str =NULL , *id_str; +struct rdt_l3_mon_domain *d;unsigned long dom_id, val; -struct rdt_mon_domain *d;/* Walking r->domains, ensure it can't race with cpuhp */ lockdep_assert_cpus_held ();
@@ -2581,7 +2581,7 @@ static int rdt_get_tree(struct fs_context *fc) {struct rdt_fs_context *ctx =rdt_fc2context (fc);unsigned long flags =RFTYPE_CTRL_BASE ; -struct rdt_mon_domain *dom; +struct rdt_l3_mon_domain *dom;struct rdt_resource *r;int ret;
@@ -3036,11 +3036,11 @@ static void rmdir_mondata_subdir_allrdtgrp(struct rdt_resource *r,char name[32 ];if (r->rid ==RDT_RESOURCE_L3 ) { -struct rdt_mon_domain *d; +struct rdt_l3_mon_domain *d;if (!domain_header_is_valid (hdr,RESCTRL_MON_DOMAIN ,RDT_RESOURCE_L3 ))return ; - d = container_of(hdr, struct rdt_mon_domain, hdr); + d = container_of(hdr, struct rdt_l3_mon_domain, hdr);/* SNC mode? */ if (r->mon_scope ==RESCTRL_L3_NODE ) {
@@ -3100,11 +3100,11 @@ static int mkdir_mondata_subdir(struct kernfs_node *parent_kn,if (r->rid ==RDT_RESOURCE_L3 ) { snc_mode = r->mon_scope ==RESCTRL_L3_NODE ;if (snc_mode) { -struct rdt_mon_domain *d; +struct rdt_l3_mon_domain *d;if (!domain_header_is_valid (hdr,RESCTRL_MON_DOMAIN ,RDT_RESOURCE_L3 ))return -EINVAL ; - d = container_of(hdr, struct rdt_mon_domain, hdr); + d = container_of(hdr, struct rdt_l3_mon_domain, hdr); domid = d->ci_id; } }
@@ -4040,7 +4040,7 @@ static void rdtgroup_setup_default(void)mutex_unlock (&rdtgroup_mutex); } -static void domain_destroy_mon_state (struct rdt_mon_domain *d) +static void domain_destroy_mon_state (struct rdt_l3_mon_domain *d) {int idx;
@@ -4063,7 +4063,7 @@ void resctrl_offline_ctrl_domain(struct rdt_resource *r, struct rdt_ctrl_domainvoid resctrl_offline_mon_domain (struct rdt_resource *r,struct rdt_domain_hdr *hdr) { -struct rdt_mon_domain *d; +struct rdt_l3_mon_domain *d;mutex_lock (&rdtgroup_mutex);
@@ -4080,7 +4080,7 @@ void resctrl_offline_mon_domain(struct rdt_resource *r, struct rdt_domain_hdr *hif (!domain_header_is_valid (hdr,RESCTRL_MON_DOMAIN ,RDT_RESOURCE_L3 )) goto out_unlock; - d = container_of(hdr, struct rdt_mon_domain, hdr); + d = container_of(hdr, struct rdt_l3_mon_domain, hdr);if (resctrl_is_mbm_enabled ())cancel_delayed_work (&d->mbm_over);if (resctrl_is_mon_event_enabled (QOS_L3_OCCUP_EVENT_ID ) &&has_busy_rmid (d)) {
@@ -4114,7 +4114,7 @@ void resctrl_offline_mon_domain(struct rdt_resource *r, struct rdt_domain_hdr *h* * Returns 0 for success, or -ENOMEM. */ -static int domain_setup_mon_state (struct rdt_resource *r,struct rdt_mon_domain *d) +static int domain_setup_mon_state (struct rdt_resource *r,struct rdt_l3_mon_domain *d) {u32 idx_limit =resctrl_arch_system_num_rmid_idx ();size_t tsize =sizeof (*d->mbm_states[0 ]);
@@ -4165,7 +4165,7 @@ int resctrl_online_ctrl_domain(struct rdt_resource *r, struct rdt_ctrl_domain *dint resctrl_online_mon_domain (struct rdt_resource *r,struct rdt_domain_hdr *hdr) { -struct rdt_mon_domain *d; +struct rdt_l3_mon_domain *d;int err = -EINVAL ;mutex_lock (&rdtgroup_mutex);
@@ -4176,7 +4176,7 @@ int resctrl_online_mon_domain(struct rdt_resource *r, struct rdt_domain_hdr *hdrif (!domain_header_is_valid (hdr,RESCTRL_MON_DOMAIN ,RDT_RESOURCE_L3 )) goto out_unlock; - d = container_of(hdr, struct rdt_mon_domain, hdr); + d = container_of(hdr, struct rdt_l3_mon_domain, hdr); err =domain_setup_mon_state (r, d);if (err) goto out_unlock;
@@ -4225,10 +4225,10 @@ static void clear_childcpus(struct rdtgroup *r, unsigned int cpu) } } -static struct rdt_mon_domain *get_mon_domain_from_cpu (int cpu, -struct rdt_resource *r) +static struct rdt_l3_mon_domain *get_mon_domain_from_cpu (int cpu, +struct rdt_resource *r) { -struct rdt_mon_domain *d; +struct rdt_l3_mon_domain *d;lockdep_assert_cpus_held ();
@@ -4244,7 +4244,7 @@ static struct rdt_mon_domain *get_mon_domain_from_cpu(int cpu,void resctrl_offline_cpu (unsigned int cpu) {struct rdt_resource *l3 =resctrl_arch_get_resource (RDT_RESOURCE_L3 ); -struct rdt_mon_domain *d; +struct rdt_l3_mon_domain *d;struct rdtgroup *rdtgrp;mutex_lock (&rdtgroup_mutex);
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 10/32] x86,fs/resctrl: Rename struct rdt_mon_domain and rdt_hw_mon_domain
Hi Tony,
Quoted 1 line · Tony Luck
All monitoring events are associated with the L3 resource.
With a bit more context:
All monitoring events are associated with the L3 resource. The per L3 domain resctrl fs monitoring state is maintained in the generically named struct rdt_mon_domain while the per L3 domain architecture specific monitoring state is maintained in the generically named struct rdt_hw_mon_domain.
Quoted 2 lines
This will change when support for telemetry events is added.
Upcoming telemetry event monitoring will be tied to another resource and requires new domain structures.
Quoted 4 lines
The structures to track monitor domains of the L3 resource at both the file system and architecture level have generic names. This may cause confusion when support for monitoring events in other resources is added.
Rename the L3 resource specific domain data structures to include "l3_" in their names to avoid confusion between the different resource specific domain structures:
rdt_mon_domain -> rdt_l3_mon_domain
rdt_hw_mon_domain -> rdt_hw_l3_mon_domain
Quoted 9 lines
Rename by adding "
l3_" into the names:rdt_mon_domain->rdt_l3_mon_domainrdt_hw_mon_domain->rdt_hw_l3_mon_domainNo functional change.
Signed-off-by Tony Luck <[email protected]>---
Running "git grep rdt_mon_domain" with this series applied found one more spot
that needs to switch:arch/x86/kernel/cpu/resctrl/monitor.c: * nodes that share an L3 cache). Linux creates an rdt_mon_domain for
Reinette
Tony Luck
maintainerPATCH v8 11/32 x86,fs/resctrl: Rename some L3 specific functions
In reply to Tony LuckAll monitor functions are tied to the RDT_RESOURCE_L3 resource, so generic function names to setup and tear down domains makes sense.
With the arrival of monitor events tied to new domains associated with different resources it would be clearer if these functions are more accurately named.
Two groups of functions renamed here:
Functions that allocate/free architecture per-RMID MBM state information:arch_domain_mbm_alloc() -> l3_mon_domain_mbm_alloc()mon_domain_free() -> l3_mon_domain_free()
Functions that allocate/free filesystem per-RMID MBM state information:domain_setup_mon_state() -> domain_setup_l3_mon_state()domain_destroy_mon_state() -> domain_destroy_l3_mon_state()
Initialization/exit:resctrl_mon_resource_init -> resctrl_mon_l3_resource_init()resctrl_mon_resource_exit() -> resctrl_mon_l3_resource_exit()
--- fs/resctrl/internal.h | 6 +++--- arch/x86/kernel/cpu/resctrl/core.c | 16 ++++++++-------- fs/resctrl/monitor.c | 6 +++--- fs/resctrl/rdtgroup.c | 22 +++++++++++----------- 4 files changed, 25 insertions(+), 25 deletions(-)
fs/resctrl/internal.h +3 -3
@@ -345,7 +345,9 @@ int alloc_rmid(u32 closid);void free_rmid (u32 closid,u32 rmid); -void resctrl_mon_resource_exit (void ); +int resctrl_mon_l3_resource_init (void ); + +void resctrl_mon_l3_resource_exit (void );void mon_event_count (void *info);
@@ -355,8 +357,6 @@ void mon_event_read(struct rmid_read *rr, struct rdt_resource *r, struct rdt_domain_hdr *hdr, struct rdtgroup *rdtgrp, cpumask_t *cpumask, int evtid, int first); -int resctrl_mon_resource_init (void ); -void mbm_setup_overflow_handler (struct rdt_l3_mon_domain *dom,unsigned long delay_ms,int exclude_cpu);
arch/x86/kernel/cpu/resctrl/core.c +8 -8
@@ -363,7 +363,7 @@ static void ctrl_domain_free(struct rdt_hw_ctrl_domain *hw_dom)kfree (hw_dom); } -static void mon_domain_free (struct rdt_hw_l3_mon_domain *hw_dom) +static void l3_mon_domain_free (struct rdt_hw_l3_mon_domain *hw_dom) {int idx;
@@ -396,11 +396,11 @@ static int domain_setup_ctrlval(struct rdt_resource *r, struct rdt_ctrl_domain * }/** -* arch_domain_mbm_alloc() - Allocate arch private storage for the MBM counters +* l3_mon_domain_mbm_alloc() - Allocate arch private storage for the MBM counters * @num_rmid: The size of the MBM counter array * @hw_dom: The domain that owns the allocated arrays */ -static int arch_domain_mbm_alloc (u32 num_rmid,struct rdt_hw_l3_mon_domain *hw_dom) +static int l3_mon_domain_mbm_alloc (u32 num_rmid,struct rdt_hw_l3_mon_domain *hw_dom) {size_t tsize =sizeof (*hw_dom->arch_mbm_states[0 ]);enum resctrl_event_id eventid;
@@ -514,7 +514,7 @@ static void l3_mon_domain_setup(int cpu, int id, struct rdt_resource *r, struct ci =get_cpu_cacheinfo_level (cpu,RESCTRL_L3_CACHE );if (!ci) {pr_warn_once ("Can't find L3 cache for CPU:%d resource %s\n" , cpu, r->name); -mon_domain_free (hw_dom); +l3_mon_domain_free (hw_dom);return ; } d->ci_id = ci->id;
@@ -522,8 +522,8 @@ static void l3_mon_domain_setup(int cpu, int id, struct rdt_resource *r, structarch_mon_domain_online (r, d); -if (arch_domain_mbm_alloc (r->num_rmid, hw_dom)) { -mon_domain_free (hw_dom); +if (l3_mon_domain_mbm_alloc (r->num_rmid, hw_dom)) { +l3_mon_domain_free (hw_dom);return ; }
@@ -533,7 +533,7 @@ static void l3_mon_domain_setup(int cpu, int id, struct rdt_resource *r, structif (err) {list_del_rcu (&d->hdr.list);synchronize_rcu (); -mon_domain_free (hw_dom); +l3_mon_domain_free (hw_dom); } }
@@ -659,7 +659,7 @@ static void domain_remove_cpu_mon(int cpu, struct rdt_resource *r)resctrl_offline_mon_domain (r, hdr);list_del_rcu (&d->hdr.list);synchronize_rcu (); -mon_domain_free (hw_dom); +l3_mon_domain_free (hw_dom);break ;default :pr_warn_once ("Unknown resource rid=%d\n" , r->rid);
fs/resctrl/monitor.c +3 -3
@@ -895,7 +895,7 @@ bool resctrl_is_mon_event_enabled(enum resctrl_event_id eventid) }/** -* resctrl_mon_resource_init() - Initialise global monitoring structures. +* resctrl_mon_l3_resource_init() - Initialise global monitoring structures. * * Allocate and initialise global monitor resources that do not belong to a * specific domain. i.e. the rmid_ptrs[] used for the limbo and free lists.
@@ -906,7 +906,7 @@ bool resctrl_is_mon_event_enabled(enum resctrl_event_id eventid)* * Returns 0 for success, or -ENOMEM. */ -int resctrl_mon_resource_init (void ) +int resctrl_mon_l3_resource_init (void ) {struct rdt_resource *r =resctrl_arch_get_resource (RDT_RESOURCE_L3 );int ret;
@@ -937,7 +937,7 @@ int resctrl_mon_resource_init(void)return 0 ; } -void resctrl_mon_resource_exit (void ) +void resctrl_mon_l3_resource_exit (void ) {struct rdt_resource *r =resctrl_arch_get_resource (RDT_RESOURCE_L3 );
fs/resctrl/rdtgroup.c +11 -11
@@ -4040,7 +4040,7 @@ static void rdtgroup_setup_default(void)mutex_unlock (&rdtgroup_mutex); } -static void domain_destroy_mon_state (struct rdt_l3_mon_domain *d) +static void domain_destroy_l3_mon_state (struct rdt_l3_mon_domain *d) {int idx;
@@ -4096,13 +4096,13 @@ void resctrl_offline_mon_domain(struct rdt_resource *r, struct rdt_domain_hdr *hcancel_delayed_work (&d->cqm_limbo); } -domain_destroy_mon_state (d); +domain_destroy_l3_mon_state (d); out_unlock:mutex_unlock (&rdtgroup_mutex); }/** -* domain_setup_mon_state() - Initialise domain monitoring structures. +* domain_setup_l3_mon_state() - Initialise domain monitoring structures. * @r: The resource for the newly online domain. * @d: The newly online domain. *
@@ -4110,11 +4110,11 @@ void resctrl_offline_mon_domain(struct rdt_resource *r, struct rdt_domain_hdr *h* Called when the first CPU of a domain comes online, regardless of whether * the filesystem is mounted. * During boot this may be called before global allocations have been made by -* resctrl_mon_resource_init(). +* resctrl_mon_l3_resource_init(). * * Returns 0 for success, or -ENOMEM. */ -static int domain_setup_mon_state (struct rdt_resource *r,struct rdt_l3_mon_domain *d) +static int domain_setup_l3_mon_state (struct rdt_resource *r,struct rdt_l3_mon_domain *d) {u32 idx_limit =resctrl_arch_system_num_rmid_idx ();size_t tsize =sizeof (*d->mbm_states[0 ]);
@@ -4177,7 +4177,7 @@ int resctrl_online_mon_domain(struct rdt_resource *r, struct rdt_domain_hdr *hdr goto out_unlock; d = container_of(hdr, struct rdt_l3_mon_domain, hdr); - err =domain_setup_mon_state (r, d); + err =domain_setup_l3_mon_state (r, d);if (err) goto out_unlock;
@@ -4294,13 +4294,13 @@ int resctrl_init(void)thread_throttle_mode_init (); - ret =resctrl_mon_resource_init (); + ret =resctrl_mon_l3_resource_init ();if (ret)return ret; ret =sysfs_create_mount_point (fs_kobj,"resctrl" );if (ret) { -resctrl_mon_resource_exit (); +resctrl_mon_l3_resource_exit ();return ret; }
@@ -4335,7 +4335,7 @@ int resctrl_init(void) cleanup_mountpoint:sysfs_remove_mount_point (fs_kobj,"resctrl" ); -resctrl_mon_resource_exit (); +resctrl_mon_l3_resource_exit ();return ret; }
@@ -4371,7 +4371,7 @@ static bool resctrl_online_domains_exist(void)* When called by the architecture code, all CPUs and resctrl domains must be * offline. This ensures the limbo and overflow handlers are not scheduled to * run, meaning the data structures they access can be freed by -* resctrl_mon_resource_exit(). +* resctrl_mon_l3_resource_exit(). * * After resctrl_exit() returns, the architecture code should return an * error from all resctrl_arch_ functions that can do this.
@@ -4398,5 +4398,5 @@ void resctrl_exit(void)* it can be used to umount resctrl. */ -resctrl_mon_resource_exit (); +resctrl_mon_l3_resource_exit (); }
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 11/32] x86,fs/resctrl: Rename some L3 specific functions
Hi Tony,
Quoted 5 lines · Tony Luck
All monitor functions are tied to the
RDT_RESOURCE_L3resource, so generic function names to setup and tear down domains makes sense.With the arrival of monitor events tied to new domains associated with different resources it would be clearer if these functions are more
"different resources" -> "a different resource"? "these functions" -> "the L3 resource specific functions"
Quoted 3 lines
accurately named.
Two groups of functions renamed here:
"Rename three groups of functions:"
(correct the number and make imperative)
Quoted 11 lines
Functions that allocate/free architecture per-RMID MBM state information:
arch_domain_mbm_alloc()->l3_mon_domain_mbm_alloc()mon_domain_free()->l3_mon_domain_free()Functions that allocate/free filesystem per-RMID MBM state information:
domain_setup_mon_state()->domain_setup_l3_mon_state()domain_destroy_mon_state()->domain_destroy_l3_mon_state()Initialization/exit:
resctrl_mon_resource_init->resctrl_mon_l3_resource_init()
"resctrl_mon_resource_init" -> "resctrl_mon_resource_init()"
Up to here the renaming was consistent ... the previous patches renamed the structs to have "l3_mon" and the functions up to here changed to have "l3_mon" ... and then these last two switched it up to be "mon_l3" instead. Having a consistent term makes code easier to search and follow, could these also use "l3_mon"?
Quoted 4 lines
resctrl_mon_resource_exit()->resctrl_mon_l3_resource_exit()Signed-off-by Tony Luck <[email protected]>---
Reinette
Tony Luck
maintainerPATCH v8 12/32 fs/resctrl: Make event details accessible to functions when reading events
In reply to Tony LuckAll details about a monitor event are kept in the mon_evt structure.
Upper levels of code only provide the event id to lower levels.
But those lower levels need more than just the event id, they need the attributes of the event too.
Change the mon_data and rmid_read structures to hold a pointer to the mon_evt structure instead of just taking a copy of the event id.
No functional change.
--- fs/resctrl/internal.h | 10 +++++----- fs/resctrl/ctrlmondata.c | 16 ++++++++-------- fs/resctrl/monitor.c | 17 +++++++++-------- fs/resctrl/rdtgroup.c | 6 +++--- 4 files changed, 25 insertions(+), 24 deletions(-)
fs/resctrl/internal.h +5 -5
@@ -76,7 +76,7 @@ extern struct mon_evt mon_event_all[QOS_NUM_EVENTS];* struct mon_data - Monitoring details for each event file. * @list: Member of the global @mon_data_kn_priv_list list. * @rid: Resource id associated with the event file. -* @evtid: Event id associated with the event file. +* @evt: Event structure associated with the event file. * @sum: Set for RDT_RESOURCE_L3 when event must be summed * across multiple domains. * @domid: When @sum is zero this is the domain to which
@@ -90,7 +90,7 @@ extern struct mon_evt mon_event_all[QOS_NUM_EVENTS];struct mon_data {struct list_head list;enum resctrl_res_level rid; -enum resctrl_event_id evtid; +struct mon_evt *evt;int domid;bool sum; };
@@ -103,7 +103,7 @@ struct mon_data {* @r: Resource describing the properties of the event being read. * @hdr: Header of domain that the counter should be read from. If NULL then sum all * domains in @r sharing L3 @ci.id -* @evtid: Which monitor event to read. +* @evt: Which monitor event to read. * @first: Initialize MBM counter when true. * @ci_id: Cacheinfo id for L3. Only set when @hdr is NULL. Used when summing domains. * @err: Error encountered when reading counter.
@@ -117,7 +117,7 @@ struct rmid_read {struct rdtgroup *rgrp;struct rdt_resource *r;struct rdt_domain_hdr *hdr; -enum resctrl_event_id evtid; +struct mon_evt *evt;bool first;unsigned int ci_id;int err;
@@ -355,7 +355,7 @@ int rdtgroup_mondata_show(struct seq_file *m, void *arg);void mon_event_read (struct rmid_read *rr,struct rdt_resource *r,struct rdt_domain_hdr *hdr,struct rdtgroup *rdtgrp, -cpumask_t *cpumask,int evtid,int first); +cpumask_t *cpumask,struct mon_evt *evt,int first); void mbm_setup_overflow_handler(struct rdt_l3_mon_domain *dom, unsigned long delay_ms,
fs/resctrl/ctrlmondata.c +8 -8
@@ -548,7 +548,7 @@ struct rdt_domain_hdr *resctrl_find_domain(struct list_head *h, int id,void mon_event_read (struct rmid_read *rr,struct rdt_resource *r,struct rdt_domain_hdr *hdr,struct rdtgroup *rdtgrp, -cpumask_t *cpumask,int evtid,int first) +cpumask_t *cpumask,struct mon_evt *evt,int first) {int cpu;
@@ -559,11 +559,11 @@ void mon_event_read(struct rmid_read *rr, struct rdt_resource *r,* Setup the parameters to pass to mon_event_count() to read the data. */ rr->rgrp = rdtgrp; - rr->evtid = evtid; + rr->evt = evt; rr->r = r; rr->hdr = hdr; rr->first = first; - rr->arch_mon_ctx =resctrl_arch_mon_ctx_alloc (r, evtid); + rr->arch_mon_ctx =resctrl_arch_mon_ctx_alloc (r, evt->evtid);if (IS_ERR (rr->arch_mon_ctx)) { rr->err = -EINVAL ;return ;
@@ -582,20 +582,20 @@ void mon_event_read(struct rmid_read *rr, struct rdt_resource *r,else smp_call_on_cpu (cpu, smp_mon_event_count, rr, false); -resctrl_arch_mon_ctx_free (r, evtid, rr->arch_mon_ctx); +resctrl_arch_mon_ctx_free (r, evt->evtid, rr->arch_mon_ctx); }int rdtgroup_mondata_show (struct seq_file *m,void *arg) {struct kernfs_open_file *of = m->private;enum resctrl_res_level resid; -enum resctrl_event_id evtid;struct rdt_domain_hdr *hdr;struct rmid_read rr = {0 };struct rdtgroup *rdtgrp;int domid, cpu, ret =0 ;struct rdt_resource *r;struct cacheinfo *ci; +struct mon_evt *evt;struct mon_data *md; rdtgrp =rdtgroup_kn_lock_live (of->kn);
@@ -612,7 +612,7 @@ int rdtgroup_mondata_show(struct seq_file *m, void *arg) resid = md->rid; domid = md->domid; - evtid = md->evtid; + evt = md->evt; r =resctrl_arch_get_resource (resid);if (md->sum) {
@@ -636,7 +636,7 @@ int rdtgroup_mondata_show(struct seq_file *m, void *arg)if (!ci)continue ;mon_event_read (&rr, r,NULL , rdtgrp, - &ci->shared_cpu_map, evtid, false); + &ci->shared_cpu_map, evt, false); goto checkresult; } }
@@ -652,7 +652,7 @@ int rdtgroup_mondata_show(struct seq_file *m, void *arg) ret = -ENOENT ; goto out; } -mon_event_read (&rr, r, hdr, rdtgrp, &hdr->cpu_mask, evtid, false); +mon_event_read (&rr, r, hdr, rdtgrp, &hdr->cpu_mask, evt, false); } checkresult:
fs/resctrl/monitor.c +9 -8
@@ -369,8 +369,8 @@ static int __mon_event_count(u32 closid, u32 rmid, struct rmid_read *rr)if (!domain_header_is_valid (rr->hdr,RESCTRL_MON_DOMAIN ,RDT_RESOURCE_L3 ))return -EINVAL ; d = container_of(rr->hdr, struct rdt_l3_mon_domain, hdr); -resctrl_arch_reset_rmid (rr->r, d, closid, rmid, rr->evtid); - m =get_mbm_state (d, closid, rmid, rr->evtid); +resctrl_arch_reset_rmid (rr->r, d, closid, rmid, rr->evt->evtid); + m =get_mbm_state (d, closid, rmid, rr->evt->evtid);if (m)memset (m,0 ,sizeof (struct mbm_state ));return 0 ;
@@ -381,7 +381,7 @@ static int __mon_event_count(u32 closid, u32 rmid, struct rmid_read *rr)if (!cpumask_test_cpu (cpu, &rr->hdr->cpu_mask))return -EINVAL ; rr->err =resctrl_arch_rmid_read (rr->r, rr->hdr, closid, rmid, - rr->evtid, &tval, rr->arch_mon_ctx); + rr->evt->evtid, &tval, rr->arch_mon_ctx);if (rr->err)return rr->err;
@@ -410,7 +410,7 @@ static int __mon_event_count(u32 closid, u32 rmid, struct rmid_read *rr)if (d->ci_id != rr->ci_id)continue ; err =resctrl_arch_rmid_read (rr->r, &d->hdr, closid, rmid, - rr->evtid, &tval, rr->arch_mon_ctx); + rr->evt->evtid, &tval, rr->arch_mon_ctx);if (!err) { rr->val += tval; ret =0 ;
@@ -444,7 +444,7 @@ static void mbm_bw_count(u32 closid, u32 rmid, struct rmid_read *rr)if (!domain_header_is_valid (rr->hdr,RESCTRL_MON_DOMAIN ,RDT_RESOURCE_L3 ))return ; d = container_of(rr->hdr, struct rdt_l3_mon_domain, hdr); - m =get_mbm_state (d, closid, rmid, rr->evtid); + m =get_mbm_state (d, closid, rmid, rr->evt->evtid);if (WARN_ON_ONCE (!m))return ;
@@ -615,12 +615,13 @@ static void update_mba_bw(struct rdtgroup *rgrp, struct rdt_l3_mon_domain *dom_mstatic void mbm_update_one_event (struct rdt_resource *r,struct rdt_l3_mon_domain *d,u32 closid,u32 rmid,enum resctrl_event_id evtid) { +struct mon_evt *evt = &mon_event_all[evtid];struct rmid_read rr = {0 }; rr.r = r; rr.hdr = &d->hdr; - rr.evtid = evtid; - rr.arch_mon_ctx =resctrl_arch_mon_ctx_alloc (rr.r, rr.evtid); + rr.evt = evt; + rr.arch_mon_ctx =resctrl_arch_mon_ctx_alloc (rr.r, evt->evtid);if (IS_ERR (rr.arch_mon_ctx)) {pr_warn_ratelimited ("Failed to allocate monitor context: %ld" ,PTR_ERR (rr.arch_mon_ctx));
@@ -636,7 +637,7 @@ static void mbm_update_one_event(struct rdt_resource *r, struct rdt_l3_mon_domaiif (is_mba_sc (NULL ))mbm_bw_count (closid, rmid, &rr); -resctrl_arch_mon_ctx_free (rr.r, rr.evtid, rr.arch_mon_ctx); +resctrl_arch_mon_ctx_free (rr.r, evt->evtid, rr.arch_mon_ctx); } static void mbm_update(struct rdt_resource *r, struct rdt_l3_mon_domain *d,
fs/resctrl/rdtgroup.c +3 -3
@@ -2903,7 +2903,7 @@ static struct mon_data *mon_get_kn_priv(enum resctrl_res_level rid, int domid,list_for_each_entry (priv, &mon_data_kn_priv_list, list) {if (priv->rid == rid && priv->domid == domid && - priv->sum == do_sum && priv->evtid == mevt->evtid) + priv->sum == do_sum && priv->evt == mevt)return priv; }
@@ -2914,7 +2914,7 @@ static struct mon_data *mon_get_kn_priv(enum resctrl_res_level rid, int domid, priv->rid = rid; priv->domid = domid; priv->sum = do_sum; - priv->evtid = mevt->evtid; + priv->evt = mevt;list_add_tail (&priv->list, &mon_data_kn_priv_list);return priv;
@@ -3079,7 +3079,7 @@ static int mon_add_all_files(struct kernfs_node *kn, struct rdt_domain_hdr *hdr,return ret;if (r->rid ==RDT_RESOURCE_L3 && !do_sum &&resctrl_is_mbm_event (mevt->evtid)) -mon_event_read (&rr, r, hdr, prgrp, &hdr->cpu_mask, mevt->evtid, true); +mon_event_read (&rr, r, hdr, prgrp, &hdr->cpu_mask, mevt, true); }return 0 ;
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 12/32] fs/resctrl: Make event details accessible to functions when reading events
Hi Tony,
Quoted 3 lines · Tony Luck
All details about a monitor event are kept in the
mon_evtstructure.Upper levels of code only provide the event id to lower levels.
"to lower levels" -> "via the mon_data and rmid_read structures to the functions finally reading the monitoring data."
Quoted 3 lines
But those lower levels need more than just the event id, they need the attributes of the event too.
This motivation is weak. If those "lower levels" needed more than what they have now then existing code will be broken, no? This change is thus in support of a new requirements and "this is needed" is not a valid motivation.
Consider something like:
The event id is sufficient for reading existing monitoring event data that requires programming of event id into MSR when reading the counter. Reading monitoring data from MMIO requires more context to be able to read the correct memory. struct mon_evt is the appropriate place for this event specific context.
Quoted 9 lines
Change the
mon_dataandrmid_readstructures to hold a pointer to themon_evtstructure instead of just taking a copy of the event id.No functional change.
Signed-off-by Tony Luck <[email protected]>---
Reinette
Tony Luck
maintainerPATCH v8 13/32 x86,fs/resctrl: Handle events that can be read from any CPU
In reply to Tony Luckresctrl assumes that monitor events can only be read from a CPU in the cpumask_t set of each domain.
This is true for x86 events accessed with an MSR interface, but may not be true for other access methods such as MMIO.
Add a flag to struct mon_evt to indicate if the event can be read on any CPU.
Architecture uses resctrl_enable_mon_event() to enable an event and set the flag appropriately.
Bypass all the smp_call*() code for events that can be read on any CPU and call mon_event_count() directly from mon_event_read().
Add a test for events that can be read from any domain to skip checks in __mon_event_count() that the read is being done from a CPU in the correct domain or cache scope.
--- include/linux/resctrl.h | 2 +- fs/resctrl/internal.h | 2 ++ arch/x86/kernel/cpu/resctrl/core.c | 6 ++-- fs/resctrl/ctrlmondata.c | 7 +++- fs/resctrl/monitor.c | 53 ++++++++++++++++++++++-------- 5 files changed, 51 insertions(+), 19 deletions(-)
include/linux/resctrl.h +1 -1
@@ -379,7 +379,7 @@ u32 resctrl_arch_get_num_closid(struct rdt_resource *r);u32 resctrl_arch_system_num_rmid_idx (void );int resctrl_arch_update_domains (struct rdt_resource *r,u32 closid); -void resctrl_enable_mon_event (enum resctrl_event_id eventid); +void resctrl_enable_mon_event (enum resctrl_event_id eventid,bool any_cpu);bool resctrl_is_mon_event_enabled (enum resctrl_event_id eventid);
fs/resctrl/internal.h +2 -0
@@ -57,6 +57,7 @@ static inline struct rdt_fs_context *rdt_fc2context(struct fs_context *fc)* @rid: resource id for this event * @name: name of the event * @configurable: true if the event is configurable +* @any_cpu: true if the event can be read from any CPU * @enabled: true if the event is enabled */ struct mon_evt {
@@ -64,6 +65,7 @@ struct mon_evt {enum resctrl_res_level rid;char *name;bool configurable; +bool any_cpu;bool enabled; };
arch/x86/kernel/cpu/resctrl/core.c +3 -3
@@ -888,15 +888,15 @@ static __init bool get_rdt_mon_resources(void)bool ret = false;if (rdt_cpu_has (X86_FEATURE_CQM_OCCUP_LLC )) { -resctrl_enable_mon_event (QOS_L3_OCCUP_EVENT_ID ); +resctrl_enable_mon_event (QOS_L3_OCCUP_EVENT_ID , false); ret = true; }if (rdt_cpu_has (X86_FEATURE_CQM_MBM_TOTAL )) { -resctrl_enable_mon_event (QOS_L3_MBM_TOTAL_EVENT_ID ); +resctrl_enable_mon_event (QOS_L3_MBM_TOTAL_EVENT_ID , false); ret = true; }if (rdt_cpu_has (X86_FEATURE_CQM_MBM_LOCAL )) { -resctrl_enable_mon_event (QOS_L3_MBM_LOCAL_EVENT_ID ); +resctrl_enable_mon_event (QOS_L3_MBM_LOCAL_EVENT_ID , false); ret = true; }
fs/resctrl/ctrlmondata.c +6 -1
@@ -569,6 +569,11 @@ void mon_event_read(struct rmid_read *rr, struct rdt_resource *r,return ; } +if (evt->any_cpu) { +mon_event_count (rr); + goto out_ctx_free; + } + cpu =cpumask_any_housekeeping (cpumask,RESCTRL_PICK_ANY_CPU );/*
@@ -581,7 +586,7 @@ void mon_event_read(struct rmid_read *rr, struct rdt_resource *r,smp_call_function_any (cpumask, mon_event_count, rr,1 ); elsesmp_call_on_cpu (cpu ,smp_mon_event_count ,rr ,false ); - +out_ctx_free:resctrl_arch_mon_ctx_free (r, evt->evtid, rr->arch_mon_ctx); }
fs/resctrl/monitor.c +39 -14
91 lines not on this page · raw message
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 13/32] x86,fs/resctrl: Handle events that can be read from any CPU
Hi Tony,
On 8/11/25 11:16 AM, Tony Luck wrote:
...
Quoted 6 lines
fs/resctrl/monitor.c +0
-0@@ -356,15 +356,47 @@ static struct mbm_state *get_mbm_state(struct rdt_l3_mon_domain *d, u32 closid,return state ? &state[idx] :NULL ;
fs/resctrl/monitor.c static struct mbm_state *get_mbm_state(struct rdt_l3_mon_domain *d, u32 closid, · line 366
Quoted 10 lines
fs/resctrl/monitor.c +8
-0} +/* +* Called from preemptible context via a direct call of mon_event_count() for +* events that can be read on any CPU. +* Called from preemptible but non-migratable process context (mon_event_count() +* via smp_call_on_cpu()) OR non-preemptible context (mon_event_count() via +* smp_call_function_any()) for events that need to be read on a specific CPU. +*/ +static bool cpu_on_correct_domain (struct rmid_read *rr)
Function returns bool ...
Quoted 6 lines
fs/resctrl/monitor.c +6
-0+{ +struct cacheinfo *ci; +int cpu; + +/* Any CPU is OK for this event */ +if (rr->evt->any_cpu)
fs/resctrl/monitor.c static struct mbm_state *get_mbm_state(struct rdt_l3_mon_domain *d, u32 closid, · line 382
Quoted 10 lines
fs/resctrl/monitor.c +10
-0+return true; + + cpu =smp_processor_id (); + +/* Single domain. Must be on a CPU in that domain. */ +if (rr->hdr) +return cpumask_test_cpu (cpu, &rr->hdr->cpu_mask); + +if (WARN_ON_ONCE (rr->r->rid !=RDT_RESOURCE_L3 )) +return -EINVAL ;
return false?
fs/resctrl/monitor.c static struct mbm_state *get_mbm_state(struct rdt_l3_mon_domain *d, u32 closid, · line 389
Quoted 7 lines
fs/resctrl/monitor.c +7
-0+ +/* Summing domains that share a cache, must be on a CPU for that cache. */ + ci =get_cpu_cacheinfo_level (cpu,RESCTRL_L3_CACHE ); + +return ci && ci->id == rr->ci_id; +} +
Reinette
Tony Luck
maintainerPATCH v8 14/32 x86,fs/resctrl: Support binary fixed point event counters
In reply to Tony Luckresctrl assumes that all monitor events can be displayed as unsigned decimal integers.
Hardware architecture counters may provide some telemetry events with greater precision where the event is not a simple count, but is a measurement of some sort (e.g. Joules for energy consumed).
Add a new argument to resctrl_enable_mon_event() for architecture code to inform the file system that the value for a counter is a fixed-point value with a specific number of binary places.
Only allow architecture to use floating point format on events that it marked with mon_evt::is_floating_point.
Display fixed point values with values rounded to an appropriate number of decimal places for the precision of the number of binary places provided. Add one extra decimal place for every three additional binary places, except for low precision binary values where exact representation is possible:
1 binary place is 0.0 or 0.5. => 1 decimal place
2 binary places is 0.0, 0.25, 0.5, 0.75 => 2 decimal places
3 binary places is 0.0, 0.125, etc. => 3 decimal places
--- include/linux/resctrl.h | 5 +- fs/resctrl/internal.h | 5 ++ arch/x86/kernel/cpu/resctrl/core.c | 6 +-- fs/resctrl/ctrlmondata.c | 84 ++++++++++++++++++++++++++++++ fs/resctrl/monitor.c | 10 +++- 5 files changed, 104 insertions(+), 6 deletions(-)
include/linux/resctrl.h +4 -1
@@ -379,7 +379,10 @@ u32 resctrl_arch_get_num_closid(struct rdt_resource *r);u32 resctrl_arch_system_num_rmid_idx (void );int resctrl_arch_update_domains (struct rdt_resource *r,u32 closid); -void resctrl_enable_mon_event (enum resctrl_event_id eventid,bool any_cpu); +#define MAX_BINARY_BITS 27 + +void resctrl_enable_mon_event (enum resctrl_event_id eventid,bool any_cpu, +unsigned int binary_bits);bool resctrl_is_mon_event_enabled (enum resctrl_event_id eventid);
fs/resctrl/internal.h +5 -0
@@ -58,6 +58,9 @@ static inline struct rdt_fs_context *rdt_fc2context(struct fs_context *fc)* @name: name of the event * @configurable: true if the event is configurable * @any_cpu: true if the event can be read from any CPU +* @is_floating_point: event values are displayed in floating point format +* @binary_bits: number of fixed-point binary bits from architecture, +* only valid if @is_floating_point is true * @enabled: true if the event is enabled */ struct mon_evt {
@@ -66,6 +69,8 @@ struct mon_evt {char *name;bool configurable;bool any_cpu; +bool is_floating_point; +unsigned int binary_bits;bool enabled; };
arch/x86/kernel/cpu/resctrl/core.c +3 -3
@@ -888,15 +888,15 @@ static __init bool get_rdt_mon_resources(void)bool ret = false;if (rdt_cpu_has (X86_FEATURE_CQM_OCCUP_LLC )) { -resctrl_enable_mon_event (QOS_L3_OCCUP_EVENT_ID , false); +resctrl_enable_mon_event (QOS_L3_OCCUP_EVENT_ID , false,0 ); ret = true; }if (rdt_cpu_has (X86_FEATURE_CQM_MBM_TOTAL )) { -resctrl_enable_mon_event (QOS_L3_MBM_TOTAL_EVENT_ID , false); +resctrl_enable_mon_event (QOS_L3_MBM_TOTAL_EVENT_ID , false,0 ); ret = true; }if (rdt_cpu_has (X86_FEATURE_CQM_MBM_LOCAL )) { -resctrl_enable_mon_event (QOS_L3_MBM_LOCAL_EVENT_ID , false); +resctrl_enable_mon_event (QOS_L3_MBM_LOCAL_EVENT_ID , false,0 ); ret = true; }
fs/resctrl/ctrlmondata.c +84 -0
102 lines not on this page · raw message
fs/resctrl/monitor.c +8 -2
@@ -901,16 +901,22 @@ struct mon_evt mon_event_all[QOS_NUM_EVENTS] = { }, }; -void resctrl_enable_mon_event (enum resctrl_event_id eventid,bool any_cpu) +void resctrl_enable_mon_event (enum resctrl_event_id eventid,bool any_cpu,unsigned int binary_bits) { -if (WARN_ON_ONCE (eventid <QOS_FIRST_EVENT || eventid >=QOS_NUM_EVENTS )) +if (WARN_ON_ONCE (eventid <QOS_FIRST_EVENT || eventid >=QOS_NUM_EVENTS || + binary_bits >MAX_BINARY_BITS ))return ;if (mon_event_all[eventid].enabled) {pr_warn ("Duplicate enable for event %d\n" , eventid);return ; } +if (binary_bits && !mon_event_all[eventid].is_floating_point) { +pr_warn ("Event %d may not be floating point\n" , eventid); +return ; + } mon_event_all[eventid].any_cpu = any_cpu; + mon_event_all[eventid].binary_bits = binary_bits; mon_event_all[eventid].enabled = true; }
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 14/32] x86,fs/resctrl: Support binary fixed point event counters
Hi Tony,
Quoted 7 lines · Tony Luck
resctrl assumes that all monitor events can be displayed as unsigned decimal integers.
Hardware architecture counters may provide some telemetry events with greater precision where the event is not a simple count, but is a measurement of some sort (e.g. Joules for energy consumed).
Quoted 5 lines
Add a new argument to
resctrl_enable_mon_event()for architecture code to inform the file system that the value for a counter is a fixed-point value with a specific number of binary places.
Only allow architecture to use floating point format on events that it marked withmon_evt::is_floating_point.
I interpret two phrases above to mean that architecture controls whether
an event is floating point or not:
"architecture code to inform the file system that the value for a counter is a fixed-point value"
and
"Only allow architecture to use floating point format on events that *it* marked with mon_evt::is_floating_point."
I think this needs to be explicit that resctrl fs determines whether an event is floating point or not and architecture cannot modify this, of course it could set a floating point event's binary places to zero.
Quoted 25 lines
Display fixed point values with values rounded to an appropriate number of decimal places for the precision of the number of binary places provided. Add one extra decimal place for every three additional binary places, except for low precision binary values where exact representation is possible:
1 binary place is 0.0 or 0.5. => 1 decimal place
2 binary places is 0.0, 0.25, 0.5, 0.75 => 2 decimal places
3 binary places is 0.0, 0.125, etc. => 3 decimal placesSigned-off-by Tony Luck <[email protected]>--- include/linux/resctrl.h | 5 +- fs/resctrl/internal.h | 5 ++ arch/x86/kernel/cpu/resctrl/core.c | 6 +-- fs/resctrl/ctrlmondata.c | 84 ++++++++++++++++++++++++++++++ fs/resctrl/monitor.c | 10 +++- 5 files changed, 104 insertions(+), 6 deletions(-)include/linux/resctrl.h +0
-0
include/linux/resctrl.h u32 resctrl_arch_get_num_closid(struct rdt_resource *r); · line 382
Quoted 5 lines
include/linux/resctrl.h +1
-1@@ -379,7 +379,10 @@ u32 resctrl_arch_get_num_closid(struct rdt_resource *r);u32 resctrl_arch_system_num_rmid_idx (void );int resctrl_arch_update_domains (struct rdt_resource *r,u32 closid); -void resctrl_enable_mon_event (enum resctrl_event_id eventid,bool any_cpu); +#define MAX_BINARY_BITS 27
This MAX_BINARY_BITS define can stay internal to resctrl until it is used by an arch.
include/linux/resctrl.h u32 resctrl_arch_get_num_closid(struct rdt_resource *r); · line 388
Quoted 6 lines
include/linux/resctrl.h +3
-0+ +void resctrl_enable_mon_event (enum resctrl_event_id eventid,bool any_cpu, +unsigned int binary_bits);bool resctrl_is_mon_event_enabled (enum resctrl_event_id eventid);
Reinette
Tony Luck
maintainerPATCH v8 15/32 x86,fs/resctrl: Add an architectural hook called for each mount
In reply to Tony LuckEnumeration of Intel telemetry events is an asyncronnous process involving several mutually dependent drivers added as auxiliary devices during the device_initcall() phase of Linux boot. The process completes after the probe functions for these drivers are called. 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.
Call the hook on every attempted mount. But expectations are that most actions (like enumeration) will only need to be performed on the first call.
The call is made with no locks held. Architecture code is responsible for any required locking.
--- include/linux/resctrl.h | 6 ++++++ arch/x86/kernel/cpu/resctrl/core.c | 9 +++++++++ fs/resctrl/rdtgroup.c | 2 ++ 3 files changed, 17 insertions(+)
include/linux/resctrl.h +6 -0
@@ -461,6 +461,12 @@ void resctrl_offline_mon_domain(struct rdt_resource *r, struct rdt_domain_hdr *hvoid resctrl_online_cpu (unsigned int cpu);void resctrl_offline_cpu (unsigned int cpu); +/* +* Architecture hook called at beginning of each file system mount attempt. +* No locks are held. +*/ +void resctrl_arch_pre_mount (void ); +/** * resctrl_arch_rmid_read() - Read the eventid counter corresponding to rmid * for this resource and domain.
arch/x86/kernel/cpu/resctrl/core.c +9 -0
@@ -718,6 +718,15 @@ static int resctrl_arch_offline_cpu(unsigned int cpu)return 0 ; } +void resctrl_arch_pre_mount (void ) +{ +static atomic_t only_once =ATOMIC_INIT (0 ); +int old =0 ; + +if (!atomic_try_cmpxchg (&only_once, &old,1 )) +return ; +} +enum {RDT_FLAG_CMT ,RDT_FLAG_MBM_TOTAL ,
fs/resctrl/rdtgroup.c +2 -0
@@ -2585,6 +2585,8 @@ static int rdt_get_tree(struct fs_context *fc)struct rdt_resource *r;int ret; +resctrl_arch_pre_mount (); +cpus_read_lock ();mutex_lock (&rdtgroup_mutex);/*
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 15/32] x86,fs/resctrl: Add an architectural hook called for each mount
Hi Tony,
Quoted 1 line · Tony Luck
Enumeration of Intel telemetry events is an asyncronnous process involving
"asyncronnous" -> "asynchronous"
Quoted 3 lines
several mutually dependent drivers added as auxiliary devices during the
device_initcall()phase of Linux boot. The process completes after the probe functions for these drivers are called. But this happens after
"for these drivers" -> "of these drivers"?
"are called" -> "completes" or "are run"?
(i.e the probe functions should not just be called but need to finish their work?)
Quoted 10 lines
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/fstabfor 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.
Call the hook on every attempted mount. But expectations are that
"But expectations" -> "Expectations"
Quoted 4 lines
most actions (like enumeration) will only need to be performed on the first call.
The call is made with no locks held. Architecture code is responsible
"The call is made with no locks held." -> "resctrl filesystem calls the hook with no locks held."
(imperative)
Quoted 4 lines
for any required locking.
Signed-off-by Tony Luck <[email protected]>---
Reinette
Tony Luck
maintainerPATCH v8 16/32 x86,fs/resctrl: Add and initialize rdt_resource for package scope monitor
In reply to Tony LuckAdd a new PERF_PKG resource and introduce package level scope for monitoring telemetry events so that CPU hotplug notifiers can build domains at the package granularity.
Use the physical package ID available via topology_physical_package_id() to identify the monitoring domains with package level scope. This enables user space to use:
/sys/devices/system/cpu/cpuX/topology/physical_package_id
to identify the monitoring domain a CPU is associated with.
--- include/linux/resctrl.h | 2 ++ fs/resctrl/internal.h | 2 ++ arch/x86/kernel/cpu/resctrl/core.c | 10 ++++++++++ fs/resctrl/rdtgroup.c | 2 ++ 4 files changed, 16 insertions(+)
include/linux/resctrl.h +2 -0
@@ -53,6 +53,7 @@ enum resctrl_res_level {RDT_RESOURCE_L2 ,RDT_RESOURCE_MBA ,RDT_RESOURCE_SMBA , +RDT_RESOURCE_PERF_PKG ,/* Must be the last */ RDT_NUM_RESOURCES,
@@ -252,6 +253,7 @@ enum resctrl_scope {RESCTRL_L2_CACHE =2 ,RESCTRL_L3_CACHE =3 ,RESCTRL_L3_NODE , + RESCTRL_PACKAGE, };/**
fs/resctrl/internal.h +2 -0
@@ -240,6 +240,8 @@ struct rdtgroup {#define RFTYPE_DEBUG BIT(10) +#define RFTYPE_RES_PERF_PKG BIT(11) +#define RFTYPE_CTRL_INFO (RFTYPE_INFO | RFTYPE_CTRL)#define RFTYPE_MON_INFO (RFTYPE_INFO | RFTYPE_MON)
arch/x86/kernel/cpu/resctrl/core.c +10 -0
@@ -100,6 +100,14 @@ struct rdt_hw_resource rdt_resources_all[RDT_NUM_RESOURCES] = { .schema_fmt = RESCTRL_SCHEMA_RANGE, }, }, + [RDT_RESOURCE_PERF_PKG ] = + { + .r_resctrl = { + .name ="PERF_PKG" , + .mon_scope =RESCTRL_PACKAGE , + .mon_domains =mon_domain_init (RDT_RESOURCE_PERF_PKG ), + }, + }, };u32 resctrl_arch_system_num_rmid_idx (void )
@@ -433,6 +441,8 @@ static int get_domain_id_from_scope(int cpu, enum resctrl_scope scope)return get_cpu_cacheinfo_id (cpu, scope);case RESCTRL_L3_NODE :return cpu_to_node (cpu); +case RESCTRL_PACKAGE : +return topology_physical_package_id (cpu);default :break ; }
fs/resctrl/rdtgroup.c +2 -0
@@ -2195,6 +2195,8 @@ static unsigned long fflags_from_resource(struct rdt_resource *r)case RDT_RESOURCE_MBA :case RDT_RESOURCE_SMBA :return RFTYPE_RES_MB ; +case RDT_RESOURCE_PERF_PKG : +return RFTYPE_RES_PERF_PKG ; }return WARN_ON_ONCE (1 );
Signature · 1 line
2.50.1
Re: [PATCH v8 16/32] x86,fs/resctrl: Add and initialize rdt_resource for package scope monitor
Hi Tony,
Quoted 4 lines · Tony Luck
Add a new
PERF_PKGresource and introduce package level scope for monitoring telemetry events so that CPU hotplug notifiers can build domains at the package granularity.
Quoted 8 lines
Use the physical package ID available via
topology_physical_package_id()to identify the monitoring domains with package level scope. This enables user space to use:
/sys/devices/system/cpu/cpuX/topology/physical_package_id
to identify the monitoring domain a CPU is associated with.Signed-off-by Tony Luck <[email protected]>---
Reinette
Tony Luck
maintainerPATCH v8 17/32 x86/resctrl: Discover hardware telemetry events
In reply to Tony LuckData for telemetry events is collected by each CPU and sent to a nearby telemetry event aggregator either when the value of IA32_PQR_ASSOC.RMID is changed, or when two milliseconds have elapsed.
The telemetry event aggregators maintain per-RMID per-event counts of the total seen for all the CPUs. There may be more than one telemetry event aggregator per package.
Each telemetry event aggregator is responsible for a specific group of events. E.g. on the Intel Clearwater Forest CPU there are two types of aggregators. One type tracks a pair of energy related events. The other type tracks a subset of "perf" type events.
The event counts are made available to Linux in a region of MMIO space for each aggregator. All details about the layout of counters in each aggregator MMIO region are described in XML files published by Intel and mad available in a GitHub
repository: https://github.com/intel/Intel-PMT.
The key to matching a specific telemetry aggregator to the XML file that describes the MMIO layout is a 32-bit value. The Linux telemetry subsystem refers to this as a "guid" while the XML files call it a "uniqueid".
Each XML file provides the following information:
1) Which telemetry events are included in the group.
2) The order in which the event counters appear for each RMID.
3) The value type of each event counter (integer or fixed-point).
4) The number of RMIDs supported.
5) Which additional aggregator status registers are included.
6) The total size of the MMIO region for this aggregator.
Enumeration of support for telemetry events is done by the INTEL_PMT_DISCOVERY driver (a subcomponent of the INTEL_PMT_TELEMETRY driver). This driver provides intel_pmt_get_regions_by_feature() to list all available telemetry event aggregators. The list includes the "guid", the base address in MMIO space for the region where the event counters are exposed, and the package id where the CPUs that report to this aggregator are located.
Add a new Kconfig option CONFIG_X86_CPU_RESCTRL_INTEL_AET for the Intel specific parts of telemetry code. This depends on the INTEL_PMT_TELEMETRY and INTEL_TPMI drivers being built-in to the kernel for enumeration of telemetry features.
Call intel_pmt_get_regions_by_feature() for each pmt_feature_id that indicates per-RMID telemetry.
Save the returned pmt_feature_group pointers with guids that are known to resctrl for use at run time.
Those pointers will be returned to the INTEL_PMT_TELEMETRY subsystem at resctrl_arch_exit() time.
--- arch/x86/kernel/cpu/resctrl/internal.h | 8 ++ arch/x86/kernel/cpu/resctrl/core.c | 5 + arch/x86/kernel/cpu/resctrl/intel_aet.c | 120 ++++++++++++++++++++++++ arch/x86/Kconfig | 13 +++ arch/x86/kernel/cpu/resctrl/Makefile | 1 + 5 files changed, 147 insertions(+) create mode 100644 arch/x86/kernel/cpu/resctrl/intel_aet.c
arch/x86/kernel/cpu/resctrl/internal.h +8 -0
@@ -169,4 +169,12 @@ void __init intel_rdt_mbm_apply_quirk(void);void rdt_domain_reconfigure_cdp (struct rdt_resource *r); +#ifdef CONFIG_X86_CPU_RESCTRL_INTEL_AET +bool intel_aet_get_events (void ); +void __exit intel_aet_exit(void); +#else +static inline bool intel_aet_get_events (void ) {return false; } +static inline void __exit intel_aet_exit(void) { } +#endif +#endif /* _ASM_X86_RESCTRL_INTERNAL_H */
arch/x86/kernel/cpu/resctrl/core.c +5 -0
@@ -735,6 +735,9 @@ void resctrl_arch_pre_mount(void)if (!atomic_try_cmpxchg (&only_once, &old,1 ))return ; + +if (!intel_aet_get_events ()) +return ; }enum {
@@ -1087,6 +1090,8 @@ late_initcall(resctrl_arch_late_init); static void __exit resctrl_arch_exit(void) { +intel_aet_exit (); +cpuhp_remove_state (rdt_online);resctrl_exit ();
arch/x86/kernel/cpu/resctrl/intel_aet.c new file +120 -0
120 lines not on this page · raw message
arch/x86/Kconfig +13 -0
@@ -525,6 +525,19 @@ config X86_CPU_RESCTRL Say N if unsure. +config X86_CPU_RESCTRL_INTEL_AET + bool "Intel Application Energy Telemetry" if INTEL_PMT_TELEMETRY=y && INTEL_TPMI=y + depends on X86_CPU_RESCTRL && CPU_SUP_INTEL + help + Enable per-RMID telemetry events in resctrl + + Intel feature that collects per-RMID execution data + about energy consumption, measure of frequency independent + activity and other performance metrics. Data is aggregated + per package. + + Say N if unsure. + config X86_FRED bool "Flexible Return and Event Delivery" depends on X86_64
arch/x86/kernel/cpu/resctrl/Makefile +1 -0
@@ -1,6 +1,7 @@ # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_X86_CPU_RESCTRL) += core.o rdtgroup.o monitor.o obj-$(CONFIG_X86_CPU_RESCTRL) += ctrlmondata.o +obj-$(CONFIG_X86_CPU_RESCTRL_INTEL_AET) += intel_aet.o obj-$(CONFIG_RESCTRL_FS_PSEUDO_LOCK) += pseudo_lock.o # To allow define_trace.h's recursive include:
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 17/32] x86/resctrl: Discover hardware telemetry events
Hi Tony,
Quoted 1 line · Tony Luck
Data for telemetry events is collected by each CPU and sent
"Each CPU collects data for telemetry events that it sends ..." (imperative)
Quoted 2 lines
to a nearby telemetry event aggregator either when the value of IA32_PQR_ASSOC.RMID is changed, or when two milliseconds
"is changed" -> "changes"
"or when a two millisecond timer expires" (imperative and matches the cover letter ... almost ... there is timer vs counter)
Quoted 1 line
have elapsed.
Please make use of allowed line length. These line wraps are getting very short and quite noticeable with this growing changelog.
Quoted 11 lines
The telemetry event aggregators maintain per-RMID per-event counts of the total seen for all the CPUs. There may be more than one telemetry event aggregator per package.
Each telemetry event aggregator is responsible for a specific group of events. E.g. on the Intel Clearwater Forest CPU there are two types of aggregators. One type tracks a pair of energy related events. The other type tracks a subset of "perf" type events.
Quoted 4 lines
The event counts are made available to Linux in a region of MMIO space for each aggregator. All details about the layout of counters in each aggregator MMIO region are described in XML files published by Intel and mad available in a GitHub
"mad" -> "made"
Quoted 15 lines
repository: https://github.com/intel/Intel-PMT.
The key to matching a specific telemetry aggregator to the XML file that describes the MMIO layout is a 32-bit value. The Linux telemetry subsystem refers to this as a "guid" while the XML files call it a "uniqueid".
Each XML file provides the following information:
1) Which telemetry events are included in the group.
2) The order in which the event counters appear for each RMID.
3) The value type of each event counter (integer or fixed-point).
4) The number of RMIDs supported.
5) Which additional aggregator status registers are included.
6) The total size of the MMIO region for this aggregator.
Quoted 2 lines
Enumeration of support for telemetry events is done by the
INTEL_PMT_DISCOVERYdriver (a subcomponent of theINTEL_PMT_TELEMETRY
"The INTEL_PMT_TELEMETRY driver enumerates support for telemetry events." (imperative)
Could mentions of INTEL_PMT_DISCOVERY be dropped? It is INTEL_PMT_TELEMETRY that provides intel_pmt_get_regions_by_feature() and I do not see how describing INTEL_PMT_DISCOVERY helps here.
Quoted 11 lines
driver). This driver provides
intel_pmt_get_regions_by_feature()to list all available telemetry event aggregators. The list includes the "guid", the base address in MMIO space for the region where the event counters are exposed, and the package id where the CPUs that report to this aggregator are located.Add a new
KconfigoptionCONFIG_X86_CPU_RESCTRL_INTEL_AETfor the Intel specific parts of telemetry code. This depends on theINTEL_PMT_TELEMETRYandINTEL_TPMIdrivers being built-in to the kernel for enumeration of telemetry features.
Quoted 8 lines
Call
intel_pmt_get_regions_by_feature()for eachpmt_feature_idthat indicates per-RMID telemetry.Save the returned
pmt_feature_grouppointers with guids that are known to resctrl for use at run time.Those pointers will be returned to the
INTEL_PMT_TELEMETRYsubsystem atresctrl_arch_exit()time.
Last two paragraphs can merge.
intel_aet_exit() is empty here and I think that the code that "returns the pointers" can actually be included here to make clear how the "get" done in this patch is paired with a "put" to not make one wonder about reference counting issues. I believe that doing so cleanly here (without the active_event_groups that I find unnecessary ... more later) will make the code more symmetrical and easier to follow while also removing the "just trust me I'll do this later" uncertainty.
Quoted 3 lines
Signed-off-by Tony Luck <[email protected]>---
(missing the maintainer notes about checkpatch.pl troubles)
...
Quoted 20 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c new file +14
-0@@ -0,0 +1,120 @@ +// SPDX-License-Identifier: GPL-2.0-only +/* +* Resource Director Technology(RDT) +* - Intel Application Energy Telemetry +* +* Copyright (C) 2025 Intel Corporation +* +* Author: +* Tony Luck <[email protected]> +*/ + +#define pr_fmt (fmt) "resctrl: " fmt + +#include <linux/cleanup.h>
arch/x86/kernel/cpu/resctrl/intel_aet.c line 24
Quoted 10 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c new file +10
-0+#include <linux/cpu.h> +#include <linux/intel_vsec.h> +#include <linux/resctrl.h> + +#include "internal.h" + +/** +* struct event_group - All information about a group of telemetry events. +* @pfg: Points to the aggregated telemetry space information +* within the OOBMSM driver that contains data for all
"OOBMSM" -> "INTEL_PMT_TELEMETRY"?
Quoted 37 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c new file +37
-0+* telemetry regions. +* @guid: Unique number per XML description file. +*/ +struct event_group { +/* Data fields for additional structures to manage this group. */ +struct pmt_feature_group *pfg; + +/* Remaining fields initialized from XML file. */ +u32 guid; +}; + +/* +* Link: https://github.com/intel/Intel-PMT +* File: xml/CWF/OOBMSM/RMID-ENERGY/cwf_aggregator.xml +*/ +static struct event_group energy_0x26696143 = { + .guid =0x26696143 , +}; + +/* +* Link: https://github.com/intel/Intel-PMT +* File: xml/CWF/OOBMSM/RMID-PERF/cwf_aggregator.xml +*/ +static struct event_group perf_0x26557651 = { + .guid =0x26557651 , +}; + +static struct event_group *known_energy_event_groups[] = { + &energy_0x26696143, +}; + +static struct event_group *known_perf_event_groups[] = { + &perf_0x26557651, +}; + +/* Stub for now */ +static int discover_events (struct event_group *e,struct pmt_feature_group *p)
arch/x86/kernel/cpu/resctrl/intel_aet.c line 71
Quoted 10 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c new file +10
-0+{ +return -EINVAL ; +} + +DEFINE_FREE(intel_pmt_put_feature_group, struct pmt_feature_group *, + if (!IS_ERR_OR_NULL(_T)) +intel_pmt_put_feature_group (_T)) + +/* +* Make a request to the INTEL_PMT_DISCOVERY driver for the
"INTEL_PMT_DISCOVERY" -> "INTEL_PMT_TELEMETRY"
Please use line length available to not wrap lines so short.
Quoted 20 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c new file +20
-0+* pmt_feature_group for a specific feature. If there is +* one the returned structure has an array of telemetry_region +* structures. Each describes one telemetry aggregator. +* Try to use every telemetry aggregator with a known guid. +*/ +static bool get_pmt_feature (enum pmt_feature_id feature,struct event_group **evgs, +unsigned int num_evg) +{ + struct pmt_feature_group *p __free(intel_pmt_put_feature_group) = NULL; +struct event_group **peg; +int ret; + + p =intel_pmt_get_regions_by_feature (feature); + +if (IS_ERR_OR_NULL (p)) +return false; + +for (peg = evgs; peg < &evgs[num_evg]; peg++) { + ret =discover_events (*peg, p); +if (!ret) {
arch/x86/kernel/cpu/resctrl/intel_aet.c line 101
Quoted 10 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c new file +10
-0+ (*peg)->pfg =no_free_ptr (p); +return true; + } + } + +return false; +} + +/* +* Ask OOBMSM discovery driver for all the RMID based telemetry groups
"OOBMSM discovery" -> "INTEL_PMT_TELEMETRY"
Quoted 24 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c new file +19
-0+* that it supports. +*/ +bool intel_aet_get_events (void ) +{ +bool ret1, ret2; + + ret1 =get_pmt_feature (FEATURE_PER_RMID_ENERGY_TELEM , + known_energy_event_groups, +ARRAY_SIZE (known_energy_event_groups)); + ret2 =get_pmt_feature (FEATURE_PER_RMID_PERF_TELEM , + known_perf_event_groups, +ARRAY_SIZE (known_perf_event_groups)); + +return ret1 || ret2; +} + +void __exit intel_aet_exit(void) +{ +}arch/x86/Kconfig +0
-0
arch/x86/Kconfig config X86_CPU_RESCTRL · line 532
Quoted 8 lines
arch/x86/Kconfig +5
-0@@ -525,6 +525,19 @@ config X86_CPU_RESCTRL Say N if unsure. +config X86_CPU_RESCTRL_INTEL_AET + bool "Intel Application Energy Telemetry" if INTEL_PMT_TELEMETRY=y && INTEL_TPMI=y + depends on X86_CPU_RESCTRL && CPU_SUP_INTEL + help + Enable per-RMID telemetry events in resctrl
Missing period at end of sentence.
Quoted 16 lines
arch/x86/Kconfig +8
-0+ + Intel feature that collects per-RMID execution data + about energy consumption, measure of frequency independent + activity and other performance metrics. Data is aggregated + per package. + + Say N if unsure. + config X86_FRED bool "Flexible Return and Event Delivery" depends on X86_64arch/x86/kernel/cpu/resctrl/Makefile +0
-0
arch/x86/kernel/cpu/resctrl/Makefile line 7
Quoted 7 lines
arch/x86/kernel/cpu/resctrl/Makefile +1
-0@@ -1,6 +1,7 @@ # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_X86_CPU_RESCTRL) += core.o rdtgroup.o monitor.o obj-$(CONFIG_X86_CPU_RESCTRL) += ctrlmondata.o +obj-$(CONFIG_X86_CPU_RESCTRL_INTEL_AET) += intel_aet.o obj-$(CONFIG_RESCTRL_FS_PSEUDO_LOCK) += pseudo_lock.o # To allow define_trace.h's recursive include:
Reinette
Tony Luck
maintainerPATCH v8 18/32 x86/resctrl: Count valid telemetry aggregators per package
In reply to Tony LuckThere may be multiple telemetry aggregators per package, each enumerated by a telemetry region structure in the feature group.
Linux can only use telemetry regions when all of the following conditions are met:
1) The "guid" of the region is known to Linux
2) The package id for the region is valid (less than topology_max_packages())
3) The size of the MMIO region exactly matches the expected size for this "guid" (as implied from description in the XML file for this "guid").
Scan the array of telemetry region structures and count how many are usable in each package in preparation to allocate structures to save the MMIO addresses for each in a convenient format for use when reading event counters.
--- arch/x86/kernel/cpu/resctrl/intel_aet.c | 56 ++++++++++++++++++++++++- 1 file changed, 54 insertions(+), 2 deletions(-)
arch/x86/kernel/cpu/resctrl/intel_aet.c +54 -2
@@ -15,6 +15,7 @@#include <linux/cpu.h> #include <linux/intel_vsec.h> #include <linux/resctrl.h> +#include <linux/slab.h> #include "internal.h"
@@ -24,6 +25,7 @@* within the OOBMSM driver that contains data for all * telemetry regions. * @guid: Unique number per XML description file. +* @mmio_size: Number of bytes of MMIO registers for this group. */ struct event_group {/* Data fields for additional structures to manage this group. */
@@ -31,14 +33,19 @@ struct event_group {/* Remaining fields initialized from XML file. */ u32 guid; +size_t mmio_size; }; +#define XML_MMIO_SIZE (num_rmids, num_events, num_extra_status) \ + (((num_rmids) * (num_events) + (num_extra_status)) * sizeof(u64)) +/* * Link: https://github.com/intel/Intel-PMT * File: xml/CWF/OOBMSM/RMID-ENERGY/cwf_aggregator.xml */ static struct event_group energy_0x26696143 = { .guid =0x26696143 , + .mmio_size =XML_MMIO_SIZE (576 ,2 ,3 ), };/*
@@ -47,6 +54,7 @@ static struct event_group energy_0x26696143 = {*/ static struct event_group perf_0x26557651 = { .guid =0x26557651 , + .mmio_size =XML_MMIO_SIZE (576 ,7 ,3 ), };static struct event_group *known_energy_event_groups[] = {
@@ -57,10 +65,54 @@ static struct event_group *known_perf_event_groups[] = { &perf_0x26557651, }; -/* Stub for now */ +static bool skip_this_region (struct telemetry_region *tr,struct event_group *e) +{ +if (tr->guid != e->guid) +return true; +if (tr->plat_info.package_id >=topology_max_packages ()) { +pr_warn_once ("Bad package %d in guid 0x%x\n" , tr->plat_info.package_id, + tr->guid); +return true; + } +if (tr->size != e->mmio_size) { +pr_warn_once ("MMIO space %zu wrong size for guid 0x%x\n" , tr->size, e->guid); +return true; + } + +return false; +} + +/* +* Discover events from one pmt_feature_group. +* 1) Count how many usable telemetry regions per package. +* 2...) To be continued. +*/ static int discover_events (struct event_group *e,struct pmt_feature_group *p) { -return -EINVAL ; + int *pkgcounts __free(kfree) = NULL; +struct telemetry_region *tr; +int num_pkgs; + + num_pkgs =topology_max_packages (); + +/* Get per-package counts of telemetry regions for this event group */ +for (int i =0 ; i < p->count; i++) { + tr = &p->regions[i]; +if (skip_this_region (tr, e)) +continue ; + +if (!pkgcounts) { + pkgcounts =kcalloc (num_pkgs,sizeof (*pkgcounts),GFP_KERNEL ); +if (!pkgcounts) +return -ENOMEM ; + } + pkgcounts[tr->plat_info.package_id]++; + } + +if (!pkgcounts) +return -ENODEV ; + +return 0 ; } DEFINE_FREE(intel_pmt_put_feature_group, struct pmt_feature_group *,
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 18/32] x86/resctrl: Count valid telemetry aggregators per package
Hi Tony,
Quoted 54 lines · Tony Luck
arch/x86/kernel/cpu/resctrl/intel_aet.c +9
-1@@ -15,6 +15,7 @@#include <linux/cpu.h> #include <linux/intel_vsec.h> #include <linux/resctrl.h> +#include <linux/slab.h> #include "internal.h" @@ -24,6 +25,7 @@* within the OOBMSM driver that contains data for all * telemetry regions. * @guid: Unique number per XML description file. +* @mmio_size: Number of bytes of MMIO registers for this group. */ struct event_group {/* Data fields for additional structures to manage this group. */ @@ -31,14 +33,19 @@ struct event_group {/* Remaining fields initialized from XML file. */ u32 guid; +size_t mmio_size; }; +#define XML_MMIO_SIZE (num_rmids, num_events, num_extra_status) \ + (((num_rmids) * (num_events) + (num_extra_status)) * sizeof(u64)) +/* * Link: https://github.com/intel/Intel-PMT * File: xml/CWF/OOBMSM/RMID-ENERGY/cwf_aggregator.xml */ static struct event_group energy_0x26696143 = { .guid =0x26696143 , + .mmio_size =XML_MMIO_SIZE (576 ,2 ,3 ), };/* @@ -47,6 +54,7 @@ static struct event_group energy_0x26696143 = {*/ static struct event_group perf_0x26557651 = { .guid =0x26557651 , + .mmio_size =XML_MMIO_SIZE (576 ,7 ,3 ), };static struct event_group *known_energy_event_groups[] = {@@ -57,10 +65,54 @@ static struct event_group *known_perf_event_groups[] = { &perf_0x26557651, }; -/* Stub for now */ +static bool skip_this_region (struct telemetry_region *tr,struct event_group *e)
arch/x86/kernel/cpu/resctrl/intel_aet.c static struct event_group *known_perf_event_groups[] = { · line 78
Quoted 10 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +10
-0+{ +if (tr->guid != e->guid) +return true; +if (tr->plat_info.package_id >=topology_max_packages ()) { +pr_warn_once ("Bad package %d in guid 0x%x\n" , tr->plat_info.package_id, + tr->guid); +return true; + } +if (tr->size != e->mmio_size) { +pr_warn_once ("MMIO space %zu wrong size for guid 0x%x\n" , tr->size, e->guid);
I think this message can be improved. Compare with, for example, "MMIO space wrong size (%zu bytes) for guid 0x%x. Expected %zu bytes.\n" (please feel free to improve open to other ideas)
Quoted 28 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +25
-1+return true; + } + +return false; +} + +/* +* Discover events from one pmt_feature_group. +* 1) Count how many usable telemetry regions per package. +* 2...) To be continued. +*/ static int discover_events (struct event_group *e,struct pmt_feature_group *p) { -return -EINVAL ; + int *pkgcounts __free(kfree) = NULL; +struct telemetry_region *tr; +int num_pkgs; + + num_pkgs =topology_max_packages (); + +/* Get per-package counts of telemetry regions for this event group */ +for (int i =0 ; i < p->count; i++) { + tr = &p->regions[i]; +if (skip_this_region (tr, e)) +continue ; + +if (!pkgcounts) { + pkgcounts =kcalloc (num_pkgs,sizeof (*pkgcounts),GFP_KERNEL );
arch/x86/kernel/cpu/resctrl/intel_aet.c static struct event_group *known_perf_event_groups[] = { · line 115
Quoted 10 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +10
-0+if (!pkgcounts) +return -ENOMEM ; + } + pkgcounts[tr->plat_info.package_id]++; + } + +if (!pkgcounts) +return -ENODEV ; + +return 0 ;
Returning success requires matching support to drop the reference to the feature group that does not exist at this point. This makes the code increasingly harder to follow since the code that is promised in previous patch is not available yet but needed here. This can be solved by handling the reference in previous patch.
arch/x86/kernel/cpu/resctrl/intel_aet.c static struct event_group *known_perf_event_groups[] = { · line 118
Quoted 3 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +0
-0} DEFINE_FREE(intel_pmt_put_feature_group, struct pmt_feature_group *,
Reinette
Tony Luck
maintainerPATCH v8 19/32 x86/resctrl: Complete telemetry event enumeration
In reply to Tony LuckCounters for telemetry events are in MMIO space. Each telemetry_region structure returned in the pmt_feature_group returned from OOBMSM contains the base MMIO address for the counters.
There may be multiple aggregators per package. Scan all the telemetry_region structures again and save the number of regions together with a flex array of the MMIO addresses for each region indexed by package id.
Completed structure for each event group looks like this:
+---------------------+---------------------+
pkginfo** -->|pkginfo[package ID 0]|pkginfo[package ID 1]|
+---------------------+---------------------+
| |
v v
+--------------------+ +--------------------+
|struct pkg_mmio_info| |struct pkg_mmio_info|
+--------------------+ +--------------------+
|num_regions = M | |num_regions = N |
| addrs[0] | | addrs[0] |
| addrs[1] | | addrs[1] |
| ... | | ... |
| addrs[M-1] | | addrs[N-1] |
+--------------------+ +--------------------+Build a list (active_event_groups) of all the event groups that were successfully enabled. Use it to clean up in intel_aet_exit().
--- arch/x86/kernel/cpu/resctrl/intel_aet.c | 76 ++++++++++++++++++++++++- 1 file changed, 75 insertions(+), 1 deletion(-)
arch/x86/kernel/cpu/resctrl/intel_aet.c +75 -1
@@ -19,23 +19,43 @@#include "internal.h" +/** +* struct pkg_mmio_info - MMIO address information for one event group of a package. +* @num_regions: Number of telemetry regions on this package. +* @addrs: Array of MMIO addresses, one per telemetry region on this package. +* +* Provides convenient access to all MMIO addresses of one event group +* for one package. Used when reading event data on a package. +*/ +struct pkg_mmio_info { +unsigned int num_regions; + void __iomem *addrs[] __counted_by(num_regions); +}; +/** * struct event_group - All information about a group of telemetry events. * @pfg: Points to the aggregated telemetry space information * within the OOBMSM driver that contains data for all * telemetry regions. +* @list: Member of active_event_groups. +* @pkginfo: Per-package MMIO addresses of telemetry regions belonging to this group. * @guid: Unique number per XML description file. * @mmio_size: Number of bytes of MMIO registers for this group. */ struct event_group {/* Data fields for additional structures to manage this group. */ struct pmt_feature_group *pfg; +struct list_head list; +struct pkg_mmio_info **pkginfo;/* Remaining fields initialized from XML file. */ u32 guid;size_t mmio_size; }; +/* All successfully enabled event groups */ +static LIST_HEAD (active_event_groups); +#define XML_MMIO_SIZE (num_rmids, num_events, num_extra_status) \ (((num_rmids) * (num_events) + (num_extra_status)) * sizeof(u64))
@@ -82,15 +102,32 @@ static bool skip_this_region(struct telemetry_region *tr, struct event_group *e)return false; } +static void free_pkg_mmio_info (struct pkg_mmio_info **mmi) +{ +int num_pkgs =topology_max_packages (); + +if (!mmi) +return ; + +for (int i =0 ; i < num_pkgs; i++) +kfree (mmi[i]); +kfree (mmi); +} + +DEFINE_FREE(pkg_mmio_info, struct pkg_mmio_info **, free_pkg_mmio_info(_T)) +/* * Discover events from one pmt_feature_group. * 1) Count how many usable telemetry regions per package. -* 2...) To be continued. +* 2) Allocate per-package structures and populate with MMIO +* addresses of the telemetry regions. */static int discover_events (struct event_group *e,struct pmt_feature_group *p) { + struct pkg_mmio_info **pkginfo __free(pkg_mmio_info) = NULL; int *pkgcounts __free(kfree) = NULL;struct telemetry_region *tr; +struct pkg_mmio_info *mmi;int num_pkgs; num_pkgs =topology_max_packages ();
@@ -112,6 +149,34 @@ static int discover_events(struct event_group *e, struct pmt_feature_group *p)if (!pkgcounts)return -ENODEV ; +/* Allocate array for per-package struct pkg_mmio_info data */ + pkginfo =kcalloc (num_pkgs,sizeof (*pkginfo),GFP_KERNEL ); +if (!pkginfo) +return -ENOMEM ; + +/* +* Allocate per-package pkg_mmio_info structures and initialize +* count of telemetry_regions in each one. +*/ +for (int i =0 ; i < num_pkgs; i++) { + pkginfo[i] =kzalloc (struct_size (pkginfo[i], addrs, pkgcounts[i]),GFP_KERNEL ); +if (!pkginfo[i]) +return -ENOMEM ; + pkginfo[i]->num_regions = pkgcounts[i]; + } + +/* Save MMIO address(es) for each telemetry region in per-package structures */ +for (int i =0 ; i < p->count; i++) { + tr = &p->regions[i]; +if (skip_this_region (tr, e)) +continue ; + mmi = pkginfo[tr->plat_info.package_id]; + mmi->addrs[--pkgcounts[tr->plat_info.package_id]] = tr->addr; + } + e->pkginfo =no_free_ptr (pkginfo); + +list_add (&e->list, &active_event_groups); +return 0 ; }
@@ -169,4 +234,13 @@ bool intel_aet_get_events(void) void __exit intel_aet_exit(void) { +struct event_group *evg, *tmp; + +list_for_each_entry_safe (evg, tmp, &active_event_groups, list) { +intel_pmt_put_feature_group (evg->pfg); + evg->pfg =NULL ; +free_pkg_mmio_info (evg->pkginfo); + evg->pkginfo =NULL ; +list_del (&evg->list); + } }
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 19/32] x86/resctrl: Complete telemetry event enumeration
Hi Tony,
Quoted 2 lines · Tony Luck
Counters for telemetry events are in MMIO space. Each
telemetry_regionstructure returned in thepmt_feature_groupreturned from OOBMSM contains
"OOBMSM" -> "INTEL_PMT_TELEMETRY"?
Quoted 24 lines
the base MMIO address for the counters.
There may be multiple aggregators per package. Scan all the
telemetry_regionstructures again and save the number of regions together with a flex array of the MMIO addresses for each region indexed by package id.Completed structure for each event group looks like this:
+---------------------+---------------------+ pkginfo** -->|pkginfo[package ID 0]|pkginfo[package ID 1]| +---------------------+---------------------+ | | v v +--------------------+ +--------------------+ |struct pkg_mmio_info| |struct pkg_mmio_info| +--------------------+ +--------------------+ |num_regions = M | |num_regions = N | | addrs[0] | | addrs[0] | | addrs[1] | | addrs[1] | | ... | | ... | | addrs[M-1] | | addrs[N-1] | +--------------------+ +--------------------+
Quoted 2 lines
Build a list (
active_event_groups) of all the event groups that were successfully enabled. Use it to clean up inintel_aet_exit().
While this adds a note about active_event_groups it does not motivate *why* this additional data structure is needed. I find this additional data structure unnecessary and actually makes the code harder to understand. As I understand event_group::pfg can already be used to determine if the event group is active or not. Adding a new data structure to track this thus seems unnecessary. If this is a data structure created for convenience I think it should rather be replaced by helpers that use event_group::pfg.
Quoted 3 lines
Signed-off-by Tony Luck <[email protected]>---
...
Quoted 4 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +0
-0@@ -169,4 +234,13 @@ bool intel_aet_get_events(void) void __exit intel_aet_exit(void) {
arch/x86/kernel/cpu/resctrl/intel_aet.c bool intel_aet_get_events(void) · line 246
Quoted 10 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +9
-0+struct event_group *evg, *tmp; + +list_for_each_entry_safe (evg, tmp, &active_event_groups, list) { +intel_pmt_put_feature_group (evg->pfg); + evg->pfg =NULL ; +free_pkg_mmio_info (evg->pkginfo); + evg->pkginfo =NULL ; +list_del (&evg->list); + } }
I think above can be simplified by making it symmetrical to intel_aet_get_events().
For example:
static void put_pmt_feature(struct event_group **evgs, unsigned int num_evg)
{
struct event_group **peg;
for (peg = evgs; peg < &evgs[num_evg]; peg++) {
if (!(*peg)->pfg)
return;
intel_pmt_put_feature_group((*peg)->pfg);
/* rest of cleanup from intel_aet_exit() above */
}
} void __ exit intel_aet_exit(void) {
put_pmt_feature(known_energy_event_groups,
ARRAY_SIZE(known_energy_event_groups));
put_pmt_feature(known_perf_event_groups,
ARRAY_SIZE(known_perf_event_groups));
} Reinette
Tony Luck
maintainerPATCH v8 20/32 x86,fs/resctrl: Fill in details of events for guid 0x26696143 and 0x26557651
In reply to Tony LuckThese two guids describe the events supported on Clearwater Forest.
The offsets in MMIO space are arranged in groups for each RMID.
E.g the "energy" counters for guid 0x26696143 are arranged like this:
MMIO offset:0x0000 Counter for RMID 0 PMT_EVENT_ENERGY
MMIO offset:0x0008 Counter for RMID 0 PMT_EVENT_ACTIVITY
MMIO offset:0x0010 Counter for RMID 1 PMT_EVENT_ENERGY
MMIO offset:0x0018 Counter for RMID 1 PMT_EVENT_ACTIVITY
...
MMIO offset:0x23F0 Counter for RMID 575 PMT_EVENT_ENERGY
MMIO offset:0x23F8 Counter for RMID 575 PMT_EVENT_ACTIVITYDefine these events in the file system code and add the events to the event_group structures.
PMT_EVENT_ENERGY and PMT_EVENT_ACTIVITY are produced in fixed point format. File system code must output as floating point values.
--- include/linux/resctrl_types.h | 11 ++++++++ arch/x86/kernel/cpu/resctrl/intel_aet.c | 34 ++++++++++++++++++++++++ fs/resctrl/monitor.c | 35 ++++++++++++++----------- 3 files changed, 65 insertions(+), 15 deletions(-)
include/linux/resctrl_types.h +11 -0
@@ -47,6 +47,17 @@ enum resctrl_event_id {QOS_L3_MBM_TOTAL_EVENT_ID =0x02 ,QOS_L3_MBM_LOCAL_EVENT_ID =0x03 , +/* Intel Telemetry Events */ +PMT_EVENT_ENERGY , +PMT_EVENT_ACTIVITY , +PMT_EVENT_STALLS_LLC_HIT , +PMT_EVENT_C1_RES , +PMT_EVENT_UNHALTED_CORE_CYCLES , +PMT_EVENT_STALLS_LLC_MISS , +PMT_EVENT_AUTO_C6_RES , +PMT_EVENT_UNHALTED_REF_CYCLES , +PMT_EVENT_UOPS_RETIRED , +/* Must be the last */ QOS_NUM_EVENTS, };
arch/x86/kernel/cpu/resctrl/intel_aet.c +34 -0
@@ -32,6 +32,21 @@ struct pkg_mmio_info { void __iomem *addrs[] __counted_by(num_regions); }; +/** +* struct pmt_event - Telemetry event. +* @id: Resctrl event id. +* @idx: Counter index within each per-RMID block of counters. +* @bin_bits: Zero for integer valued events, else number bits in fraction +* part of fixed-point. +*/ +struct pmt_event { +enum resctrl_event_id id; +unsigned int idx; +unsigned int bin_bits; +}; + +#define EVT (_id, _idx, _bits) { .id = _id, .idx = _idx, .bin_bits = _bits } +/** * struct event_group - All information about a group of telemetry events. * @pfg: Points to the aggregated telemetry space information
@@ -41,6 +56,8 @@ struct pkg_mmio_info {* @pkginfo: Per-package MMIO addresses of telemetry regions belonging to this group. * @guid: Unique number per XML description file. * @mmio_size: Number of bytes of MMIO registers for this group. +* @num_events: Number of events in this group. +* @evts: Array of event descriptors. */ struct event_group {/* Data fields for additional structures to manage this group. */
@@ -51,6 +68,8 @@ struct event_group {/* Remaining fields initialized from XML file. */ u32 guid;size_t mmio_size; +unsigned int num_events; + struct pmt_event evts[] __counted_by(num_events); };/* All successfully enabled event groups */
@@ -66,6 +85,11 @@ static LIST_HEAD(active_event_groups);static struct event_group energy_0x26696143 = { .guid =0x26696143 , .mmio_size =XML_MMIO_SIZE (576 ,2 ,3 ), + .num_events =2 , + .evts = { +EVT (PMT_EVENT_ENERGY ,0 ,18 ), +EVT (PMT_EVENT_ACTIVITY ,1 ,18 ), + } };/*
@@ -75,6 +99,16 @@ static struct event_group energy_0x26696143 = {static struct event_group perf_0x26557651 = { .guid =0x26557651 , .mmio_size =XML_MMIO_SIZE (576 ,7 ,3 ), + .num_events =7 , + .evts = { +EVT (PMT_EVENT_STALLS_LLC_HIT ,0 ,0 ), +EVT (PMT_EVENT_C1_RES ,1 ,0 ), +EVT (PMT_EVENT_UNHALTED_CORE_CYCLES ,2 ,0 ), +EVT (PMT_EVENT_STALLS_LLC_MISS ,3 ,0 ), +EVT (PMT_EVENT_AUTO_C6_RES ,4 ,0 ), +EVT (PMT_EVENT_UNHALTED_REF_CYCLES ,5 ,0 ), +EVT (PMT_EVENT_UOPS_RETIRED ,6 ,0 ), + } };static struct event_group *known_energy_event_groups[] = {
fs/resctrl/monitor.c +20 -15
@@ -878,27 +878,32 @@ static void dom_data_exit(struct rdt_resource *r)mutex_unlock (&rdtgroup_mutex); } +#define MON_EVENT (_eventid, _name, _res, _fp) \ + [_eventid] = { \ + .name = _name, \ + .evtid = _eventid, \ + .rid = _res, \ + .is_floating_point = _fp, \ +} +/* * All available events. Architecture code marks the ones that * are supported by a system using resctrl_enable_mon_event() * to set .enabled. */ struct mon_evt mon_event_all[QOS_NUM_EVENTS ] = { - [QOS_L3_OCCUP_EVENT_ID ] = { - .name ="llc_occupancy" , - .evtid =QOS_L3_OCCUP_EVENT_ID , - .rid =RDT_RESOURCE_L3 , - }, - [QOS_L3_MBM_TOTAL_EVENT_ID ] = { - .name ="mbm_total_bytes" , - .evtid =QOS_L3_MBM_TOTAL_EVENT_ID , - .rid =RDT_RESOURCE_L3 , - }, - [QOS_L3_MBM_LOCAL_EVENT_ID ] = { - .name ="mbm_local_bytes" , - .evtid =QOS_L3_MBM_LOCAL_EVENT_ID , - .rid =RDT_RESOURCE_L3 , - }, +MON_EVENT (QOS_L3_OCCUP_EVENT_ID ,"llc_occupancy" ,RDT_RESOURCE_L3 , false), +MON_EVENT (QOS_L3_MBM_TOTAL_EVENT_ID ,"mbm_total_bytes" ,RDT_RESOURCE_L3 , false), +MON_EVENT (QOS_L3_MBM_LOCAL_EVENT_ID ,"mbm_local_bytes" ,RDT_RESOURCE_L3 , false), +MON_EVENT (PMT_EVENT_ENERGY ,"core_energy" ,RDT_RESOURCE_PERF_PKG , true), +MON_EVENT (PMT_EVENT_ACTIVITY ,"activity" ,RDT_RESOURCE_PERF_PKG , true), +MON_EVENT (PMT_EVENT_STALLS_LLC_HIT ,"stalls_llc_hit" ,RDT_RESOURCE_PERF_PKG , false), +MON_EVENT (PMT_EVENT_C1_RES ,"c1_res" ,RDT_RESOURCE_PERF_PKG , false), +MON_EVENT (PMT_EVENT_UNHALTED_CORE_CYCLES ,"unhalted_core_cycles" ,RDT_RESOURCE_PERF_PKG , false), +MON_EVENT (PMT_EVENT_STALLS_LLC_MISS ,"stalls_llc_miss" ,RDT_RESOURCE_PERF_PKG , false), +MON_EVENT (PMT_EVENT_AUTO_C6_RES ,"c6_res" ,RDT_RESOURCE_PERF_PKG , false), +MON_EVENT (PMT_EVENT_UNHALTED_REF_CYCLES ,"unhalted_ref_cycles" ,RDT_RESOURCE_PERF_PKG , false), +MON_EVENT (PMT_EVENT_UOPS_RETIRED ,"uops_retired" ,RDT_RESOURCE_PERF_PKG , false), };void resctrl_enable_mon_event (enum resctrl_event_id eventid,bool any_cpu,unsigned int binary_bits)
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 20/32] x86,fs/resctrl: Fill in details of events for guid 0x26696143 and 0x26557651
Hi Tony,
Quoted 1 line · Tony Luck
These two guids describe the events supported on Clearwater Forest.
Please let changelog stand on its own and not be a continuation of the subject.
Quoted 13 lines
The offsets in MMIO space are arranged in groups for each RMID.
E.g the "energy" counters for guid
0x26696143are arranged like this:MMIO offset:0x0000 Counter for RMID 0 PMT_EVENT_ENERGY MMIO offset:0x0008 Counter for RMID 0 PMT_EVENT_ACTIVITY MMIO offset:0x0010 Counter for RMID 1 PMT_EVENT_ENERGY MMIO offset:0x0018 Counter for RMID 1 PMT_EVENT_ACTIVITY ... MMIO offset:0x23F0 Counter for RMID 575 PMT_EVENT_ENERGY MMIO offset:0x23F8 Counter for RMID 575 PMT_EVENT_ACTIVITY
Quoted 2 lines
Define these events in the file system code and add the events to the
event_groupstructures.
Please add a note/link where these values are obtained from.
Quoted 6 lines
PMT_EVENT_ENERGYandPMT_EVENT_ACTIVITYare produced in fixed point format. File system code must output as floating point values.Signed-off-by Tony Luck <[email protected]>---
Reinette
Tony Luck
maintainerPATCH v8 21/32 x86,fs/resctrl: Add architectural event pointer
In reply to Tony LuckThe resctrl file system layer passes the domain, RMID, and event id to resctrl_arch_rmid_read() to fetch an event counter.
For some resources this is not enough information to efficiently access the counter. Fetching a telemetry event counter requires additional information that is private to the architecture, for example, the offset into MMIO space from where counter should be read.
Add mon_evt::arch_priv void pointer. Architecture code can initialize this when marking each event enabled.
File system code passes this pointer to resctrl_arch_rmid_read().
--- include/linux/resctrl.h | 7 +++++-- fs/resctrl/internal.h | 4 ++++ arch/x86/kernel/cpu/resctrl/core.c | 6 +++--- arch/x86/kernel/cpu/resctrl/monitor.c | 2 +- fs/resctrl/monitor.c | 14 ++++++++++---- 5 files changed, 23 insertions(+), 10 deletions(-)
include/linux/resctrl.h +5 -2
@@ -384,7 +384,7 @@ int resctrl_arch_update_domains(struct rdt_resource *r, u32 closid);#define MAX_BINARY_BITS 27void resctrl_enable_mon_event (enum resctrl_event_id eventid,bool any_cpu, -unsigned int binary_bits); +unsigned int binary_bits,void *arch_priv);bool resctrl_is_mon_event_enabled (enum resctrl_event_id eventid);
@@ -479,6 +479,9 @@ void resctrl_arch_pre_mount(void);* only. * @rmid: rmid of the counter to read. * @eventid: eventid to read, e.g. L3 occupancy. +* @arch_priv: Architecture private data for this event. +* The @arch_priv provided by the architecture via +* resctrl_enable_mon_event(). * @val: result of the counter read in bytes. * @arch_mon_ctx: An architecture specific value from * resctrl_arch_mon_ctx_alloc(), for MPAM this identifies
@@ -496,7 +499,7 @@ void resctrl_arch_pre_mount(void);*/ int resctrl_arch_rmid_read (struct rdt_resource *r,struct rdt_domain_hdr *hdr,u32 closid,u32 rmid,enum resctrl_event_id eventid, -u64 *val,void *arch_mon_ctx); +void *arch_priv,u64 *val,void *arch_mon_ctx);/** * resctrl_arch_rmid_read_context_check() - warn about invalid contexts
fs/resctrl/internal.h +4 -0
@@ -62,6 +62,9 @@ static inline struct rdt_fs_context *rdt_fc2context(struct fs_context *fc)* @binary_bits: number of fixed-point binary bits from architecture, * only valid if @is_floating_point is true * @enabled: true if the event is enabled +* @arch_priv: Architecture private data for this event. +* The @arch_priv provided by the architecture via +* resctrl_enable_mon_event(). */ struct mon_evt {enum resctrl_event_id evtid;
@@ -72,6 +75,7 @@ struct mon_evt {bool is_floating_point;unsigned int binary_bits;bool enabled; +void *arch_priv; };extern struct mon_evt mon_event_all[QOS_NUM_EVENTS ];
arch/x86/kernel/cpu/resctrl/core.c +3 -3
@@ -910,15 +910,15 @@ static __init bool get_rdt_mon_resources(void)bool ret = false;if (rdt_cpu_has (X86_FEATURE_CQM_OCCUP_LLC )) { -resctrl_enable_mon_event (QOS_L3_OCCUP_EVENT_ID , false,0 ); +resctrl_enable_mon_event (QOS_L3_OCCUP_EVENT_ID , false,0 ,NULL ); ret = true; }if (rdt_cpu_has (X86_FEATURE_CQM_MBM_TOTAL )) { -resctrl_enable_mon_event (QOS_L3_MBM_TOTAL_EVENT_ID , false,0 ); +resctrl_enable_mon_event (QOS_L3_MBM_TOTAL_EVENT_ID , false,0 ,NULL ); ret = true; }if (rdt_cpu_has (X86_FEATURE_CQM_MBM_LOCAL )) { -resctrl_enable_mon_event (QOS_L3_MBM_LOCAL_EVENT_ID , false,0 ); +resctrl_enable_mon_event (QOS_L3_MBM_LOCAL_EVENT_ID , false,0 ,NULL ); ret = true; }
arch/x86/kernel/cpu/resctrl/monitor.c +1 -1
@@ -219,7 +219,7 @@ static u64 mbm_overflow_count(u64 prev_msr, u64 cur_msr, unsigned int width)int resctrl_arch_rmid_read (struct rdt_resource *r,struct rdt_domain_hdr *hdr,u32 unused,u32 rmid,enum resctrl_event_id eventid, -u64 *val,void *ignored) +void *arch_priv,u64 *val,void *ignored) {int cpu =cpumask_any (&hdr->cpu_mask);struct rdt_hw_l3_mon_domain *hw_dom;
fs/resctrl/monitor.c +10 -4
@@ -137,9 +137,11 @@ void __check_limbo(struct rdt_l3_mon_domain *d, bool force_free)struct rmid_entry *entry;u32 idx, cur_idx =1 ;void *arch_mon_ctx; +void *arch_priv;bool rmid_dirty;u64 val =0 ; + arch_priv = mon_event_all[QOS_L3_OCCUP_EVENT_ID ].arch_priv; arch_mon_ctx =resctrl_arch_mon_ctx_alloc (r,QOS_L3_OCCUP_EVENT_ID );if (IS_ERR (arch_mon_ctx)) { pr_warn_ratelimited("Failed to allocate monitor context: %ld",
@@ -160,7 +162,7 @@ void __check_limbo(struct rdt_l3_mon_domain *d, bool force_free) entry =__rmid_entry (idx);if (resctrl_arch_rmid_read (r, &d->hdr, entry->closid, entry->rmid, -QOS_L3_OCCUP_EVENT_ID , &val, +QOS_L3_OCCUP_EVENT_ID , arch_priv, &val, arch_mon_ctx)) { rmid_dirty = true; }else {
@@ -411,7 +413,8 @@ static int __mon_event_count(u32 closid, u32 rmid, struct rmid_read *rr)if (rr->hdr) {/* Single domain. */ rr->err =resctrl_arch_rmid_read (rr->r, rr->hdr, closid, rmid, - rr->evt->evtid, &tval, rr->arch_mon_ctx); + rr->evt->evtid, rr->evt->arch_priv, + &tval, rr->arch_mon_ctx);if (rr->err)return rr->err;
@@ -434,7 +437,8 @@ static int __mon_event_count(u32 closid, u32 rmid, struct rmid_read *rr)if (d->ci_id != rr->ci_id)continue ; err =resctrl_arch_rmid_read (rr->r, &d->hdr, closid, rmid, - rr->evt->evtid, &tval, rr->arch_mon_ctx); + rr->evt->evtid, rr->evt->arch_priv, + &tval, rr->arch_mon_ctx);if (!err) { rr->val += tval; ret =0 ;
@@ -906,7 +910,8 @@ struct mon_evt mon_event_all[QOS_NUM_EVENTS] = { MON_EVENT(PMT_EVENT_UOPS_RETIRED, "uops_retired", RDT_RESOURCE_PERF_PKG, false), }; -void resctrl_enable_mon_event (enum resctrl_event_id eventid,bool any_cpu,unsigned int binary_bits) +void resctrl_enable_mon_event (enum resctrl_event_id eventid,bool any_cpu, +unsigned int binary_bits,void *arch_priv) {if (WARN_ON_ONCE (eventid <QOS_FIRST_EVENT || eventid >=QOS_NUM_EVENTS || binary_bits >MAX_BINARY_BITS ))
@@ -922,6 +927,7 @@ void resctrl_enable_mon_event(enum resctrl_event_id eventid, bool any_cpu, unsig mon_event_all[eventid].any_cpu = any_cpu; mon_event_all[eventid].binary_bits = binary_bits; + mon_event_all[eventid].arch_priv = arch_priv; mon_event_all[eventid].enabled = true; }
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 21/32] x86,fs/resctrl: Add architectural event pointer
Hi Tony,
Quoted 5 lines · Tony Luck
The resctrl file system layer passes the domain, RMID, and event id to
resctrl_arch_rmid_read()to fetch an event counter.For some resources this is not enough information to efficiently access the counter. Fetching a telemetry event counter requires additional
The vague first sentence can now be dropped.
Quoted 11 lines
information that is private to the architecture, for example, the offset into MMIO space from where counter should be read.
Add
mon_evt::arch_privvoid pointer. Architecture code can initialize this when marking each event enabled.File system code passes this pointer to
resctrl_arch_rmid_read().Suggested-by Reinette Chatre <[email protected]>Signed-off-by Tony Luck <[email protected]>---
Reinette
Tony Luck
maintainerPATCH v8 22/32 x86/resctrl: Read telemetry events
In reply to Tony LuckTelemetry events are enumerated by the INTEL_PMT_TELEMETRY subsystem. resctrl enables events with resctrl_enable_mon_event() passing a pointer to the pmt_event structure for the event within the struct event_group. The file system stores it in mon_evt::arch_priv.
Add a check to resctrl_arch_rmid_read() for resource id RDT_RESOURCE_PERF_PKG and directly call intel_aet_read_event() passing the enum resctrl_event_id for the event and the arch_priv pointer that was supplied when the event was enabled.
There may be multiple aggregators tracking each package, so scan all of them and add up all counters.
Resctrl now uses readq() so depends on X86_64. Update Kconfig.
--- arch/x86/kernel/cpu/resctrl/internal.h | 7 ++++ arch/x86/kernel/cpu/resctrl/intel_aet.c | 44 +++++++++++++++++++++++++ arch/x86/kernel/cpu/resctrl/monitor.c | 3 ++ arch/x86/Kconfig | 2 +- 4 files changed, 55 insertions(+), 1 deletion(-)
arch/x86/kernel/cpu/resctrl/internal.h +7 -0
@@ -172,9 +172,16 @@ void rdt_domain_reconfigure_cdp(struct rdt_resource *r);#ifdef CONFIG_X86_CPU_RESCTRL_INTEL_AET bool intel_aet_get_events (void ); void __exit intel_aet_exit(void); +int intel_aet_read_event (int domid,int rmid,enum resctrl_event_id evtid, +void *arch_priv,u64 *val);#else static inline bool intel_aet_get_events (void ) {return false; } static inline void __exit intel_aet_exit(void) { } +static inline int intel_aet_read_event (int domid,int rmid,enum resctrl_event_id evtid, +void *arch_priv,u64 *val) +{ +return -EINVAL ; +}#endif #endif /* _ASM_X86_RESCTRL_INTERNAL_H */
arch/x86/kernel/cpu/resctrl/intel_aet.c +44 -0
59 lines not on this page · raw message
arch/x86/kernel/cpu/resctrl/monitor.c +3 -0
@@ -232,6 +232,9 @@ int resctrl_arch_rmid_read(struct rdt_resource *r, struct rdt_domain_hdr *hdr,resctrl_arch_rmid_read_context_check (); +if (r->rid ==RDT_RESOURCE_PERF_PKG ) +return intel_aet_read_event (hdr->id, rmid, eventid, arch_priv, val); +if (r->rid !=RDT_RESOURCE_L3 )return -EINVAL ;
arch/x86/Kconfig +1 -1
@@ -527,7 +527,7 @@ config X86_CPU_RESCTRL config X86_CPU_RESCTRL_INTEL_AET bool "Intel Application Energy Telemetry" if INTEL_PMT_TELEMETRY=y && INTEL_TPMI=y - depends on X86_CPU_RESCTRL && CPU_SUP_INTEL + depends on X86_64 && X86_CPU_RESCTRL && CPU_SUP_INTEL help Enable per-RMID telemetry events in resctrl
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 22/32] x86/resctrl: Read telemetry events
Hi Tony,
Subject: "x86/resctrl: Enable and read telemetry events"?
Quoted 1 line · Tony Luck
Telemetry events are enumerated by the
INTEL_PMT_TELEMETRYsubsystem.
Above is the context but does not actually describe what this patch builds on. Below is something to start working from:
The active event groups are known after matching the known event groups with the system's telemetry events enumerated by the INTEL_PMT_TELEMETRY subsystem.
Enable the active events in resctrl filesystem to make them available to user space. Pass a pointer to the pmt_event structure of the event within the struct event_group that resctrl stores in mon_evt::arch_priv. resctrl passes this pointer back when asking to read the event data which enables the data to be found in MMIO.
...
Quoted 11 lines
resctrl enables events with
resctrl_enable_mon_event()passing a pointer to thepmt_eventstructure for the event within the structevent_group. The file system stores it inmon_evt::arch_priv.Add a check to
resctrl_arch_rmid_read()for resource idRDT_RESOURCE_PERF_PKGand directly callintel_aet_read_event()passing the enumresctrl_event_idfor the event and thearch_privpointer that was supplied when the event was enabled.There may be multiple aggregators tracking each package, so scan all of them and add up all counters.
As mentioned below it is possible for some aggregators to not return valid data and this is treated as a success. User will not be aware when this happens. What is likelihood of this happening? Should user be made aware when this happens?
Quoted 5 lines
Resctrl now uses
readq()so depends onX86_64. UpdateKconfig.Signed-off-by Tony Luck <[email protected]>---
...
Review static int discover_events(struct event_group *e, struct pmt_feature_group *p)
Quoted 2 lines
(quoted diff) +0
-0@@ -211,6 +212,9 @@ static int discover_events(struct event_group *e, struct pmt_feature_group *p)
Recurring feedback to this series is that in the beginning of the series discover_events() gets function comments the describes the "steps" of discover ... but later in series (like in this patch) when discover_events() is updated these comments/steps are no longer updated.
Looking at the final work discover_events() thus has function comments with only two steps that document part of what it does.
I actually find the comments within the function that describes what an associated snippet does more helpful than lumping everything at top of function in a list. For example, below change can get a comment like:
/*
* Enable all events of active event group. Pass pointer to event's struct pmt_event
* as private data that resctrl fs includes when it requests to read the counter. */
Quoted 10 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +3
-0list_add (&e->list, &active_event_groups); +for (int i =0 ; i < e->num_events; i++) +resctrl_enable_mon_event (e->evts[i].id, true, e->evts[i].bin_bits, &e->evts[i]); +return 0 ; }
arch/x86/kernel/cpu/resctrl/intel_aet.c void __exit intel_aet_exit(void) · line 291
Quoted 10 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +7
-0@@ -278,3 +282,43 @@ void __exit intel_aet_exit(void)list_del (&evg->list); } } + +#define DATA_VALID BIT_ULL(63) +#define DATA_BITS GENMASK_ULL(62, 0) + +/* +* Read counter for an event on a domain (summing all aggregators +* on the domain).
Function comment can highlight that it is intentional that as long as at least one aggregator returns valid data the read is considered a success with the possibility that partial data may be returned to user space without user being aware.
Quoted 23 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +23
-0+*/ +int intel_aet_read_event (int domid,int rmid,enum resctrl_event_id eventid, +void *arch_priv,u64 *val) +{ +struct pmt_event *pevt = arch_priv; +struct pkg_mmio_info *mmi; +struct event_group *e; +bool valid = false; +u64 evtcount; +void *pevt0; +int idx; + + pevt0 = pevt - pevt->idx; + e = container_of(pevt0, struct event_group, evts); + idx = rmid * e->num_events; + idx += pevt->idx; + mmi = e->pkginfo[domid]; + +if (idx *sizeof (u64) +sizeof (u64) > e->mmio_size) { +pr_warn_once ("MMIO index %d out of range\n" , idx); +return -EIO ; + } +
arch/x86/kernel/cpu/resctrl/intel_aet.c void __exit intel_aet_exit(void) · line 324
Quoted 10 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +10
-0+for (int i =0 ; i < mmi->num_regions; i++) { + evtcount =readq (mmi->addrs[i] + idx *sizeof (u64)); +if (!(evtcount &DATA_VALID )) +continue ; + *val += evtcount &DATA_BITS ; + valid = true; + } + +return valid ?0 : -EINVAL ; +}
Reinette
Tony Luck
maintainerPATCH v8 23/32 x86/resctrl: Handle domain creation/deletion for RDT_RESOURCE_PERF_PKG
In reply to Tony LuckThe L3 resource has several requirements for domains. There are structures that hold the 64-bit values of counters, and elements to keep track of the overflow and limbo threads.
None of these are needed for the PERF_PKG resource. The hardware counters are wide enough that they do not wrap around for decades.
Define a new rdt_perf_pkg_mon_domain structure which just consists of the standard rdt_domain_hdr to keep track of domain id and CPU mask.
Add a case RDT_RESOURCE_PERF_PKG to domain_add_cpu_mon() to call intel_aet_setup_mon_domain() to allocate and initialize the rdt_perf_pkg_mon_domain structure.
Also add a case to domain_remove_cpu_mon() cleanup when the last CPU of a domain is removed.
--- arch/x86/kernel/cpu/resctrl/internal.h | 13 +++++++++++++ arch/x86/kernel/cpu/resctrl/core.c | 9 +++++++++ arch/x86/kernel/cpu/resctrl/intel_aet.c | 24 ++++++++++++++++++++++++ 3 files changed, 46 insertions(+)
arch/x86/kernel/cpu/resctrl/internal.h +13 -0
@@ -75,6 +75,14 @@ static inline struct rdt_hw_l3_mon_domain *resctrl_to_arch_mon_dom(struct rdt_l3 return container_of(r, struct rdt_hw_l3_mon_domain, d_resctrl); } +/** +* struct rdt_perf_pkg_mon_domain - CPUs sharing an package scoped resctrl monitor resource +* @hdr: common header for different domain types +*/ +struct rdt_perf_pkg_mon_domain { +struct rdt_domain_hdr hdr; +}; +/** * struct msr_param - set a range of MSRs from a domain * @res: The resource to use
@@ -174,6 +182,8 @@ bool intel_aet_get_events(void); void __exit intel_aet_exit(void);int intel_aet_read_event (int domid,int rmid,enum resctrl_event_id evtid,void *arch_priv,u64 *val); +void intel_aet_setup_mon_domain (int cpu,int id,struct rdt_resource *r, +struct list_head *add_pos);#else static inline bool intel_aet_get_events (void ) {return false; } static inline void __exit intel_aet_exit(void) { }
@@ -182,6 +192,9 @@ static inline int intel_aet_read_event(int domid, int rmid, enum resctrl_event_i {return -EINVAL ; } + +static inline void intel_aet_setup_mon_domain (int cpu,int id,struct rdt_resource *r, +struct list_head *add_pos) { }#endif #endif /* _ASM_X86_RESCTRL_INTERNAL_H */
arch/x86/kernel/cpu/resctrl/core.c +9 -0
@@ -574,6 +574,9 @@ static void domain_add_cpu_mon(int cpu, struct rdt_resource *r)case RDT_RESOURCE_L3 :l3_mon_domain_setup (cpu, id, r, add_pos);break ; +case RDT_RESOURCE_PERF_PKG : +intel_aet_setup_mon_domain (cpu, id, r, add_pos); +break ;default :WARN_ON_ONCE (1 );break ;
@@ -671,6 +674,12 @@ static void domain_remove_cpu_mon(int cpu, struct rdt_resource *r)synchronize_rcu ();l3_mon_domain_free (hw_dom);break ; +case RDT_RESOURCE_PERF_PKG : +resctrl_offline_mon_domain (r, hdr); +list_del_rcu (&hdr->list); +synchronize_rcu (); +kfree (container_of (hdr ,struct rdt_perf_pkg_mon_domain ,hdr )); +break ;default :pr_warn_once ("Unknown resource rid=%d\n" , r->rid);break ;
arch/x86/kernel/cpu/resctrl/intel_aet.c +24 -0
@@ -322,3 +322,27 @@ int intel_aet_read_event(int domid, int rmid, enum resctrl_event_id eventid,return valid ?0 : -EINVAL ; } + +void intel_aet_setup_mon_domain (int cpu,int id,struct rdt_resource *r, +struct list_head *add_pos) +{ +struct rdt_perf_pkg_mon_domain *d; +int err; + + d =kzalloc_node (sizeof (*d),GFP_KERNEL ,cpu_to_node (cpu)); +if (!d) +return ; + + d->hdr.id = id; + d->hdr.type =RESCTRL_MON_DOMAIN ; + d->hdr.rid = r->rid; +cpumask_set_cpu (cpu, &d->hdr.cpu_mask); +list_add_tail_rcu (&d->hdr.list, add_pos); + + err =resctrl_online_mon_domain (r, &d->hdr); +if (err) { +list_del_rcu (&d->hdr.list); +synchronize_rcu (); +kfree (d); + } +}
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 23/32] x86/resctrl: Handle domain creation/deletion for RDT_RESOURCE_PERF_PKG
Hi Tony,
Quoted 1 line · Tony Luck
The L3 resource has several requirements for domains. There are structures
"There are structures" -> "There are per domain structures ..."? (to help connect with new domain structure later)
Quoted 6 lines
that hold the 64-bit values of counters, and elements to keep track of the overflow and limbo threads.
None of these are needed for the
PERF_PKGresource. The hardware counters are wide enough that they do not wrap around for decades.
Quoted 8 lines
Define a new
rdt_perf_pkg_mon_domainstructure which just consists of the standardrdt_domain_hdrto keep track of domain id and CPU mask.Add a case
RDT_RESOURCE_PERF_PKGtodomain_add_cpu_mon()to callintel_aet_setup_mon_domain()to allocate and initialize therdt_perf_pkg_mon_domainstructure.Also add a case to
domain_remove_cpu_mon()cleanup when the last
"cleanup" -" to clean up" ?
Regarding the "Add a case" usage ... you need not document the actual code changes in such detail, that can be seen from the patch. Just describing what the patch does on high level is sufficient.
For example,
Support the PERF_PKG resource in the CPU online/offline handlers.
Allocate and initialize the rdt_perf_pkg_mon_domain structure when the first CPU of a domain comes online and do necessary cleanup when the last CPU of a domain goes offline.
Quoted 4 lines
CPU of a domain is removed.
Signed-off-by Tony Luck <[email protected]>---
Reinette
Tony Luck
maintainerPATCH v8 24/32 x86/resctrl: Add energy/perf choices to rdt boot option
In reply to Tony LuckLegacy resctrl features are enumerated by X86_FEATURE_* flags. These may be overridden by quirks to disable features in the case of errata.
Users can use kernel command line options to either disable a feature, or to force enable a feature that was disabled by a quirk.
Provide similar functionality for hardware features that do not have an X86_FEATURE_* flag.
Unlike other features that are tied to X86_FEATURE_* flags, these must be queried by name. Add rdt_is_feature_enabled() to check whether quirks or kernel command line have disabled a feature. Just like the legacy features the command line enable overrides quirk disable.
--- .../admin-guide/kernel-parameters.txt | 2 +- arch/x86/kernel/cpu/resctrl/internal.h | 2 ++ arch/x86/kernel/cpu/resctrl/core.c | 30 +++++++++++++++++++ 3 files changed, 33 insertions(+), 1 deletion(-)
Documentation/admin-guide/kernel-parameters.txt +1 -1
@@ -6154,7 +6154,7 @@ rdt= [HW,X86,RDT] Turn on/off individual RDT features. List is: cmt, mbmtotal, mbmlocal, l3cat, l3cdp, l2cat, l2cdp, - mba, smba, bmec. + mba, smba, bmec, energy, perf. E.g. to turn on cmt and turn off mba use: rdt=cmt,!mba
arch/x86/kernel/cpu/resctrl/internal.h +2 -0
@@ -177,6 +177,8 @@ void __init intel_rdt_mbm_apply_quirk(void);void rdt_domain_reconfigure_cdp (struct rdt_resource *r); +bool rdt_is_feature_enabled (char *name); +#ifdef CONFIG_X86_CPU_RESCTRL_INTEL_AET bool intel_aet_get_events (void ); void __exit intel_aet_exit(void);
arch/x86/kernel/cpu/resctrl/core.c +30 -0
@@ -760,6 +760,8 @@ enum {RDT_FLAG_MBA ,RDT_FLAG_SMBA ,RDT_FLAG_BMEC , +RDT_FLAG_ENERGY , + RDT_FLAG_PERF, };#define RDT_OPT (idx, n, f) \
@@ -785,6 +787,8 @@ static struct rdt_options rdt_options[] __ro_after_init = {RDT_OPT (RDT_FLAG_MBA ,"mba" ,X86_FEATURE_MBA ),RDT_OPT (RDT_FLAG_SMBA ,"smba" ,X86_FEATURE_SMBA ),RDT_OPT (RDT_FLAG_BMEC ,"bmec" ,X86_FEATURE_BMEC ), +RDT_OPT (RDT_FLAG_ENERGY ,"energy" ,0 ), + RDT_OPT(RDT_FLAG_PERF, "perf", 0), };#define NUM_RDT_OPTIONS ARRAY_SIZE(rdt_options)
@@ -834,6 +838,32 @@ bool rdt_cpu_has(int flag)return ret; } +/* +* Hardware features that do not have X86_FEATURE_* bits. +* There is no "hardware does not support this at all" case. +* Assume that the caller has already determined that hardware +* support is present and just needs to check if the feature has been +* disabled by a quirk that has not been overridden by a command +* line option. +*/ +bool rdt_is_feature_enabled (char *name) +{ +struct rdt_options *o; +bool ret = true; + +for (o = rdt_options; o < &rdt_options[NUM_RDT_OPTIONS ]; o++) { +if (!strcmp (name, o->name)) { +if (o->force_off) + ret = false; +if (o->force_on) + ret = true; +break ; + } + } + +return ret; +} +bool resctrl_arch_is_evt_configurable (enum resctrl_event_id evt) {if (!rdt_cpu_has (X86_FEATURE_BMEC ))
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 24/32] x86/resctrl: Add energy/perf choices to rdt boot option
Hi Tony,
Quoted 6 lines · Tony Luck
Legacy resctrl features are enumerated by X86_FEATURE_* flags. These may be overridden by quirks to disable features in the case of errata.
Users can use kernel command line options to either disable a feature, or to force enable a feature that was disabled by a quirk.
Quoted 7 lines
Provide similar functionality for hardware features that do not have an X86_FEATURE_* flag.
Unlike other features that are tied to X86_FEATURE_* flags, these must be queried by name. Add
rdt_is_feature_enabled()to check whether quirks or kernel command line have disabled a feature. Just like the legacy features the command line enable overrides quirk disable.
I am not able to parse the last sentence.
Quoted 3 lines
Signed-off-by Tony Luck <[email protected]>---
Reinette
Tony Luck
maintainerPATCH v8 25/32 x86/resctrl: Handle number of RMIDs supported by telemetry resources
In reply to Tony LuckThere are now three meanings for "number of RMIDs":
1) The number for legacy features enumerated by CPUID leaf 0xF. This is the maximum number of distinct values that can be loaded into the IA32_PQR_ASSOC MSR. Note that systems with Sub-NUMA Cluster mode enabled will force scaling down the CPUID enumerated value by the number of SNC nodes per L3-cache.
2) The number of registers in MMIO space for each event. This is enumerated in the XML files and is the value initialized into event_group::num_rmids. This will be overwritten with a lower value if hardware does not support all these registers at the same time (see next case).
3) The number of "hardware counters" (this isn't a strictly accurate description of how things work, but serves as a useful analogy that does describe the limitations) feeding to those MMIO registers. This is enumerated in telemetry_region::num_rmids returned from the call to intel_pmt_get_regions_by_feature()
Event groups with insufficient "hardware counters" to track all RMIDs are difficult for users to use, since the system may reassign "hardware counters" at any time. This means that users cannot reliably collect two consecutive event counts to compute the rate at which events are occurring.
Use rdt_set_feature_disabled() to mark any under-resourced event groups (those with telemetry_region::num_rmids < event_group::num_rmids) as unusable. Note that the rdt_options[] structure must now be writable at run-time. The request to disable will be overridden if the user explicitly requests to enable using the "rdt=" Linux boot argument.
Scan all enabled event groups and assign the RDT_RESOURCE_PERF_PKG resource "num_rmids" value to the smallest of these values as this value will be used later to compare against the number of RMIDs supported by other resources.
N.B. Changed type of rdt_resource::num_rmid to u32 to match type of event_group::num_rmids so that min(r->num_rmid, e->num_rmids) won't complain about mixing signed and unsigned types. Print r->num_rmid as unsigned value in rdt_num_rmids_show().
--- include/linux/resctrl.h | 2 +- arch/x86/kernel/cpu/resctrl/internal.h | 2 ++ arch/x86/kernel/cpu/resctrl/core.c | 18 ++++++++++- arch/x86/kernel/cpu/resctrl/intel_aet.c | 43 +++++++++++++++++++++++++ fs/resctrl/rdtgroup.c | 2 +- 5 files changed, 64 insertions(+), 3 deletions(-)
include/linux/resctrl.h +1 -1
@@ -288,7 +288,7 @@ struct rdt_resource {int rid;bool alloc_capable;bool mon_capable; -int num_rmid; +u32 num_rmid;enum resctrl_scope ctrl_scope;enum resctrl_scope mon_scope;struct resctrl_cache cache;
arch/x86/kernel/cpu/resctrl/internal.h +2 -0
@@ -179,6 +179,8 @@ void rdt_domain_reconfigure_cdp(struct rdt_resource *r);bool rdt_is_feature_enabled (char *name); +void rdt_set_feature_disabled (char *name); +#ifdef CONFIG_X86_CPU_RESCTRL_INTEL_AET bool intel_aet_get_events (void ); void __exit intel_aet_exit(void);
arch/x86/kernel/cpu/resctrl/core.c +17 -1
@@ -776,7 +776,7 @@ struct rdt_options {bool force_off, force_on; }; -static struct rdt_options rdt_options[]__ro_after_init = { +static struct rdt_options rdt_options[] = {RDT_OPT (RDT_FLAG_CMT ,"cmt" ,X86_FEATURE_CQM_OCCUP_LLC ),RDT_OPT (RDT_FLAG_MBM_TOTAL ,"mbmtotal" ,X86_FEATURE_CQM_MBM_TOTAL ),RDT_OPT (RDT_FLAG_MBM_LOCAL ,"mbmlocal" ,X86_FEATURE_CQM_MBM_LOCAL ),
@@ -838,6 +838,22 @@ bool rdt_cpu_has(int flag)return ret; } +/* +* Can be called during feature enumeration if sanity check of +* a feature's parameters indicates problems with the feature. +*/ +void rdt_set_feature_disabled (char *name) +{ +struct rdt_options *o; + +for (o = rdt_options; o < &rdt_options[NUM_RDT_OPTIONS ]; o++) { +if (!strcmp (name, o->name)) { + o->force_off = true; +return ; + } + } +} +/* * Hardware features that do not have X86_FEATURE_* bits. * There is no "hardware does not support this at all" case.
arch/x86/kernel/cpu/resctrl/intel_aet.c +43 -0
117 lines not on this page · raw message
fs/resctrl/rdtgroup.c +1 -1
@@ -1135,7 +1135,7 @@ static int rdt_num_rmids_show(struct kernfs_open_file *of, {struct rdt_resource *r =rdt_kn_parent_priv (of->kn); -seq_printf (seq,"%d\n" , r->num_rmid); +seq_printf (seq,"%u\n" , r->num_rmid);return 0 ; }
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 25/32] x86/resctrl: Handle number of RMIDs supported by telemetry resources
Hi Tony,
Quoted 8 lines · Tony Luck
There are now three meanings for "number of RMIDs":
1) The number for legacy features enumerated by CPUID leaf
0xF. This is the maximum number of distinct values that can be loaded into theIA32_PQR_ASSOCMSR. Note that systems with Sub-NUMA Cluster mode enabled will force scaling down the CPUID enumerated value by the number of SNC nodes per L3-cache.
Quoted 5 lines
2) The number of registers in MMIO space for each event. This is enumerated in the XML files and is the value initialized into
event_group::num_rmids. This will be overwritten with a lower value if hardware does not support all these registers at the same time (see next case).
I think the "This will be overwritten ..." should be dropped. It is not always overwritten and the later part of changelog describes these details. This part is just to introduce the different meanings of RMIDs.
Quoted 13 lines
3) The number of "hardware counters" (this isn't a strictly accurate description of how things work, but serves as a useful analogy that does describe the limitations) feeding to those MMIO registers. This is enumerated in
telemetry_region::num_rmidsreturned from the call tointel_pmt_get_regions_by_feature()Event groups with insufficient "hardware counters" to track all RMIDs are difficult for users to use, since the system may reassign "hardware counters" at any time. This means that users cannot reliably collect two consecutive event counts to compute the rate at which events are occurring.
Quoted 4 lines
Use
rdt_set_feature_disabled()to mark any under-resourced event groups (those withtelemetry_region::num_rmids<event_group::num_rmids) as unusable. Note that the rdt_options[] structure must now be writable at run-time. The request to disable will be overridden if the user
"The request to disable will be overridden ..." -> "User can force an under-resourced event group to be usable using the "rdt=" Linux boot parameter. In this case, reduce the number of RMIDs supported by the event group to be the number of RMIDs of the telemetry region."?
Quoted 8 lines
explicitly requests to enable using the "rdt=" Linux boot argument.
Scan all enabled event groups and assign the
RDT_RESOURCE_PERF_PKGresource "num_rmids" value to the smallest of these values as this value will be used later to compare against the number of RMIDs supported by other resources.N.B. Changed type of
rdt_resource::num_rmidto u32 to match type of
Changed -> Change
Quoted 89 lines
event_group::num_rmidsso thatmin(r->num_rmid, e->num_rmids)won't complain about mixing signed and unsigned types. Printr->num_rmidas unsigned value inrdt_num_rmids_show().Signed-off-by Tony Luck <[email protected]>--- include/linux/resctrl.h | 2 +- arch/x86/kernel/cpu/resctrl/internal.h | 2 ++ arch/x86/kernel/cpu/resctrl/core.c | 18 ++++++++++- arch/x86/kernel/cpu/resctrl/intel_aet.c | 43 +++++++++++++++++++++++++ fs/resctrl/rdtgroup.c | 2 +- 5 files changed, 64 insertions(+), 3 deletions(-)include/linux/resctrl.h +1
-1@@ -288,7 +288,7 @@ struct rdt_resource {int rid;bool alloc_capable;bool mon_capable; -int num_rmid; +u32 num_rmid;enum resctrl_scope ctrl_scope;enum resctrl_scope mon_scope;struct resctrl_cache cache;arch/x86/kernel/cpu/resctrl/internal.h +2
-0@@ -179,6 +179,8 @@ void rdt_domain_reconfigure_cdp(struct rdt_resource *r);bool rdt_is_feature_enabled (char *name); +void rdt_set_feature_disabled (char *name); +#ifdef CONFIG_X86_CPU_RESCTRL_INTEL_AET bool intel_aet_get_events (void ); void __exit intel_aet_exit(void);arch/x86/kernel/cpu/resctrl/core.c +17
-1@@ -776,7 +776,7 @@ struct rdt_options {bool force_off, force_on; }; -static struct rdt_options rdt_options[]__ro_after_init = { +static struct rdt_options rdt_options[] = {RDT_OPT (RDT_FLAG_CMT ,"cmt" ,X86_FEATURE_CQM_OCCUP_LLC ),RDT_OPT (RDT_FLAG_MBM_TOTAL ,"mbmtotal" ,X86_FEATURE_CQM_MBM_TOTAL ),RDT_OPT (RDT_FLAG_MBM_LOCAL ,"mbmlocal" ,X86_FEATURE_CQM_MBM_LOCAL ),@@ -838,6 +838,22 @@ bool rdt_cpu_has(int flag)return ret; } +/* +* Can be called during feature enumeration if sanity check of +* a feature's parameters indicates problems with the feature. +*/ +void rdt_set_feature_disabled (char *name) +{ +struct rdt_options *o; + +for (o = rdt_options; o < &rdt_options[NUM_RDT_OPTIONS ]; o++) { +if (!strcmp (name, o->name)) { + o->force_off = true; +return ; + } + } +} +/* * Hardware features that do not have X86_FEATURE_* bits. * There is no "hardware does not support this at all" case. arch/x86/kernel/cpu/resctrl/intel_aet.c +1
-0@@ -15,6 +15,7 @@#include <linux/cpu.h> #include <linux/intel_vsec.h> #include <linux/io.h> +#include <linux/minmax.h> #include <linux/resctrl.h> #include <linux/slab.h> @@ -50,24 +51,30 @@ struct pmt_event {
arch/x86/kernel/cpu/resctrl/intel_aet.c struct pmt_event { · line 61
Quoted 10 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +2
-0/** * struct event_group - All information about a group of telemetry events. +* @name: Name for this group (used by boot rdt= option) * @pfg: Points to the aggregated telemetry space information * within the OOBMSM driver that contains data for all * telemetry regions. * @list: Member of active_event_groups. * @pkginfo: Per-package MMIO addresses of telemetry regions belonging to this group. * @guid: Unique number per XML description file. +* @num_rmids: Number of RMIDS supported by this group. Adjusted downwards
RMIDS -> RMIDs
"Adjusted downwards ..." -> "May be adjusted downwards ..." (it is not always adjusted, only when user insists, no?)
Quoted 40 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +8
-0+* if enumeration from intel_pmt_get_regions_by_feature() indicates +* fewer RMIDs can be tracked simultaneously. * @mmio_size: Number of bytes of MMIO registers for this group. * @num_events: Number of events in this group. * @evts: Array of event descriptors. */ struct event_group {/* Data fields for additional structures to manage this group. */ +char *name;struct pmt_feature_group *pfg;struct list_head list;struct pkg_mmio_info **pkginfo;/* Remaining fields initialized from XML file. */ u32 guid; +u32 num_rmids;size_t mmio_size;unsigned int num_events; struct pmt_event evts[] __counted_by(num_events);@@ -84,7 +91,9 @@ static LIST_HEAD(active_event_groups);* File: xml/CWF/OOBMSM/RMID-ENERGY/cwf_aggregator.xml */ static struct event_group energy_0x26696143 = { + .name ="energy" , .guid =0x26696143 , + .num_rmids =576 , .mmio_size =XML_MMIO_SIZE (576 ,2 ,3 ), .num_events =2 , .evts = {@@ -98,7 +107,9 @@ static struct event_group energy_0x26696143 = {* File: xml/CWF/OOBMSM/RMID-PERF/cwf_aggregator.xml */ static struct event_group perf_0x26557651 = { + .name ="perf" , .guid =0x26557651 , + .num_rmids =576 , .mmio_size =XML_MMIO_SIZE (576 ,7 ,3 ), .num_events =7 , .evts = {
arch/x86/kernel/cpu/resctrl/intel_aet.c static bool skip_this_region(struct telemetry_region *tr, struct event_group *e) · line 151
Quoted 4 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +1
-0@@ -137,6 +148,22 @@ static bool skip_this_region(struct telemetry_region *tr, struct event_group *e)return false; } +static bool check_rmid_count (struct event_group *e,struct pmt_feature_group *p)
I think the function name can be made more helpful, how about:all_regions_have_sufficient_rmid()?
Quoted 20 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +15
-0+{ +struct telemetry_region *tr; + +for (int i =0 ; i < p->count; i++) { + tr = &p->regions[i]; +if (skip_this_region (tr, e)) +continue ; + +if (tr->num_rmids < e->num_rmids) +return false; + } + +return true; +} +static void free_pkg_mmio_info (struct pkg_mmio_info **mmi) {int num_pkgs =topology_max_packages ();@@ -159,12 +186,21 @@ DEFINE_FREE(pkg_mmio_info, struct pkg_mmio_info **, free_pkg_mmio_info(_T))*/
arch/x86/kernel/cpu/resctrl/intel_aet.c DEFINE_FREE(pkg_mmio_info, struct pkg_mmio_info **, free_pkg_mmio_info(_T)) · line 196
Quoted 10 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +2
-0static int discover_events (struct event_group *e,struct pmt_feature_group *p) { +struct rdt_resource *r = &rdt_resources_all[RDT_RESOURCE_PERF_PKG ].r_resctrl; struct pkg_mmio_info **pkginfo __free(pkg_mmio_info) = NULL; int *pkgcounts __free(kfree) = NULL;struct telemetry_region *tr;struct pkg_mmio_info *mmi;int num_pkgs; +/* Potentially disable feature if insufficient RMIDs */
"Potentially disable" -> "Disable"
Quoted 11 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +7
-0+if (!check_rmid_count (e, p)) +rdt_set_feature_disabled (e->name); + +/* User can override above disable from kernel command line */ +if (!rdt_is_feature_enabled (e->name)) +return -EINVAL ; + num_pkgs =topology_max_packages ();/* Get per-package counts of telemetry regions for this event group */
arch/x86/kernel/cpu/resctrl/intel_aet.c static int discover_events(struct event_group *e, struct pmt_feature_group *p) · line 211
Quoted 3 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +0
-0@@ -173,6 +209,8 @@ static int discover_events(struct event_group *e, struct pmt_feature_group *p)if (skip_this_region (tr, e))continue ;
Would a comment like below be valid? If so, I think it will be useful.
/* e->num_rmids only adjusted lower if user forces an unusable region to be usable */
Quoted 6 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +2
-0+ e->num_rmids =min (e->num_rmids, tr->num_rmids); +if (!pkgcounts) { pkgcounts =kcalloc (num_pkgs,sizeof (*pkgcounts),GFP_KERNEL );if (!pkgcounts)
arch/x86/kernel/cpu/resctrl/intel_aet.c static int discover_events(struct event_group *e, struct pmt_feature_group *p) · line 260
Quoted 8 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +5
-0@@ -215,6 +253,11 @@ static int discover_events(struct event_group *e, struct pmt_feature_group *p)for (int i =0 ; i < e->num_events; i++)resctrl_enable_mon_event (e->evts[i].id, true, e->evts[i].bin_bits, &e->evts[i]); +if (r->num_rmid) + r->num_rmid =min (r->num_rmid, e->num_rmids); +else + r->num_rmid = e->num_rmids; +
Another step in the discover_events() function comments?
arch/x86/kernel/cpu/resctrl/intel_aet.c static int discover_events(struct event_group *e, struct pmt_feature_group *p) · line 262
Quoted 2 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +0
-0return 0 ; }
Reinette
Tony Luck
maintainerPATCH v8 26/32 fs/resctrl: Move allocation/free of closid_num_dirty_rmid
In reply to Tony Luckclosid_num_dirty_rmid[] is allocated in dom_data_init() and freed by dom_data_exit() giving it the same life cycle as rmid_ptrs[].
Move the alloc/free out to resctrl_mon_l3_resource_init() and resctrl_mon_l3_resource_exit() in preparation for rmid_ptrs[] to be allocated on resctrl mount in support of the new telemetry events.
--- fs/resctrl/monitor.c | 56 ++++++++++++++++++++++---------------------- 1 file changed, 28 insertions(+), 28 deletions(-)
fs/resctrl/monitor.c +28 -28
@@ -805,36 +805,14 @@ void mbm_setup_overflow_handler(struct rdt_l3_mon_domain *dom, unsigned long delstatic int dom_data_init (struct rdt_resource *r) {u32 idx_limit =resctrl_arch_system_num_rmid_idx (); -u32 num_closid =resctrl_arch_get_num_closid (r);struct rmid_entry *entry =NULL ;int err =0 , i;u32 idx;mutex_lock (&rdtgroup_mutex); -if (IS_ENABLED (CONFIG_RESCTRL_RMID_DEPENDS_ON_CLOSID )) { -u32 *tmp; - -/* -* If the architecture hasn't provided a sanitised value here, -* this may result in larger arrays than necessary. Resctrl will -* use a smaller system wide value based on the resources in -* use. -*/ - tmp =kcalloc (num_closid,sizeof (*tmp),GFP_KERNEL ); -if (!tmp) { - err = -ENOMEM ; - goto out_unlock; - } - - closid_num_dirty_rmid = tmp; - } rmid_ptrs =kcalloc (idx_limit,sizeof (struct rmid_entry ),GFP_KERNEL );if (!rmid_ptrs) { -if (IS_ENABLED (CONFIG_RESCTRL_RMID_DEPENDS_ON_CLOSID )) { -kfree (closid_num_dirty_rmid); - closid_num_dirty_rmid =NULL ; - } err = -ENOMEM ; goto out_unlock; }
@@ -870,11 +848,6 @@ static void dom_data_exit(struct rdt_resource *r)if (!r->mon_capable) goto out_unlock; -if (IS_ENABLED (CONFIG_RESCTRL_RMID_DEPENDS_ON_CLOSID )) { -kfree (closid_num_dirty_rmid); - closid_num_dirty_rmid =NULL ; - } -kfree (rmid_ptrs); rmid_ptrs =NULL ;
@@ -957,9 +930,31 @@ int resctrl_mon_l3_resource_init(void)if (!r->mon_capable)return 0 ; +if (IS_ENABLED (CONFIG_RESCTRL_RMID_DEPENDS_ON_CLOSID )) { +u32 num_closid =resctrl_arch_get_num_closid (r); +u32 *tmp; + +/* +* If the architecture hasn't provided a sanitised value here, +* this may result in larger arrays than necessary. Resctrl will +* use a smaller system wide value based on the resources in +* use. +*/ + tmp =kcalloc (num_closid,sizeof (*tmp),GFP_KERNEL ); +if (!tmp) +return -ENOMEM ; + + closid_num_dirty_rmid = tmp; + } + ret =dom_data_init (r); -if (ret) +if (ret) { +if (IS_ENABLED (CONFIG_RESCTRL_RMID_DEPENDS_ON_CLOSID )) { +kfree (closid_num_dirty_rmid); + closid_num_dirty_rmid =NULL ; + }return ret; + }if (resctrl_arch_is_evt_configurable (QOS_L3_MBM_TOTAL_EVENT_ID )) { mon_event_all[QOS_L3_MBM_TOTAL_EVENT_ID ].configurable = true;
@@ -984,5 +979,10 @@ void resctrl_mon_l3_resource_exit(void) {struct rdt_resource *r =resctrl_arch_get_resource (RDT_RESOURCE_L3 ); +if (IS_ENABLED (CONFIG_RESCTRL_RMID_DEPENDS_ON_CLOSID )) { +kfree (closid_num_dirty_rmid); + closid_num_dirty_rmid =NULL ; + } +dom_data_exit (r); }
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 26/32] fs/resctrl: Move allocation/free of closid_num_dirty_rmid
Hi Tony,
Quoted 2 lines · Tony Luck
closid_num_dirty_rmid[] is allocated in
dom_data_init()and freed bydom_data_exit()giving it the same life cycle as rmid_ptrs[].
To help connect the current flow with the planned changes mentioned below this can be:
closid_num_dirty_rmid[] is allocated in dom_data_init() during resctrl initialization and freed by dom_data_exit() during resctrl exit giving it the same life cycle as rmid_ptrs[].
Quoted 2 lines
Move the alloc/free out to
resctrl_mon_l3_resource_init()and
"Move the alloc/free out ..." -> "Move closid_num_dirty_rmid[] alloc/free out ..."
Quoted 5 lines
resctrl_mon_l3_resource_exit()in preparation for rmid_ptrs[] to be allocated on resctrl mount in support of the new telemetry events.Signed-off-by Tony Luck <[email protected]>---
Reinette
Tony Luck
maintainerPATCH v8 27/32 fs,x86/resctrl: Compute number of RMIDs as minimum across resources
In reply to Tony Luckresctrl assumes that only the L3 resource supports monitor events, so it simply takes the rdt_resource::num_rmid from RDT_RESOURCE_L3 as the number of RMIDs.
The addition of telemetry events in a different resource breaks that assumption.
Compute the number of available RMIDs as the minimum value across all mon capable resources (analogous to how the number of CLOSIDs is computed across alloc capable resources).
Note that mount time enumeration of the telemetry resource means that this number can be reduced. If this happens, then some memory will be wasted as the allocations for rdt_l3_mon_domain::states[] will be larger than needed.
--- arch/x86/kernel/cpu/resctrl/core.c | 15 +++++++++++++-- fs/resctrl/rdtgroup.c | 5 +++++ 2 files changed, 18 insertions(+), 2 deletions(-)
arch/x86/kernel/cpu/resctrl/core.c +13 -2
@@ -110,12 +110,23 @@ struct rdt_hw_resource rdt_resources_all[RDT_NUM_RESOURCES] = { }, }; +/** +* resctrl_arch_system_num_rmid_idx - Compute number of supported RMIDs +* (minimum across all mon capable resource) +* +* Return: Number of supported RMIDs at time of call. Note that mount time +* enumeration of resources may reduce the number. +*/ u32 resctrl_arch_system_num_rmid_idx (void ) { -struct rdt_resource *r = &rdt_resources_all[RDT_RESOURCE_L3 ].r_resctrl; +u32 num_rmids =U32_MAX ; +struct rdt_resource *r; + +for_each_mon_capable_rdt_resource (r) + num_rmids =min (num_rmids, r->num_rmid);/* RMID are independent numbers for x86. num_rmid_idx == num_rmid */ -return r->num_rmid; +return num_rmids ==U32_MAX ?0 : num_rmids; }struct rdt_resource *resctrl_arch_get_resource (enum resctrl_res_level l)
fs/resctrl/rdtgroup.c +5 -0
@@ -4116,6 +4116,11 @@ void resctrl_offline_mon_domain(struct rdt_resource *r, struct rdt_domain_hdr *h* During boot this may be called before global allocations have been made by * resctrl_mon_l3_resource_init(). * +* This routine is called at resctrl init time. The number of supported RMIDs +* may be reduced if additional mon capable resources are enumerated at mount +* time. This means the rdt_l3_mon_domain::states[] allocations may be larger +* than needed. +* * Returns 0 for success, or -ENOMEM. */ static int domain_setup_l3_mon_state (struct rdt_resource *r,struct rdt_l3_mon_domain *d)
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 27/32] fs,x86/resctrl: Compute number of RMIDs as minimum across resources
Hi Tony,
Quoted 3 lines · Tony Luck
resctrl assumes that only the L3 resource supports monitor events, so it simply takes the
rdt_resource::num_rmidfromRDT_RESOURCE_L3as the number of RMIDs.
There does not seem to be anything wrong with "taking num_rmid ... as the number of RMIDs". How about:
"the number of RMIDs" -> "the system's number of RMIDs"?
Quoted 6 lines
The addition of telemetry events in a different resource breaks that assumption.
Compute the number of available RMIDs as the minimum value across all mon capable resources (analogous to how the number of CLOSIDs
"mon capable" -> "monitoring capable" or "mon_capable"
Quoted 1 line
is computed across alloc capable resources).
"alloc capable" -> "allocation capable" or "alloc_capable"
Quoted 4 lines
Note that mount time enumeration of the telemetry resource means that this number can be reduced. If this happens, then some memory will be wasted as the allocations for rdt_l3_mon_domain::states[] will be
"rdt_l3_mon_domain::states[]" -> "rdt_l3_mon_domain::mbm_states[] and rdt_l3_mon_domain::rmid_busy_llc created during resctrl initialization"
Quoted 13 lines
larger than needed.
Signed-off-by Tony Luck <[email protected]>--- arch/x86/kernel/cpu/resctrl/core.c | 15 +++++++++++++-- fs/resctrl/rdtgroup.c | 5 +++++ 2 files changed, 18 insertions(+), 2 deletions(-)arch/x86/kernel/cpu/resctrl/core.c +0
-0
arch/x86/kernel/cpu/resctrl/core.c struct rdt_hw_resource rdt_resources_all[RDT_NUM_RESOURCES] = { · line 115
Quoted 6 lines
arch/x86/kernel/cpu/resctrl/core.c +3
-0@@ -110,12 +110,23 @@ struct rdt_hw_resource rdt_resources_all[RDT_NUM_RESOURCES] = { }, }; +/** +* resctrl_arch_system_num_rmid_idx - Compute number of supported RMIDs +* (minimum across all mon capable resource)
"mon capable" -> "monitoring capable" or "mon_capable"
Quoted 24 lines
arch/x86/kernel/cpu/resctrl/core.c +10
-2+* +* Return: Number of supported RMIDs at time of call. Note that mount time +* enumeration of resources may reduce the number. +*/ u32 resctrl_arch_system_num_rmid_idx (void ) { -struct rdt_resource *r = &rdt_resources_all[RDT_RESOURCE_L3 ].r_resctrl; +u32 num_rmids =U32_MAX ; +struct rdt_resource *r; + +for_each_mon_capable_rdt_resource (r) + num_rmids =min (num_rmids, r->num_rmid);/* RMID are independent numbers for x86. num_rmid_idx == num_rmid */ -return r->num_rmid; +return num_rmids ==U32_MAX ?0 : num_rmids; }struct rdt_resource *resctrl_arch_get_resource (enum resctrl_res_level l)fs/resctrl/rdtgroup.c +0
-0
fs/resctrl/rdtgroup.c void resctrl_offline_mon_domain(struct rdt_resource *r, struct rdt_domain_hdr *h · line 4120
Quoted 5 lines
fs/resctrl/rdtgroup.c +2
-0@@ -4116,6 +4116,11 @@ void resctrl_offline_mon_domain(struct rdt_resource *r, struct rdt_domain_hdr *h* During boot this may be called before global allocations have been made by * resctrl_mon_l3_resource_init(). * +* This routine is called at resctrl init time. The number of supported RMIDs +* may be reduced if additional mon capable resources are enumerated at mount
"mon capable" -> "monitoring capable" or "mon_capable"
fs/resctrl/rdtgroup.c void resctrl_offline_mon_domain(struct rdt_resource *r, struct rdt_domain_hdr *h · line 4121
Quoted 1 line
fs/resctrl/rdtgroup.c +1
-0+* time. This means the rdt_l3_mon_domain::states[] allocations may be larger
"rdt_l3_mon_domain::states[]" -> "rdt_l3_mon_domain::mbm_states[] and rdt_l3_mon_domain::rmid_busy_llc"
fs/resctrl/rdtgroup.c void resctrl_offline_mon_domain(struct rdt_resource *r, struct rdt_domain_hdr *h · line 4126
Quoted 5 lines
fs/resctrl/rdtgroup.c +2
-0+* than needed. +* * Returns 0 for success, or -ENOMEM. */ static int domain_setup_l3_mon_state (struct rdt_resource *r,struct rdt_l3_mon_domain *d)
Reinette
Tony Luck
maintainerPATCH v8 28/32 fs/resctrl: Move RMID initialization to first mount
In reply to Tony Luckresctrl assumesthat the number of supported RMIDs is enumerated during early initialization.
Telemetry monitor events break that assumption because they are not enumerated in early initialization and may support a different number of RMIDs compared to L3 monitor features.
Delay allocation and initialization of rmid_ptrs[] until first mount.
Rename routines to match what they now do:dom_data_init() -> setup_rmid_lru_list()dom_data_exit() -> free_rmid_lru_list()
--- fs/resctrl/internal.h | 4 ++++ fs/resctrl/monitor.c | 47 ++++++++++--------------------------------- fs/resctrl/rdtgroup.c | 7 +++++++ 3 files changed, 22 insertions(+), 36 deletions(-)
fs/resctrl/internal.h +4 -0
@@ -354,6 +354,10 @@ int closids_supported(void);void closid_free (int closid); +int setup_rmid_lru_list (void ); + +void free_rmid_lru_list (void ); +int alloc_rmid (u32 closid);void free_rmid (u32 closid,u32 rmid);
fs/resctrl/monitor.c +11 -36
103 lines not on this page · raw message
fs/resctrl/rdtgroup.c +7 -0
@@ -2599,6 +2599,12 @@ static int rdt_get_tree(struct fs_context *fc) goto out; } +if (resctrl_arch_mon_capable ()) { + ret =setup_rmid_lru_list (); +if (ret) + goto out; + } + ret =rdtgroup_setup_root (ctx);if (ret) goto out;
@@ -4408,4 +4414,5 @@ void resctrl_exit(void)*/ resctrl_mon_l3_resource_exit (); +free_rmid_lru_list (); }
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 28/32] fs/resctrl: Move RMID initialization to first mount
Hi Tony,
Quoted 1 line · Tony Luck
resctrl assumesthat the number of supported RMIDs is enumerated during
"assumesthat" -> "assumes that"
Quoted 1 line
early initialization.
The context can be made a more specific though. For example,
L3 monitor features are enumerated during resctrl initialization and rmid_ptrs[] that tracks all RMIDs and depends on the number of supported RMIDs is allocated during this time.
Telemetry monitor features are enumerated during resctrl mount and may support a different number of RMIDs compared to L3 monitor features.
Quoted 13 lines
Telemetry monitor events break that assumption because they are not enumerated in early initialization and may support a different number of RMIDs compared to L3 monitor features.
Delay allocation and initialization of rmid_ptrs[] until first mount.
Rename routines to match what they now do:
dom_data_init()->setup_rmid_lru_list()dom_data_exit()->free_rmid_lru_list()Signed-off-by Tony Luck <[email protected]>---
...
Quoted 40 lines
fs/resctrl/monitor.c +7
-8@@ -802,20 +802,19 @@ void mbm_setup_overflow_handler(struct rdt_l3_mon_domain *dom, unsigned long delschedule_delayed_work_on (cpu, &dom->mbm_over, delay); } -static int dom_data_init (struct rdt_resource *r) +int setup_rmid_lru_list (void ) {u32 idx_limit =resctrl_arch_system_num_rmid_idx ();struct rmid_entry *entry =NULL ; -int err =0 , i;u32 idx; +int i; -mutex_lock (&rdtgroup_mutex); +if (rmid_ptrs) +return 0 ; rmid_ptrs =kcalloc (idx_limit,sizeof (struct rmid_entry ),GFP_KERNEL ); -if (!rmid_ptrs) { - err = -ENOMEM ; - goto out_unlock; - } +if (!rmid_ptrs) +return -ENOMEM ;for (i =0 ; i < idx_limit; i++) { entry = &rmid_ptrs[i];@@ -828,31 +827,20 @@ static int dom_data_init(struct rdt_resource *r)/* * RESCTRL_RESERVED_CLOSID and RESCTRL_RESERVED_RMID are special and * are always allocated. These are used for the rdtgroup_default -* control group, which will be setup later in resctrl_init(). +* control group, which was setup earlier in rdtgroup_setup_default(). */ idx =resctrl_arch_rmid_idx_encode (RESCTRL_RESERVED_CLOSID ,RESCTRL_RESERVED_RMID );
fs/resctrl/monitor.c static int dom_data_init(struct rdt_resource *r) · line 839
Quoted 10 lines
fs/resctrl/monitor.c +1
-4entry =__rmid_entry (idx);list_del (&entry->list); -out_unlock: -mutex_unlock (&rdtgroup_mutex); - -return err; +return 0 ; }
Removing the mutex lock/unlock from setup_rmid_lru_list() is correct since setup_rmid_lru_list() is called with mutex held. free_rmid_lru_list() is not called with mutex held so it is not clear why it is ok to remove mutex lock/unlock below?
Quoted 70 lines
fs/resctrl/monitor.c +3
-24-static void dom_data_exit (struct rdt_resource *r) +void free_rmid_lru_list (void ) { -mutex_lock (&rdtgroup_mutex); - -if (!r->mon_capable) - goto out_unlock; -kfree (rmid_ptrs); rmid_ptrs =NULL ; - -out_unlock: -mutex_unlock (&rdtgroup_mutex); }#define MON_EVENT (_eventid, _name, _res, _fp) \@@ -914,7 +902,8 @@ bool resctrl_is_mon_event_enabled(enum resctrl_event_id eventid)* resctrl_mon_l3_resource_init() - Initialise global monitoring structures. * * Allocate and initialise global monitor resources that do not belong to a -* specific domain. i.e. the rmid_ptrs[] used for the limbo and free lists. +* specific domain. i.e. the closid_num_dirty_rmid[] used to find the CLOSID +* with the cleanest set of RMIDs. * Called once during boot after the struct rdt_resource's have been configured * but before the filesystem is mounted. * Resctrl's cpuhp callbacks may be called before this point to bring a domain @@ -925,7 +914,6 @@ bool resctrl_is_mon_event_enabled(enum resctrl_event_id eventid)int resctrl_mon_l3_resource_init (void ) {struct rdt_resource *r =resctrl_arch_get_resource (RDT_RESOURCE_L3 ); -int ret;if (!r->mon_capable)return 0 ;@@ -947,15 +935,6 @@ int resctrl_mon_l3_resource_init(void) closid_num_dirty_rmid = tmp; } - ret =dom_data_init (r); -if (ret) { -if (IS_ENABLED (CONFIG_RESCTRL_RMID_DEPENDS_ON_CLOSID )) { -kfree (closid_num_dirty_rmid); - closid_num_dirty_rmid =NULL ; - } -return ret; - } -if (resctrl_arch_is_evt_configurable (QOS_L3_MBM_TOTAL_EVENT_ID )) { mon_event_all[QOS_L3_MBM_TOTAL_EVENT_ID ].configurable = true; resctrl_file_fflags_init("mbm_total_bytes_config",@@ -977,12 +956,8 @@ int resctrl_mon_l3_resource_init(void)void resctrl_mon_l3_resource_exit (void ) { -struct rdt_resource *r =resctrl_arch_get_resource (RDT_RESOURCE_L3 ); -if (IS_ENABLED (CONFIG_RESCTRL_RMID_DEPENDS_ON_CLOSID )) {kfree (closid_num_dirty_rmid); closid_num_dirty_rmid =NULL ; } - -dom_data_exit (r); }fs/resctrl/rdtgroup.c +0
-0@@ -2599,6 +2599,12 @@ static int rdt_get_tree(struct fs_context *fc) goto out; }
fs/resctrl/rdtgroup.c static int rdt_get_tree(struct fs_context *fc) · line 2610
Quoted 10 lines
fs/resctrl/rdtgroup.c +6
-0+if (resctrl_arch_mon_capable ()) { + ret =setup_rmid_lru_list (); +if (ret) + goto out; + } + ret =rdtgroup_setup_root (ctx);if (ret) goto out;
Shouldn't this be cleaned up on failure? I expected to see free_rmid_lru_list() in rdt_get_tree()'s failure paths.
fs/resctrl/rdtgroup.c void resctrl_exit(void) · line 4418
Quoted 6 lines
fs/resctrl/rdtgroup.c +1
-0@@ -4408,4 +4414,5 @@ void resctrl_exit(void)*/ resctrl_mon_l3_resource_exit (); +free_rmid_lru_list (); }
Reinette
Tony Luck
maintainerPATCH v8 29/32 x86/resctrl: Enable RDT_RESOURCE_PERF_PKG
In reply to Tony LuckThe RDT_RESOURCE_PERF_PKG resource is not marked as "mon_capable" during early resctrl initialization. This means that the domain lists for the resource are not built when the CPU hot plug notifiers are registered.
Set the global rdt_mon_capable (to cover the case when none of the L3 monitor events are enabled).
Mark the resource as mon_capable and call domain_add_cpu_mon() for each online CPU to build the domain lists in the first call to the resctrl_arch_pre_mount() hook.
--- arch/x86/kernel/cpu/resctrl/core.c | 17 ++++++++++++++++- arch/x86/kernel/cpu/resctrl/intel_aet.c | 4 ++++ 2 files changed, 20 insertions(+), 1 deletion(-)
arch/x86/kernel/cpu/resctrl/core.c +16 -1
@@ -750,14 +750,29 @@ static int resctrl_arch_offline_cpu(unsigned int cpu)void resctrl_arch_pre_mount (void ) { +struct rdt_resource *r = &rdt_resources_all[RDT_RESOURCE_PERF_PKG ].r_resctrl;static atomic_t only_once =ATOMIC_INIT (0 ); -int old =0 ; +int cpu, old =0 ;if (!atomic_try_cmpxchg (&only_once, &old,1 ))return ;if (!intel_aet_get_events ())return ; + +if (!r->mon_capable) +return ; + +/* +* Late discovery of telemetry events means the domains for the +* resource were not built. Do that now. +*/ +cpus_read_lock (); +mutex_lock (&domain_list_lock); +for_each_online_cpu (cpu) +domain_add_cpu_mon (cpu, r); +mutex_unlock (&domain_list_lock); +cpus_read_unlock (); }enum {
arch/x86/kernel/cpu/resctrl/intel_aet.c +4 -0
@@ -258,6 +258,10 @@ static int discover_events(struct event_group *e, struct pmt_feature_group *p)else r->num_rmid = e->num_rmids; +pr_info ("%s %s monitoring detected\n" , r->name, e->name); + r->mon_capable = true; + rdt_mon_capable = true; +return 0 ; }
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 29/32] x86/resctrl: Enable RDT_RESOURCE_PERF_PKG
Hi Tony,
Quoted 3 lines · Tony Luck
The
RDT_RESOURCE_PERF_PKGresource is not marked as "mon_capable" during early resctrl initialization. This means that the domain lists for the resource are not built when the CPU hot plug notifiers are registered.
Please check series for consistent terminology ... I think these "CPU hot plug notifiers" may have been called "hooks", "callbacks", and "handlers" through this series.
Reinette
Tony Luck
maintainerPATCH v8 30/32 fs/resctrl: Provide interface to create architecture specific debugfs area
In reply to Tony LuckAll files below /sys/fs/resctrl are considered user ABI.
This leaves no place for architectures to provide additional interfaces.
Add resctrl_debugfs_mon_info_arch_mkdir() which creates a directory in the debugfs file system for a resource. Naming follows the layout of the main resctrl hierarchy:
/sys/kernel/debug/resctrl/info/{resource}_MON/{arch}The {arch} last level directory name matches the output of the user level "uname -m" command.
Architecture code may use this directory for debug information, or for minor tuning of features. It must not be used for basic feature enabling as debugfs may not be configured/mounted on production systems.
--- include/linux/resctrl.h | 9 +++++++++ fs/resctrl/rdtgroup.c | 29 +++++++++++++++++++++++++++++ 2 files changed, 38 insertions(+)
include/linux/resctrl.h +9 -0
@@ -571,6 +571,15 @@ void resctrl_arch_reset_all_ctrls(struct rdt_resource *r);extern unsigned int resctrl_rmid_realloc_threshold;extern unsigned int resctrl_rmid_realloc_limit; +/** +* resctrl_debugfs_mon_info_arch_mkdir() - Create a debugfs info directory. +* Removed by resctrl_exit(). +* @r: Resource (must be mon_capable). +* +* Return: dentry pointer on success, or NULL on error. +*/ +struct dentry *resctrl_debugfs_mon_info_arch_mkdir (struct rdt_resource *r); +int resctrl_init (void );void resctrl_exit (void );
fs/resctrl/rdtgroup.c +29 -0
@@ -24,6 +24,7 @@#include <linux/sched/task.h> #include <linux/slab.h> #include <linux/user_namespace.h> +#include <linux/utsname.h> #include <uapi/linux/magic.h>
@@ -75,6 +76,8 @@ static void rdtgroup_destroy_root(void);struct dentry *debugfs_resctrl; +static struct dentry *debugfs_resctrl_info; +/* * Memory bandwidth monitoring event to use for the default CTRL_MON group * and each new CTRL_MON group created by the user. Only relevant when
@@ -4355,6 +4358,31 @@ int resctrl_init(void)return ret; } +/* +* Create /sys/kernel/debug/resctrl/info/{r->name}_MON/{arch} directory +* by request for architecture to use for debugging or minor tuning. +* Basic functionality of features must not be controlled by files +* added to this directory as debugfs may not be configured/mounted +* on production systems. +*/ +struct dentry *resctrl_debugfs_mon_info_arch_mkdir (struct rdt_resource *r) +{ +struct dentry *moninfodir; +char name[32 ]; + +if (!r->mon_capable) +return NULL ; + +if (!debugfs_resctrl_info) + debugfs_resctrl_info =debugfs_create_dir ("info" , debugfs_resctrl); + +sprintf (name,"%s_MON" , r->name); + + moninfodir =debugfs_create_dir (name, debugfs_resctrl_info); + +return debugfs_create_dir (utsname ()->machine, moninfodir); +} +static bool resctrl_online_domains_exist (void ) {struct rdt_resource *r;
@@ -4406,6 +4434,7 @@ void resctrl_exit(void)debugfs_remove_recursive (debugfs_resctrl); debugfs_resctrl =NULL ; + debugfs_resctrl_info =NULL ;unregister_filesystem (&rdt_fs_type);/*
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 30/32] fs/resctrl: Provide interface to create architecture specific debugfs area
Hi Tony,
Quoted 7 lines · Tony Luck
All files below
/sys/fs/resctrlare considered user ABI.This leaves no place for architectures to provide additional interfaces.
Add
resctrl_debugfs_mon_info_arch_mkdir()which creates a directory in the debugfs file system for a resource. Naming follows the layout of the
"a resource" -> "a monitoring resource"
Quoted 7 lines
main resctrl hierarchy:
/sys/kernel/debug/resctrl/info/{resource}_MON/{arch}The {arch} last level directory name matches the output of the user level "uname -m" command.
Quoted 8 lines
Architecture code may use this directory for debug information, or for minor tuning of features. It must not be used for basic feature enabling as debugfs may not be configured/mounted on production systems.
Suggested-by Reinette Chatre <[email protected]>Signed-off-by Tony Luck <[email protected]>---
Reinette
Tony Luck
maintainerPATCH v8 31/32 x86/resctrl: Add debugfs files to show telemetry aggregator status
In reply to Tony LuckEach telemetry aggregator provides three status registers at the top end of MMIO space after all the per-RMID per-event counters:
agg_data_loss_count: This counts the number of times that this aggregator failed to accumulate a counter value supplied by a CPU core.
agg_data_loss_timestamp: This is a "timestamp" from a free running 25MHz uncore timer indicating when the most recent data loss occurred.
last_update_timestamp: Another 25MHz timestamp indicating when the most recent counter update was successfully applied.
Create files in /sys/kernel/debug/resctrl/info/PERF_PKG_MON/x86_64/ to display the value of each of these status registers for each aggregator in each enabled event group.
--- arch/x86/kernel/cpu/resctrl/intel_aet.c | 53 +++++++++++++++++++++++++ 1 file changed, 53 insertions(+)
arch/x86/kernel/cpu/resctrl/intel_aet.c +53 -0
@@ -13,6 +13,7 @@#include <linux/cleanup.h> #include <linux/cpu.h> +#include <linux/debugfs.h> #include <linux/intel_vsec.h> #include <linux/io.h> #include <linux/minmax.h>
@@ -299,6 +300,55 @@ static bool get_pmt_feature(enum pmt_feature_id feature, struct event_group **evreturn false; } +static int status_read (void *priv,u64 *val) +{ +void __iomem *info = (void __iomem *)priv; + + *val =readq (info); + +return 0 ; +} + +DEFINE_SIMPLE_ATTRIBUTE (status_fops, status_read,NULL ,"%llu\n" ); + +static void make_status_files (struct dentry *dir,struct event_group *e,int pkg,int instance) +{ +void *info = (void __force *)e->pkginfo[pkg]->addrs[instance] + e->mmio_size; +char name[64 ]; + +sprintf (name,"%s_pkg%d_agg%d_data_loss_count" , e->name, pkg, instance); +debugfs_create_file (name,0400 , dir, info -24 , &status_fops); + +sprintf (name,"%s_pkg%d_agg%d_data_loss_timestamp" , e->name, pkg, instance); +debugfs_create_file (name,0400 , dir, info -16 , &status_fops); + +sprintf (name,"%s_pkg%d_agg%d_last_update_timestamp" , e->name, pkg, instance); +debugfs_create_file (name,0400 , dir, info -8 , &status_fops); +} + +static void create_debug_event_status_files (struct dentry *dir,struct event_group *e) +{ +int num_pkgs =topology_max_packages (); + +for (int i =0 ; i < num_pkgs; i++) +for (int j =0 ; j < e->pkginfo[i]->num_regions; j++) +make_status_files (dir, e, i, j); +} + +static void create_debugfs_status_file (void ) +{ +struct rdt_resource *r = &rdt_resources_all[RDT_RESOURCE_PERF_PKG ].r_resctrl; +struct event_group *evg; +struct dentry *infodir; + + infodir =resctrl_debugfs_mon_info_arch_mkdir (r); +if (!infodir) +return ; + +list_for_each_entry (evg, &active_event_groups, list) +create_debug_event_status_files (infodir, evg); +} +/* * Ask OOBMSM discovery driver for all the RMID based telemetry groups * that it supports.
@@ -314,6 +364,9 @@ bool intel_aet_get_events(void) known_perf_event_groups, ARRAY_SIZE(known_perf_event_groups)); +if (ret1 || ret2) +create_debugfs_status_file (); +return ret1 || ret2; }
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 31/32] x86/resctrl: Add debugfs files to show telemetry aggregator status
Hi Tony,
Quoted 11 lines · Tony Luck
Each telemetry aggregator provides three status registers at the top end of MMIO space after all the per-RMID per-event counters:
agg_data_loss_count: This counts the number of times that this aggregator failed to accumulate a counter value supplied by a CPU core.
agg_data_loss_timestamp: This is a "timestamp" from a free running 25MHz uncore timer indicating when the most recent data loss occurred.
last_update_timestamp: Another 25MHz timestamp indicating when the most recent counter update was successfully applied.
With all three files being "per aggregator" it is not clear to me why "last_update_timestamp" does not have the "agg_" prefix. Looking at the debugfs files created all three are indeed created with the "agg" prefix so this looks inconsistent.
Quoted 4 lines
Create files in
/sys/kernel/debug/resctrl/info/PERF_PKG_MON/x86_64/to display the value of each of these status registers for each aggregator in each enabled event group.
To avoid reviewers needing to dig, this can add that these files are removed as part of the debugfs_remove_recursive() called during resctrl exit.
Quoted 59 lines
Signed-off-by Tony Luck <[email protected]>--- arch/x86/kernel/cpu/resctrl/intel_aet.c | 53 +++++++++++++++++++++++++ 1 file changed, 53 insertions(+)arch/x86/kernel/cpu/resctrl/intel_aet.c +38
-0@@ -13,6 +13,7 @@#include <linux/cleanup.h> #include <linux/cpu.h> +#include <linux/debugfs.h> #include <linux/intel_vsec.h> #include <linux/io.h> #include <linux/minmax.h> @@ -299,6 +300,55 @@ static bool get_pmt_feature(enum pmt_feature_id feature, struct event_group **evreturn false; } +static int status_read (void *priv,u64 *val) +{ +void __iomem *info = (void __iomem *)priv; + + *val =readq (info); + +return 0 ; +} + +DEFINE_SIMPLE_ATTRIBUTE (status_fops, status_read,NULL ,"%llu\n" ); + +static void make_status_files (struct dentry *dir,struct event_group *e,int pkg,int instance) +{ +void *info = (void __force *)e->pkginfo[pkg]->addrs[instance] + e->mmio_size; +char name[64 ]; + +sprintf (name,"%s_pkg%d_agg%d_data_loss_count" , e->name, pkg, instance); +debugfs_create_file (name,0400 , dir, info -24 , &status_fops); + +sprintf (name,"%s_pkg%d_agg%d_data_loss_timestamp" , e->name, pkg, instance); +debugfs_create_file (name,0400 , dir, info -16 , &status_fops); + +sprintf (name,"%s_pkg%d_agg%d_last_update_timestamp" , e->name, pkg, instance); +debugfs_create_file (name,0400 , dir, info -8 , &status_fops); +} + +static void create_debug_event_status_files (struct dentry *dir,struct event_group *e) +{ +int num_pkgs =topology_max_packages (); + +for (int i =0 ; i < num_pkgs; i++) +for (int j =0 ; j < e->pkginfo[i]->num_regions; j++) +make_status_files (dir, e, i, j); +} + +static void create_debugfs_status_file (void ) +{
arch/x86/kernel/cpu/resctrl/intel_aet.c static bool get_pmt_feature(enum pmt_feature_id feature, struct event_group **ev · line 349
Quoted 10 lines
arch/x86/kernel/cpu/resctrl/intel_aet.c +10
-0+struct rdt_resource *r = &rdt_resources_all[RDT_RESOURCE_PERF_PKG ].r_resctrl; +struct event_group *evg; +struct dentry *infodir; + + infodir =resctrl_debugfs_mon_info_arch_mkdir (r); +if (!infodir) +return ; + +list_for_each_entry (evg, &active_event_groups, list) +create_debug_event_status_files (infodir, evg);
To avoid using/needing active_event_groups create_debug_event_status_files() can be called at end of discover_events() and infodir can be a global that is initialized there if it is NULL.
Reinette
Tony Luck
maintainerPATCH v8 32/32 x86,fs/resctrl: Update Documentation for package events
In reply to Tony LuckEach "mon_data" directory is now divided between L3 events and package events.
The "info/PERF_PKG_MON" directory contains parameters for perf events.
--- Documentation/filesystems/resctrl.rst | 85 +++++++++++++++++++++++---- 1 file changed, 75 insertions(+), 10 deletions(-)
Documentation/filesystems/resctrl.rst +75 -10
@@ -167,7 +167,7 @@ with respect to allocation: bandwidth percentages are directly applied to the threads running on the core -If RDT monitoring is available there will be an "L3_MON" directory +If L3 monitoring is available there will be an "L3_MON" directory with the following files: "num_rmids":
@@ -261,6 +261,18 @@ with the following files: bytes) at which a previously used LLC_occupancy counter can be considered for re-use. +If telemetry monitoring is available there will be an "PERF_PKG_MON" directory +with the following files: + +"num_rmids": + The number of telemetry RMIDs supported. If this is different + from the number reported in the L3_MON directory the limit + on the number of "CTRL_MON" + "MON" directories is the + minimum of the values. + +"mon_features": + Lists the telemetry monitoring events that are enabled on this system. + Finally, in the top level of the "info" directory there is a file named "last_cmd_status". This is reset with every "command" issued via the file system (making new directories or writing to any of the
@@ -366,15 +378,36 @@ When control is enabled all CTRL_MON groups will also contain: When monitoring is enabled all MON groups will also contain: "mon_data": - This contains a set of files organized by L3 domain and by - RDT event. E.g. on a system with two L3 domains there will - be subdirectories "mon_L3_00" and "mon_L3_01". Each of these - directories have one file per event (e.g. "llc_occupancy", - "mbm_total_bytes", and "mbm_local_bytes"). In a MON group these - files provide a read out of the current value of the event for - all tasks in the group. In CTRL_MON groups these files provide - the sum for all tasks in the CTRL_MON group and all tasks in - MON groups. Please see example section for more details on usage. + This contains a set of directories, one for each instance + of an L3 cache, or of a processor package. The L3 cache + directories are named "mon_L3_00", "mon_L3_01" etc. The + package directories "mon_PERF_PKG_00", "mon_PERF_PKG_01" etc. + + Within each directory there is one file per event. In + the L3 directories: "llc_occupancy", "mbm_total_bytes", + and "mbm_local_bytes". In the PERF_PKG directories: "core_energy", + "activity", etc. + + "core_energy" reports a floating point number for the energy + (in Joules) used by CPUs for each RMID. + + "activity" also reports a floating point value (in Farads). + This provides an estimate of work done independent of the + frequency that the CPUs used for execution. + + Note that these two counters only measure energy/activity + in the "core" of the CPU (arithmetic units, TLB, L1 and L2 + caches, etc.). They do not include L3 cache, memory, I/O + devices etc. + + All other events report decimal integer values. + + In a MON group these files provide a read out of the current + value of the event for all tasks in the group. In CTRL_MON groups + these files provide the sum for all tasks in the CTRL_MON group + and all tasks in MON groups. Please see example section for more + details on usage. + On systems with Sub-NUMA Cluster (SNC) enabled there are extra directories for each node (located within the "mon_L3_XX" directory for the L3 cache they occupy). These are named "mon_sub_L3_YY"
@@ -1300,6 +1333,38 @@ Example with C:: resctrl_release_lock(fd); } +Debugfs +======= +In addition to the use of debugfs for tracing of pseudo-locking +performance, architecture code may create debugfs directories +associated with monitoring features for a specific resource. + +The full pathname for these is in the form: + + /sys/kernel/debug/resctrl/info/{resource_name}_MON/{arch}/ + +The prescence, names, and format of these files will vary +between architectures even if the same resource is present. + +PERF_PKG_MON/x86_64 +------------------- +Three files are present per telemetry aggregator instance +that show when and how often the hardware has failed to +collect and accumulate data from the CPUs. + +agg_data_loss_count: + This counts the number of times that this aggregator + failed to accumulate a counter value supplied by a CPU. + +agg_data_loss_timestamp: + This is a "timestamp" from a free running 25MHz uncore + timer indicating when the most recent data loss occurred. + +last_update_timestamp: + Another 25MHz timestamp indicating when the + most recent counter update was successfully applied. + + Examples for RDT Monitoring along with allocation usage ======================================================= Reading monitored data
Signature · 1 line
2.50.1
Reinette Chatre
maintainerRe: [PATCH v8 32/32] x86,fs/resctrl: Update Documentation for package events
Hi Tony,
subject: "Documentation" -> "documentation"
Quoted 4 lines · Tony Luck
Each "
mon_data" directory is now divided between L3 events and package events.The "info/PERF_PKG_MON" directory contains parameters for perf events.
This changelog seems to be an incomplete and cryptic summary of the resctrl interface changes made in this series. If the goal is to document the new interfaces then please add a summary of these interfaces. Alternatively this changelog may also be ok to be succinct like:
"Update resctrl filesystem documentation with the details about the
resctrl files that support telemetry events."
Quoted 11 lines
Signed-off-by Tony Luck <[email protected]>--- Documentation/filesystems/resctrl.rst | 85 +++++++++++++++++++++++---- 1 file changed, 75 insertions(+), 10 deletions(-)Documentation/filesystems/resctrl.rst +0
-0
Documentation/filesystems/resctrl.rst with respect to allocation: · line 173
Quoted 8 lines
Documentation/filesystems/resctrl.rst +1
-1@@ -167,7 +167,7 @@ with respect to allocation: bandwidth percentages are directly applied to the threads running on the core -If RDT monitoring is available there will be an "L3_MON" directory +If L3 monitoring is available there will be an "L3_MON" directory with the following files: "num_rmids":
I expect that L3_MON's num_rmids also needs an update since it no longer dictates the upper bound on for how many "CTRL_MON" + "MON" groups can be created.
Quoted 24 lines
Documentation/filesystems/resctrl.rst +12
-1@@ -261,6 +261,18 @@ with the following files: bytes) at which a previously used LLC_occupancy counter can be considered for re-use. +If telemetry monitoring is available there will be an "PERF_PKG_MON" directory +with the following files: + +"num_rmids": + The number of telemetry RMIDs supported. If this is different + from the number reported in the L3_MON directory the limit + on the number of "CTRL_MON" + "MON" directories is the + minimum of the values. + +"mon_features": + Lists the telemetry monitoring events that are enabled on this system. + Finally, in the top level of the "info" directory there is a file named "last_cmd_status". This is reset with every "command" issued via the file system (making new directories or writing to any of the@@ -366,15 +378,36 @@ When control is enabled all CTRL_MON groups will also contain: When monitoring is enabled all MON groups will also contain: "mon_data": - This contains a set of files organized by L3 domain and by
Documentation/filesystems/resctrl.rst When control is enabled all CTRL_MON groups will also contain: · line 382
Quoted 10 lines
Documentation/filesystems/resctrl.rst +2
-8- RDT event. E.g. on a system with two L3 domains there will - be subdirectories "mon_L3_00" and "mon_L3_01". Each of these - directories have one file per event (e.g. "llc_occupancy", - "mbm_total_bytes", and "mbm_local_bytes"). In a MON group these - files provide a read out of the current value of the event for - all tasks in the group. In CTRL_MON groups these files provide - the sum for all tasks in the CTRL_MON group and all tasks in - MON groups. Please see example section for more details on usage. + This contains a set of directories, one for each instance + of an L3 cache, or of a processor package. The L3 cache
A monitor group may have directories for L3 cache *and* processor packages, right?
Documentation/filesystems/resctrl.rst When control is enabled all CTRL_MON groups will also contain: · line 389
Quoted 7 lines
Documentation/filesystems/resctrl.rst +7
-0+ directories are named "mon_L3_00", "mon_L3_01" etc. The + package directories "mon_PERF_PKG_00", "mon_PERF_PKG_01" etc. + + Within each directory there is one file per event. In + the L3 directories: "llc_occupancy", "mbm_total_bytes", + and "mbm_local_bytes". In the PERF_PKG directories: "core_energy", + "activity", etc.
I do not think this should be hardcoded as expected events. The original text was careful to use "e.g" when mentioning the L3 events while new text seems to make all three events as fact. I wonder if it may not be easier to read if this refers to the resource's mon_features file to know which events can be expected to be present and then the mon_features section is where all the intricate details of events are documented. Compare with the L3 mon_features section.
Quoted 29 lines
Documentation/filesystems/resctrl.rst +22
-0+ + "core_energy" reports a floating point number for the energy + (in Joules) used by CPUs for each RMID. + + "activity" also reports a floating point value (in Farads). + This provides an estimate of work done independent of the + frequency that the CPUs used for execution. + + Note that these two counters only measure energy/activity + in the "core" of the CPU (arithmetic units, TLB, L1 and L2 + caches, etc.). They do not include L3 cache, memory, I/O + devices etc. + + All other events report decimal integer values. + + In a MON group these files provide a read out of the current + value of the event for all tasks in the group. In CTRL_MON groups + these files provide the sum for all tasks in the CTRL_MON group + and all tasks in MON groups. Please see example section for more + details on usage. + On systems with Sub-NUMA Cluster (SNC) enabled there are extra directories for each node (located within the "mon_L3_XX" directory for the L3 cache they occupy). These are named "mon_sub_L3_YY"@@ -1300,6 +1333,38 @@ Example with C:: resctrl_release_lock(fd); } +Debugfs
Documentation/filesystems/resctrl.rst Example with C:: · line 1346
Quoted 10 lines
Documentation/filesystems/resctrl.rst +10
-0+======= +In addition to the use of debugfs for tracing of pseudo-locking +performance, architecture code may create debugfs directories +associated with monitoring features for a specific resource. + +The full pathname for these is in the form: + + /sys/kernel/debug/resctrl/info/{resource_name}_MON/{arch}/ + +The prescence, names, and format of these files will vary
prescence -> presence
Just to keep options open I would rather have this say "may vary"
Quoted 9 lines
Documentation/filesystems/resctrl.rst +9
-0+between architectures even if the same resource is present. + +PERF_PKG_MON/x86_64 +------------------- +Three files are present per telemetry aggregator instance +that show when and how often the hardware has failed to +collect and accumulate data from the CPUs. + +agg_data_loss_count:
Documentation/filesystems/resctrl.rst Example with C:: · line 1365
Quoted 10 lines
Documentation/filesystems/resctrl.rst +10
-0+ This counts the number of times that this aggregator + failed to accumulate a counter value supplied by a CPU. + +agg_data_loss_timestamp: + This is a "timestamp" from a free running 25MHz uncore + timer indicating when the most recent data loss occurred. + +last_update_timestamp: + Another 25MHz timestamp indicating when the + most recent counter update was successfully applied.
Same comment wrt missing "agg" prefix.
Documentation/filesystems/resctrl.rst Example with C:: · line 1370
Quoted 5 lines
Documentation/filesystems/resctrl.rst +2
-0+ + Examples for RDT Monitoring along with allocation usage ======================================================= Reading monitored data
Reinette
Reinette Chatre
maintainerHi Tony,
On 8/11/25 11:16 AM, Tony Luck wrote:
...
Quoted 2 lines
The
INTEL_PMT_DISCOVERYdriver providesintel_pmt_get_regions_by_feature()
INTEL_PMT_DISCOVERY -> INTEL_PMT_TELEMETRY ?
Reinette
Luck, Tony
maintainerQuoted 3 lines
Quoted 1 line
The
INTEL_PMT_DISCOVERYdriver providesintel_pmt_get_regions_by_feature()
INTEL_PMT_DISCOVERY->INTEL_PMT_TELEMETRY?
Reinette,
Perhaps. The discovery driver is somewhat it's own thing:
drivers/platform/x86/intel/pmt/Makefile:obj-$(CONFIG_INTEL_PMT_DISCOVERY) += pmt_discovery.o
But it is automatically pulled in if you enable INTEL_PMT_TELEMETRY:
drivers/platform/x86/intel/pmt/Kconfig-config INTEL_PMT_TELEMETRY drivers/platform/x86/intel/pmt/Kconfig- tristate "Intel Platform Monitoring Technology (PMT) Telemetry driver" drivers/platform/x86/intel/pmt/Kconfig- depends on INTEL_VSEC drivers/platform/x86/intel/pmt/Kconfig: select INTEL_PMT_DISCOVERY
-Tony
Reinette Chatre
maintainerHi Tony,
Quoted 8 lines · Tony
Quoted 3 lines
Quoted 1 line
The
INTEL_PMT_DISCOVERYdriver providesintel_pmt_get_regions_by_feature()
INTEL_PMT_DISCOVERY->INTEL_PMT_TELEMETRY?Reinette,
Perhaps. The discovery driver is somewhat it's own thing:
Quoted 8 lines
drivers/platform/x86/intel/pmt/Makefile:obj-$(CONFIG_INTEL_PMT_DISCOVERY) += pmt_discovery.o
But it is automatically pulled in if you enable
INTEL_PMT_TELEMETRY:
drivers/platform/x86/intel/pmt/Kconfig-configINTEL_PMT_TELEMETRYdrivers/platform/x86/intel/pmt/Kconfig-tristate "Intel Platform Monitoring Technology (PMT) Telemetry driver"drivers/platform/x86/intel/pmt/Kconfig-depends onINTEL_VSECdrivers/platform/x86/intel/pmt/Kconfig: selectINTEL_PMT_DISCOVERY
The sentence reads:
"The INTEL_PMT_DISCOVERY driver provides intel_pmt_get_regions_by_feature()"
Looking at code:intel_pmt_get_regions_by_feature() is implemented in:
drivers/platform/x86/intel/pmt/telemetry.c
Looking at Makefile (drivers/platform/x86/intel/pmt/Makefile):
obj-$(CONFIG_INTEL_PMT_TELEMETRY) += pmt_telemetry.o
pmt_telemetry-y := telemetry.o
Since intel_pmt_get_regions_by_feature() is in file associated with INTEL_PMT_TELEMETRY I believe it is more accurate to say:
"The INTEL_PMT_TELEMETRY driver provides intel_pmt_get_regions_by_feature()"
I do not see INTEL_PMT_DISCOVERY depend on INTEL_PMT_TELEMETRY so having a kernel built with just INTEL_PMT_DISCOVERY will not include intel_pmt_get_regions_by_feature() so I do not believe "The INTEL_PMT_DISCOVERY driver provides intel_pmt_get_regions_by_feature()" is accurate.
Reinette
Reinette Chatre
maintainerHi Tony,
Quoted 69 lines · Tony Luck
Background
----------
On Intel systems that support per-RMID telemetry monitoring each logical processor keeps a local count for various events. When the IA32_PQR_ASSOC.RMID value for the logical processor changes (or when a two millisecond counter expires) these event counts are transmitted to an event aggregator on the same package as the processor together with the current RMID value. The event counters are reset to zero to begin counting again.Each aggregator takes the incoming event counts and adds them to cumulative counts for each event for each RMID. Note that there can be multiple aggregators on each package with no architectural association between logical processors and an aggregator.
All of these aggregated counters can be read by an operating system from the MMIO space of the Out Of Band Management Service Module (OOBMSM) device(s) on a system. Any counter can be read from any logical processor.
Intel publishes details for each processor generation showing which events are counted by each logical processor and the offsets for each accumulated counter value within the MMIO space in XML files here:
https://github.com/intel/Intel-PMT.For example there are two energy related telemetry events for the Clearwater Forest family of processors and the MMIO space looks like this:
Offset RMID Event ------ ---- ----- 0x0000 0 core_energy 0x0008 0 activity 0x0010 1 core_energy 0x0018 1 activity ... 0x23F0 575 core_energy 0x23F8 575 activityIn addition the XML file provides the units (Joules for
core_energy, Farads for activity) and the type of data (fixed-point binary with bit 63 used to indicate the data is valid, and the low 18 bits as a binary fraction).Finally, each XML file provides a 32-bit unique id (or guid) that is used as an index to find the correct XML description file for each telemetry implementation.
The
INTEL_PMT_DISCOVERYdriver providesintel_pmt_get_regions_by_feature()to enumerate the aggregator instances (also referred to as "telemetry regions" in this series) on a platform. It provides:1) guid - so resctrl can determine which events are supported
2) MMIO base address of counters
3) package idResctrl accumulates counts from all aggregators on a package in order to provide a consistent user interface across processor generations.
Directory structure for the telemetry events looks like this:
$ tree /sys/fs/resctrl/mon_data/ /sys/fs/resctrl/mon_data/ mon_data ├── mon_PERF_PKG_00 │ ├── activity │ └── core_energy └── mon_PERF_PKG_01 ├── activity └── core_energy
Quoted 8 lines
Reading the "
core_energy" file from some resctrlmon_datadirectory shows the cumulative energy (in Joules) used by all tasks that ran with the RMID associated with that directory on a given package. Note that "core_energy" reports only energy consumed by CPU cores (data processing units, L1/L2 caches, etc.). It does not include energy used in the "uncore" (L3 cache, on package devices, etc.), or used by memory or I/O devices.
I think this series is close to being ready to pass to the x86 maintainers. To that end I focused a lot on the changelogs with the goal to meet the tip requirements that mostly involved switching to imperative tone. I do not expect that I found all the cases though (and I may also have made some mistakes in my suggested text!) so please ensure the changelogs are in imperative tone and uses consistent terms throughout the series.
If you disagree with any feedback or if any of the feedback is unclear please let us discuss before you spin a new version. Of course it is not required that you follow all feedback but if you don't I would like to learn why.
Please note that I will be offline next week.
Reinette
Luck, Tony
maintainerQuoted 7 lines
I think this series is close to being ready to pass to the x86 maintainers. To that end I focused a lot on the changelogs with the goal to meet the tip requirements that mostly involved switching to imperative tone. I do not expect that I found all the cases though (and I may also have made some mistakes in my suggested text!) so please ensure the changelogs are in imperative tone and uses consistent terms throughout the series.
Quoted 5 lines
If you disagree with any feedback or if any of the feedback is unclear please let us discuss before you spin a new version. Of course it is not required that you follow all feedback but if you don't I would like to learn why.
Please note that I will be offline next week.
Reinette,
I took one fast pass through all your comments. I think they all look good (and I believe I understand each one). Thanks for all the suggestions.
I'll try to keep (better) notes on what I change as I work through each patch so I'll have a summary of any areas that I'm unsure about for you to read when you get back before I post v9.
Enjoy your time away.
-Tony
Luck, Tony
maintainerQuoted 19 lines · Tony
Quoted 7 lines
I think this series is close to being ready to pass to the x86 maintainers. To that end I focused a lot on the changelogs with the goal to meet the tip requirements that mostly involved switching to imperative tone. I do not expect that I found all the cases though (and I may also have made some mistakes in my suggested text!) so please ensure the changelogs are in imperative tone and uses consistent terms throughout the series.
Quoted 5 lines
If you disagree with any feedback or if any of the feedback is unclear please let us discuss before you spin a new version. Of course it is not required that you follow all feedback but if you don't I would like to learn why.
Please note that I will be offline next week.
Reinette,
I took one fast pass through all your comments. I think they all look good (and I believe I understand each one). Thanks for all the suggestions.
Quoted 5 lines
I'll try to keep (better) notes on what I change as I work through each patch so I'll have a summary of any areas that I'm unsure about for you to read when you get back before I post v9.
Enjoy your time away.
Reinette,
I've completed a longer, slower, pass through making changes to prepare for v9. Summary of changes per patch below. I didn't disagree with any of your suggestions.
The bulk of the changes are small, and localized to each patch. The exception being removal of pkg_mmio_info[] which dropped patch 18 (which just counted regions prior to allocation of pkg_mmio_info[]) and patch 19 (which finished filling out the details.
discover_events() is now named enable_events(), since there are almost no "steps" involved, it doesn't have a header comment. The name now describes what it does.
Theoretically skip_this_region() might find some regions unusable, while others in the same pmt_feature_group are OK. To handle this I zero the telemetry_region::addr so that intel_aet_read_event() can easily skip "bad" regions.
I've pushed a rdt-aet-v9-wip branch to:
if you want to take a quick look at the end result before I patch bomb the list.
-Tony
--- cover ---INTEL_PMT_DISCOVERY -> INTEL_PMT_TELEMETRY
--- 1 ---
No change
--- 2 ---
No change
--- 3 ---
No change
--- 4 ---
No change
--- 5 ---
"The "type" field provides" -> "rdt_domain_hdr::type provides" Update final paragraph of commit message as suggested.
--- 6 ---
Code: in domain_add_cpu_mon() change WARN_ON_ONCE(1); in default case to
pr_warn_once("Unknown resource rid=%d\n", r->rid);
--- 7 ---
Code: in domain_remove_cpu_mon() move domain_header_is_valid()to
immediately before container_of() and switch check from r->rid to hard-coded RDT_RESOURCE_L3. s/list_del_rcu(&d->hdr.list);/list_del_rcu(&hdr->list);/
"separated" -> "separate"
"can skip" -> "skips"
--- 8 ---
Code: in domain_remove_cpu_ctrl() move domain_header_is_valid()
to immediately before container_of(). s/list_del_rcu(&d->hdr.list);/list_del_rcu(&hdr->list);/ (moved here from patch 9)
"refactor" -> "refactor domain_remove_cpu_ctrl()"
--- 9 ---
Change second paragraph of commit comment as suggested.
"so the rmid_read::d field is replaced" -> "so replace the L3 specific domain pointer rmid_read::d with rmid_read::hdr that points to the generic domain header"
Use imperative tone for last paragraph "Update kerneldoc for mon_data::sum ..."
--- 10 ---
Change rdt_mon_domain to rdt_l3_mon_domain in comment above logical_rmid_to_physical_rmid()
Replace entire commit comment with improved version.
--- 11 ---
"different resources" -> "a different resource"
"these functions" -> "the L3 resource specific functions"
"Two groups of functions renamed here:" -> "Rename three groups of functions:" Added rdt_get_mon_l3_config() to list of renamed functions to put the "l3" before the "mon" for consistency.
When changing names for resctrl_mon_resource_{init,exit} add the "l3_" before "mon" for consistency with other *l3_mon*" naming.
--- 12 ---
"to lower levels" -> "via the mon_data and rmid_read structures to the functions finally reading the monitoring data."
Replace 3rd paragraph of commit comment with supplied better version.
--- 13 ---
Code: In cpu_on_correct_domain() s/return -EINVAL;/return false;/
--- 14 ---
Code: Move definition of MAX_BINARY_BITS from <linux/resctrl.h> to
fs/resctrl/internal.h.
Be explicit in commit comment that the file system makes the determination on which events can be displayed in floating point format.
--- 15 ---
"asyncronnous" -> "asynchronous"
"for these drivers" -> "of these drivers"
"are called" -> "completes"
"But expectations" -> "Expectations"
"The call is made with no locks held." -> "resctrl filesystem calls the hook with no locks held."
--- 16 ---
s/CPU hotplug/CPU hot plug/
Add Reinette's RB tag.
--- 17 ---
Code:
"OOBMSM" -> "INTEL_PMT_TELEMETRY"
"INTEL_PMT_DISCOVERY" -> "INTEL_PMT_TELEMETRY"
re-wrap comment for get_pmt_feature() to use 80 columns. "OOBMSM discovery" -> "INTEL_PMT_TELEMETRY"
Add the intel_pmt_put_feature_group() calls to intel_aet_exit() to match the intel_pmt_get_regions_by_feature() calls in get_pmt_feature() using a new macro for_each_enabled_event_group().
Rename discover_events() to enable_events()
Add period at end of help text in arch/x86/Kconfig.
"Data for telemetry events is collected by each CPU and sent" ->
"Each CPU collects data for telemetry events that it sends"
"is changed" -> "changes"
"or when two milliseconds have elapsed" -> "or when a two millisecond timer expires" "mad" -> "made"
"Enumeration of support for telemetry events is done" ->
"The INTEL_PMT_TELEMETRY driver enumerates support for telemetry events." Drop references to INTEL_PMT_DISCOVERY driver.
Merge last two paragraphs of commit message.
Reformat commit to use more of page width.
Add maintainer note about checkpatch complaints for DEFINE_FREE()
--- 18 ---
Dropped. See new patch 0019
--- 19 ---
Dropped. See new patch 0019
--- 20 ---
Now 0018
Rewrite opening paragraph to avoid "continuation of the subject"
Add note/link on the source of the XML files that describe events.
--- 21 ---
Now 0019
Drop "vague first sentence" of second paragraph.
--- NEW 0020 ---
Replaces most of parts 18/32 and 19/32.
Contains skip_this_region() from patch 18/32, but skips all the code to count regions and allocat pkg_mmio_info[].
Also includes event enabling code from 22/32
--- 22 ---
Now 0021
Modify intel_aet_read_event() to dig into pmt_event::pfg to find the MMIO base addresses that v8 patch stored in the pkg_mmio_info[] structures.
--- 23 ---
Now 0022
Add domain_header_is_valid() check in domain_remove_cpu_mon() before using container_of().
"There are structures" -> "There are per domain structures ..."
Replace my commit fix description with better version from Reinette.
--- 24 ---
Unparseable last sentence of commit message replaced with details and examples.
--- 25 ---
RMIDS -> RMIDs
"Adjusted downwards ..." -> "May be adjusted downwards ..." check_rmid_count() -> all_regions_have_sufficient_rmid()
"Potentially disable" -> "Disable"
Add comment:
/* e->num_rmids only adjusted lower if user forces an unusable region to be usable */
--- 26 ---
Add "during resctrl initialization" and "during resctrl exit" to commit background statement.
Add "closid_num_dirty_rmid[]" to be specific about what is being allocated/freed.
--- 27 ---
"mon capable" -> "mon_capable" (three times)
"alloc capable" -> "alloc_capable" "rdt_l3_mon_domain::states[]" -> "rdt_l3_mon_domain::mbm_states[] and +rdt_l3_mon_domain::rmid_busy_llc"
"the number of RMIDs" -> "the system's number of RMIDs"
--- 28 ---
Add comment to setup_rmid_lru_list() to note that rmid_ptrs[] is allocated of first mount and is reused on subsequent mounts. It is freed in resctrl_exit().
Lock/unlock rdtgroup_mutex around body of free_rmid_lru_list()
Rewrite commit based on suggestions with some modifications to explain why error paths in rdt_get_tree() do not call free_rmid_lru_list().
--- 29 ---
TODO: recheck for use of "CPU hot plug notifiers" may have been called "hooks", "callbacks", and "handlers" through this series.
--- 30 ---
"a resource" -> "a monitoring resource"
--- 31 ---
"last_update_timestamp" -> "agg_last_update_timestamp" in commit comment
Move creation of debugfs files to the end of enable_events().
Rewrite to work based on event_group::pfg since event_group::pkginfo[] is gone.
--- 32 ---
Describe "num_rmids" file values independently for L3 and telemetry. Move the note about upper bound on directory creation to its own paragraph to say it is the smaller of reported "num_rmids" values.
"or of a processor package" -> "another for each processor package"
Change paragraph about contents of subdirectories of mon_data to gize example file names instead of hard coding specifics.
prescence -> presence
will vary -> may vary last_update_timestamp -> agg_last_update_timestamp
Simplify commit comment as suggested.
Reinette Chatre
maintainerHi Tony,
Quoted 24 lines · Tony
Quoted 23 lines · Tony
Quoted 7 lines
I think this series is close to being ready to pass to the x86 maintainers. To that end I focused a lot on the changelogs with the goal to meet the tip requirements that mostly involved switching to imperative tone. I do not expect that I found all the cases though (and I may also have made some mistakes in my suggested text!) so please ensure the changelogs are in imperative tone and uses consistent terms throughout the series.
Quoted 5 lines
If you disagree with any feedback or if any of the feedback is unclear please let us discuss before you spin a new version. Of course it is not required that you follow all feedback but if you don't I would like to learn why.
Please note that I will be offline next week.
Reinette,
I took one fast pass through all your comments. I think they all look good (and I believe I understand each one). Thanks for all the suggestions.
I'll try to keep (better) notes on what I change as I work through each patch so I'll have a summary of any areas that I'm unsure about for you to read when you get back before I post v9.
Quoted 7 lines
Quoted 1 line
Enjoy your time away.
Reinette,
I've completed a longer, slower, pass through making changes to prepare for v9. Summary of changes per patch below. I didn't disagree with any of your suggestions.
For me the item that I expected may need discussion is the use of active_event_groups that no longer exists in v9.
Quoted 6 lines
The bulk of the changes are small, and localized to each patch. The exception being removal of pkg_mmio_info[] which dropped patch 18 (which just counted regions prior to allocation of pkg_mmio_info[]) and patch 19 (which finished filling out the details.
Quoted 8 lines
discover_events()is now namedenable_events(), since there are almost no "steps" involved, it doesn't have a header comment. The name now describes what it does.Theoretically
skip_this_region()might find some regions unusable, while others in the samepmt_feature_groupare OK. To handle this I zero thetelemetry_region::addrso thatintel_aet_read_event()can easily skip "bad" regions.
This is a significant change that simplifies the implementation a lot. Even so, it is concerning that resctrl takes liberty to reach in and modify INTEL_PMT_TELEMETRY's data structure for its convenience though. Could the changelog motivate why it is ok and safe to do so? Should something like this not rather be done with a helper exposed by subsystem (INTEL_PMT_TELEMETRY) to be able to track such changes?
Reinette
Luck, Tony
maintainerQuoted 29 lines · Reinette Chatre
Hi Tony,
Quoted 26 lines · Tony
Quoted 24 lines · Tony
Quoted 7 lines
I think this series is close to being ready to pass to the x86 maintainers. To that end I focused a lot on the changelogs with the goal to meet the tip requirements that mostly involved switching to imperative tone. I do not expect that I found all the cases though (and I may also have made some mistakes in my suggested text!) so please ensure the changelogs are in imperative tone and uses consistent terms throughout the series.
Quoted 5 lines
If you disagree with any feedback or if any of the feedback is unclear please let us discuss before you spin a new version. Of course it is not required that you follow all feedback but if you don't I would like to learn why.
Please note that I will be offline next week.
Reinette,
I took one fast pass through all your comments. I think they all look good (and I believe I understand each one). Thanks for all the suggestions.
I'll try to keep (better) notes on what I change as I work through each patch so I'll have a summary of any areas that I'm unsure about for you to read when you get back before I post v9.
Enjoy your time away.
Quoted 8 lines
Quoted 5 lines
Reinette,
I've completed a longer, slower, pass through making changes to prepare for v9. Summary of changes per patch below. I didn't disagree with any of your suggestions.
For me the item that I expected may need discussion is the use of
active_event_groupsthat no longer exists in v9.
Yes. It was removed as part of the refactor to drop the pkg_mmio_info[] array.
Quoted 16 lines
Quoted 7 lines
The bulk of the changes are small, and localized to each patch. The exception being removal of pkg_mmio_info[] which dropped patch 18 (which just counted regions prior to allocation of pkg_mmio_info[]) and patch 19 (which finished filling out the details.
Quoted 8 lines
discover_events()is now namedenable_events(), since there are almost no "steps" involved, it doesn't have a header comment. The name now describes what it does.Theoretically
skip_this_region()might find some regions unusable, while others in the samepmt_feature_groupare OK. To handle this I zero thetelemetry_region::addrso thatintel_aet_read_event()can easily skip "bad" regions.
Quoted 6 lines
This is a significant change that simplifies the implementation a lot. Even so, it is concerning that resctrl takes liberty to reach in and modify INTEL_PMT_TELEMETRY's data structure for its convenience though. Could the changelog motivate why it is ok and safe to do so? Should something like this not rather be done with a helper exposed by subsystem (
INTEL_PMT_TELEMETRY) to be able to track such changes?
I can update the commit message to explain. I did check how the INTEL_PMT_TELEMETRY code handles intel_pmt_put_feature_group(). It just does kref_put() on pmt_feature_group::kref which results in a call to pmt_feature_group_release() which simply does a kfree() for the structure. So it doesn't care if I modify any fields (except for kref!)
If INTEL_PMT_TELEMETRY did care, it would have marked the return pointer from intel_pmt_get_regions_by_feature() as "const".
If that isn't sufficient, can you expand on your thoughts about a helper in the INTEL_PMT_TELEMETRY subsystem?
Quoted 1 line
Reinette
-Tony
Reinette Chatre
maintainerHi Tony,
Quoted 65 lines · Tony
Quoted 29 lines · Reinette Chatre
Hi Tony,
Quoted 26 lines · Tony
Quoted 24 lines · Tony
Quoted 7 lines
I think this series is close to being ready to pass to the x86 maintainers. To that end I focused a lot on the changelogs with the goal to meet the tip requirements that mostly involved switching to imperative tone. I do not expect that I found all the cases though (and I may also have made some mistakes in my suggested text!) so please ensure the changelogs are in imperative tone and uses consistent terms throughout the series.
Quoted 5 lines
If you disagree with any feedback or if any of the feedback is unclear please let us discuss before you spin a new version. Of course it is not required that you follow all feedback but if you don't I would like to learn why.
Please note that I will be offline next week.
Reinette,
I took one fast pass through all your comments. I think they all look good (and I believe I understand each one). Thanks for all the suggestions.
I'll try to keep (better) notes on what I change as I work through each patch so I'll have a summary of any areas that I'm unsure about for you to read when you get back before I post v9.
Enjoy your time away.
Quoted 8 lines
Quoted 5 lines
Reinette,
I've completed a longer, slower, pass through making changes to prepare for v9. Summary of changes per patch below. I didn't disagree with any of your suggestions.
For me the item that I expected may need discussion is the use of
active_event_groupsthat no longer exists in v9.Yes. It was removed as part of the refactor to drop the pkg_mmio_info[] array.
Quoted 16 lines
Quoted 7 lines
The bulk of the changes are small, and localized to each patch. The exception being removal of pkg_mmio_info[] which dropped patch 18 (which just counted regions prior to allocation of pkg_mmio_info[]) and patch 19 (which finished filling out the details.
Quoted 8 lines
discover_events()is now namedenable_events(), since there are almost no "steps" involved, it doesn't have a header comment. The name now describes what it does.Theoretically
skip_this_region()might find some regions unusable, while others in the samepmt_feature_groupare OK. To handle this I zero thetelemetry_region::addrso thatintel_aet_read_event()can easily skip "bad" regions.Quoted 6 lines
This is a significant change that simplifies the implementation a lot. Even so, it is concerning that resctrl takes liberty to reach in and modify INTEL_PMT_TELEMETRY's data structure for its convenience though. Could the changelog motivate why it is ok and safe to do so? Should something like this not rather be done with a helper exposed by subsystem (
INTEL_PMT_TELEMETRY) to be able to track such changes?
Quoted 5 lines
I can update the commit message to explain. I did check how the
INTEL_PMT_TELEMETRYcode handlesintel_pmt_put_feature_group(). It just doeskref_put()onpmt_feature_group::krefwhich results in a call topmt_feature_group_release()which simply does akfree()for the structure. So it doesn't care if I modify any fields (except for kref!)
My assumption was that "getting" a reference means that there is a single object to which multiple users can obtain a reference and then the object is released when the final reference is dropped. Now after looking more closely at intel_pmt_get_regions_by_feature() (btw, it is still remapped to fake_intel_pmt_get_regions_by_feature in the branch you provide) I see that every caller gets a fresh copy of a struct pmt_feature_group and not a reference to an existing struct pmt_feature_group as I assumed. This is unexpected to me and not clear to me why the reference counting is needed in INTEL_PMT_TELEMETRY. Are there any kref_get()/kref_put() on the pmt_feature_group's kref?
Quoted 5 lines
If
INTEL_PMT_TELEMETRYdid care, it would have marked the return pointer fromintel_pmt_get_regions_by_feature()as "const".If that isn't sufficient, can you expand on your thoughts about a helper in the
INTEL_PMT_TELEMETRYsubsystem?
Updating the changelog to highlight that INTEL_PMT_TELEMETRY provides a copy of a struct pmt_feature_group for resctrl's private use instead of a reference to an existing one will be sufficient.
Thank you
Reinette
Luck, Tony
maintainerQuoted 6 lines
Quoted 2 lines
If that isn't sufficient, can you expand on your thoughts about a helper in the
INTEL_PMT_TELEMETRYsubsystem?Updating the changelog to highlight that
INTEL_PMT_TELEMETRYprovides a copy of a structpmt_feature_groupfor resctrl's private use instead of a reference to an existing one will be sufficient..
Okay. I will update the comment.
I checked with David about whether the resources might be unmapped underneath us since there is no additional reference taken when INTEL_PMT_TELEMETRY hands us this copy. The answer is currently "no". The mappings would only be released if the INTEL_PMT_TELEMTRY driver were unloaded. But we require the driver to be built-in so that we can call from resctrl.
This could change if resctrl ever becomes a loadable module and we remove the requirement that INTEL_PMT_TELEMTRY be built in.
-Tony