License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 15:07:57 +01:00
/* SPDX-License-Identifier: GPL-2.0 */
2018-11-21 20:28:25 +00:00
# ifndef _ASM_X86_RESCTRL_INTERNAL_H
# define _ASM_X86_RESCTRL_INTERNAL_H
2016-10-22 06:19:54 -07:00
x86/resctrl: Split struct rdt_resource
resctrl is the defacto Linux ABI for SoC resource partitioning features.
To support it on another architecture, it needs to be abstracted from
the features provided by Intel RDT and AMD PQoS, and moved to /fs/.
struct rdt_resource contains a mix of architecture private details
and properties of the filesystem interface user-space uses.
Start by splitting struct rdt_resource, into an architecture private
'hw' struct, which contains the common resctrl structure that would be
used by any architecture. The foreach helpers are most commonly used by
the filesystem code, and should return the common resctrl structure.
for_each_rdt_resource() is changed to walk the common structure in its
parent arch private structure.
Move as much of the structure as possible into the common structure
in the core code's header file. The x86 hardware accessors remain
part of the architecture private code, as do num_closid, mon_scale
and mbm_width.
mon_scale and mbm_width are used to detect overflow of the hardware
counters, and convert them from their native size to bytes. Any
cross-architecture abstraction should be in terms of bytes, making
these properties private.
The hardware's num_closid is kept in the private structure to force the
filesystem code to use a helper to access it. MPAM would return a single
value for the system, regardless of the resource. Using the helper
prevents this field from being confused with the version of num_closid
that is being exposed to user-space (added in a later patch).
After this split, filesystem code touching a 'hw' struct indicates
where an abstraction is needed.
Splitting this structure only moves types around, and should not lead
to any change in behaviour.
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Jamie Iles <jamie@nuviainc.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Tested-by: Babu Moger <babu.moger@amd.com>
Link: https://lkml.kernel.org/r/20210728170637.25610-2-james.morse@arm.com
2021-07-28 17:06:14 +00:00
# include <linux/resctrl.h>
2017-02-02 17:54:15 +01:00
# include <linux/sched.h>
2016-11-02 17:51:17 +01:00
# include <linux/kernfs.h>
kernfs, sysfs, cgroup, intel_rdt: Support fs_context
Make kernfs support superblock creation/mount/remount with fs_context.
This requires that sysfs, cgroup and intel_rdt, which are built on kernfs,
be made to support fs_context also.
Notes:
(1) A kernfs_fs_context struct is created to wrap fs_context and the
kernfs mount parameters are moved in here (or are in fs_context).
(2) kernfs_mount{,_ns}() are made into kernfs_get_tree(). The extra
namespace tag parameter is passed in the context if desired
(3) kernfs_free_fs_context() is provided as a destructor for the
kernfs_fs_context struct, but for the moment it does nothing except
get called in the right places.
(4) sysfs doesn't wrap kernfs_fs_context since it has no parameters to
pass, but possibly this should be done anyway in case someone wants to
add a parameter in future.
(5) A cgroup_fs_context struct is created to wrap kernfs_fs_context and
the cgroup v1 and v2 mount parameters are all moved there.
(6) cgroup1 parameter parsing error messages are now handled by invalf(),
which allows userspace to collect them directly.
(7) cgroup1 parameter cleanup is now done in the context destructor rather
than in the mount/get_tree and remount functions.
Weirdies:
(*) cgroup_do_get_tree() calls cset_cgroup_from_root() with locks held,
but then uses the resulting pointer after dropping the locks. I'm
told this is okay and needs commenting.
(*) The cgroup refcount web. This really needs documenting.
(*) cgroup2 only has one root?
Add a suggestion from Thomas Gleixner in which the RDT enablement code is
placed into its own function.
[folded a leak fix from Andrey Vagin]
Signed-off-by: David Howells <dhowells@redhat.com>
cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
cc: Tejun Heo <tj@kernel.org>
cc: Li Zefan <lizefan@huawei.com>
cc: Johannes Weiner <hannes@cmpxchg.org>
cc: cgroups@vger.kernel.org
cc: fenghua.yu@intel.com
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2018-11-01 23:07:26 +00:00
# include <linux/fs_context.h>
2016-10-28 15:04:42 -07:00
# include <linux/jump_label.h>
2018-11-21 20:28:31 +00:00
# define MSR_IA32_L3_QOS_CFG 0xc81
# define MSR_IA32_L2_QOS_CFG 0xc82
# define MSR_IA32_L3_CBM_BASE 0xc90
# define MSR_IA32_L2_CBM_BASE 0xd10
# define MSR_IA32_MBA_THRTL_BASE 0xd50
2018-11-21 20:28:45 +00:00
# define MSR_IA32_MBA_BW_BASE 0xc0000200
2016-10-22 06:19:54 -07:00
2018-11-21 20:28:31 +00:00
# define MSR_IA32_QM_CTR 0x0c8e
# define MSR_IA32_QM_EVTSEL 0x0c8d
2016-10-28 15:04:42 -07:00
2018-11-21 20:28:31 +00:00
# define L3_QOS_CDP_ENABLE 0x01ULL
# define L2_QOS_CDP_ENABLE 0x01ULL
2017-12-20 14:57:23 -08:00
2017-07-25 14:14:27 -07:00
/*
* Event IDs are used to program IA32_QM_EVTSEL before reading event
* counter from IA32_QM_CTR
*/
# define QOS_L3_OCCUP_EVENT_ID 0x01
# define QOS_L3_MBM_TOTAL_EVENT_ID 0x02
# define QOS_L3_MBM_LOCAL_EVENT_ID 0x03
2017-07-25 14:14:45 -07:00
2017-08-15 18:00:43 -07:00
# define CQM_LIMBOCHECK_INTERVAL 1000
2020-05-05 15:36:18 -07:00
# define MBM_CNTR_WIDTH_BASE 24
2017-07-25 14:14:47 -07:00
# define MBM_OVERFLOW_INTERVAL 1000
2018-04-20 15:36:21 -07:00
# define MAX_MBA_BW 100u
2018-11-21 20:28:31 +00:00
# define MBA_IS_LINEAR 0x4
# define MBA_MAX_MBPS U32_MAX
2018-11-21 20:28:45 +00:00
# define MAX_MBA_BW_AMD 0x800
2020-06-04 14:45:16 -05:00
# define MBM_CNTR_WIDTH_OFFSET_AMD 20
2017-07-25 14:14:45 -07:00
2017-07-25 14:14:28 -07:00
# define RMID_VAL_ERROR BIT_ULL(63)
# define RMID_VAL_UNAVAIL BIT_ULL(62)
2020-05-05 15:36:18 -07:00
/*
* With the above fields in use 62 bits remain in MSR_IA32_QM_CTR for
* data to be returned . The counter width is discovered from the hardware
* as an offset from MBM_CNTR_WIDTH_BASE .
*/
# define MBM_CNTR_WIDTH_OFFSET_MAX (62 - MBM_CNTR_WIDTH_BASE)
2017-07-25 14:14:27 -07:00
kernfs, sysfs, cgroup, intel_rdt: Support fs_context
Make kernfs support superblock creation/mount/remount with fs_context.
This requires that sysfs, cgroup and intel_rdt, which are built on kernfs,
be made to support fs_context also.
Notes:
(1) A kernfs_fs_context struct is created to wrap fs_context and the
kernfs mount parameters are moved in here (or are in fs_context).
(2) kernfs_mount{,_ns}() are made into kernfs_get_tree(). The extra
namespace tag parameter is passed in the context if desired
(3) kernfs_free_fs_context() is provided as a destructor for the
kernfs_fs_context struct, but for the moment it does nothing except
get called in the right places.
(4) sysfs doesn't wrap kernfs_fs_context since it has no parameters to
pass, but possibly this should be done anyway in case someone wants to
add a parameter in future.
(5) A cgroup_fs_context struct is created to wrap kernfs_fs_context and
the cgroup v1 and v2 mount parameters are all moved there.
(6) cgroup1 parameter parsing error messages are now handled by invalf(),
which allows userspace to collect them directly.
(7) cgroup1 parameter cleanup is now done in the context destructor rather
than in the mount/get_tree and remount functions.
Weirdies:
(*) cgroup_do_get_tree() calls cset_cgroup_from_root() with locks held,
but then uses the resulting pointer after dropping the locks. I'm
told this is okay and needs commenting.
(*) The cgroup refcount web. This really needs documenting.
(*) cgroup2 only has one root?
Add a suggestion from Thomas Gleixner in which the RDT enablement code is
placed into its own function.
[folded a leak fix from Andrey Vagin]
Signed-off-by: David Howells <dhowells@redhat.com>
cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
cc: Tejun Heo <tj@kernel.org>
cc: Li Zefan <lizefan@huawei.com>
cc: Johannes Weiner <hannes@cmpxchg.org>
cc: cgroups@vger.kernel.org
cc: fenghua.yu@intel.com
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2018-11-01 23:07:26 +00:00
struct rdt_fs_context {
struct kernfs_fs_context kfc ;
bool enable_cdpl2 ;
bool enable_cdpl3 ;
bool enable_mba_mbps ;
} ;
static inline struct rdt_fs_context * rdt_fc2context ( struct fs_context * fc )
{
struct kernfs_fs_context * kfc = fc - > fs_private ;
return container_of ( kfc , struct rdt_fs_context , kfc ) ;
}
2017-07-25 14:14:47 -07:00
DECLARE_STATIC_KEY_FALSE ( rdt_enable_key ) ;
2019-12-12 04:05:05 +08:00
DECLARE_STATIC_KEY_FALSE ( rdt_mon_enable_key ) ;
2017-07-25 14:14:47 -07:00
2017-07-25 14:14:27 -07:00
/**
* struct mon_evt - Entry in the event list of a resource
* @ evtid : event id
* @ name : name of the event
2021-06-19 00:32:06 +02:00
* @ list : entry in & rdt_resource - > evt_list
2017-07-25 14:14:27 -07:00
*/
struct mon_evt {
u32 evtid ;
char * name ;
struct list_head list ;
} ;
2017-07-25 14:14:38 -07:00
/**
2021-06-19 00:32:06 +02:00
* union mon_data_bits - Monitoring details for each event file
* @ priv : Used to store monitoring event data in @ u
* as kernfs private data
* @ rid : Resource id associated with the event file
2017-07-25 14:14:38 -07:00
* @ evtid : Event id associated with the event file
* @ domid : The domain to which the event file belongs
2021-06-19 00:32:06 +02:00
* @ u : Name of the bit fields struct
2017-07-25 14:14:38 -07:00
*/
union mon_data_bits {
void * priv ;
struct {
unsigned int rid : 10 ;
unsigned int evtid : 8 ;
unsigned int domid : 14 ;
} u ;
} ;
struct rmid_read {
struct rdtgroup * rgrp ;
2020-05-05 15:36:16 -07:00
struct rdt_resource * r ;
2017-07-25 14:14:45 -07:00
struct rdt_domain * d ;
2017-07-25 14:14:38 -07:00
int evtid ;
2017-07-25 14:14:46 -07:00
bool first ;
2017-07-25 14:14:38 -07:00
u64 val ;
} ;
2018-11-21 20:28:27 +00:00
extern unsigned int resctrl_cqm_threshold ;
2017-07-25 14:14:27 -07:00
extern bool rdt_alloc_capable ;
extern bool rdt_mon_capable ;
extern unsigned int rdt_mon_features ;
2021-07-28 17:06:16 +00:00
extern struct list_head resctrl_schema_all ;
2017-07-25 14:14:32 -07:00
enum rdt_group_type {
RDTCTRL_GROUP = 0 ,
RDTMON_GROUP ,
RDT_NUM_GROUP ,
} ;
2018-06-22 15:41:54 -07:00
/**
* enum rdtgrp_mode - Mode of a RDT resource group
* @ RDT_MODE_SHAREABLE : This resource group allows sharing of its allocations
2018-06-22 15:42:00 -07:00
* @ RDT_MODE_EXCLUSIVE : No sharing of this resource group ' s allocations allowed
2018-06-22 15:42:08 -07:00
* @ RDT_MODE_PSEUDO_LOCKSETUP : Resource group will be used for Pseudo - Locking
* @ RDT_MODE_PSEUDO_LOCKED : No sharing of this resource group ' s allocations
* allowed AND the allocations are Cache Pseudo - Locked
2021-06-19 00:32:06 +02:00
* @ RDT_NUM_MODES : Total number of modes
2018-06-22 15:41:54 -07:00
*
* The mode of a resource group enables control over the allowed overlap
* between allocations associated with different resource groups ( classes
* of service ) . User is able to modify the mode of a resource group by
* writing to the " mode " resctrl file associated with the resource group .
2018-06-22 15:42:08 -07:00
*
* The " shareable " , " exclusive " , and " pseudo-locksetup " modes are set by
* writing the appropriate text to the " mode " file . A resource group enters
* " pseudo-locked " mode after the schemata is written while the resource
* group is in " pseudo-locksetup " mode .
2018-06-22 15:41:54 -07:00
*/
enum rdtgrp_mode {
RDT_MODE_SHAREABLE = 0 ,
2018-06-22 15:42:00 -07:00
RDT_MODE_EXCLUSIVE ,
2018-06-22 15:42:08 -07:00
RDT_MODE_PSEUDO_LOCKSETUP ,
RDT_MODE_PSEUDO_LOCKED ,
2018-06-22 15:41:54 -07:00
/* Must be last */
RDT_NUM_MODES ,
} ;
2017-07-25 14:14:32 -07:00
/**
* struct mongroup - store mon group ' s data in resctrl fs .
2021-06-19 00:32:06 +02:00
* @ mon_data_kn : kernfs node for the mon_data directory
2017-07-25 14:14:32 -07:00
* @ parent : parent rdtgrp
* @ crdtgrp_list : child rdtgroup node list
* @ rmid : rmid for this rdtgroup
*/
struct mongroup {
2017-07-25 14:14:38 -07:00
struct kernfs_node * mon_data_kn ;
2017-07-25 14:14:32 -07:00
struct rdtgroup * parent ;
struct list_head crdtgrp_list ;
u32 rmid ;
} ;
2018-06-22 15:42:15 -07:00
/**
* struct pseudo_lock_region - pseudo - lock region information
* @ r : RDT resource to which this pseudo - locked region
* belongs
* @ d : RDT domain to which this pseudo - locked region
* belongs
* @ cbm : bitmask of the pseudo - locked region
2018-06-22 15:42:21 -07:00
* @ lock_thread_wq : waitqueue used to wait on the pseudo - locking thread
* completion
* @ thread_done : variable used by waitqueue to test if pseudo - locking
* thread completed
* @ cpu : core associated with the cache on which the setup code
* will be run
* @ line_size : size of the cache lines
* @ size : size of pseudo - locked region in bytes
* @ kmem : the kernel memory associated with pseudo - locked region
2018-06-22 15:42:27 -07:00
* @ minor : minor number of character device associated with this
* region
2018-06-22 15:42:26 -07:00
* @ debugfs_dir : pointer to this region ' s directory in the debugfs
* filesystem
2018-06-22 15:42:30 -07:00
* @ pm_reqs : Power management QoS requests related to this region
2018-06-22 15:42:15 -07:00
*/
struct pseudo_lock_region {
struct rdt_resource * r ;
struct rdt_domain * d ;
u32 cbm ;
2018-06-22 15:42:21 -07:00
wait_queue_head_t lock_thread_wq ;
int thread_done ;
int cpu ;
unsigned int line_size ;
unsigned int size ;
void * kmem ;
2018-06-22 15:42:27 -07:00
unsigned int minor ;
2018-06-22 15:42:26 -07:00
struct dentry * debugfs_dir ;
2018-06-22 15:42:30 -07:00
struct list_head pm_reqs ;
2018-06-22 15:42:15 -07:00
} ;
2016-10-28 15:04:42 -07:00
/**
* struct rdtgroup - store rdtgroup ' s data in resctrl file system .
* @ kn : kernfs node
* @ rdtgroup_list : linked list for all rdtgroups
* @ closid : closid for this rdtgroup
2016-10-28 15:04:45 -07:00
* @ cpu_mask : CPUs assigned to this rdtgroup
2016-10-28 15:04:44 -07:00
* @ flags : status bits
* @ waitcount : how many cpus expect to find this
2016-10-28 15:04:45 -07:00
* group when they acquire rdtgroup_mutex
2017-07-25 14:14:32 -07:00
* @ type : indicates type of this rdtgroup - either
* monitor only or ctrl_mon group
* @ mon : mongroup related data
2018-06-22 15:41:55 -07:00
* @ mode : mode of resource group
2018-06-22 15:42:15 -07:00
* @ plr : pseudo - locked region
2016-10-28 15:04:42 -07:00
*/
struct rdtgroup {
2018-06-22 15:42:15 -07:00
struct kernfs_node * kn ;
struct list_head rdtgroup_list ;
u32 closid ;
struct cpumask cpu_mask ;
int flags ;
atomic_t waitcount ;
enum rdt_group_type type ;
struct mongroup mon ;
enum rdtgrp_mode mode ;
struct pseudo_lock_region * plr ;
2016-10-28 15:04:42 -07:00
} ;
2016-10-28 15:04:44 -07:00
/* rdtgroup.flags */
# define RDT_DELETED 1
2017-04-10 16:52:32 +02:00
/* rftype.flags */
# define RFTYPE_FLAGS_CPUS_LIST 1
2017-07-25 14:14:29 -07:00
/*
* Define the file type flags for base and info directories .
*/
# define RFTYPE_INFO BIT(0)
# define RFTYPE_BASE BIT(1)
# define RF_CTRLSHIFT 4
2017-07-25 14:14:30 -07:00
# define RF_MONSHIFT 5
2017-09-25 16:39:33 -07:00
# define RF_TOPSHIFT 6
2017-07-25 14:14:29 -07:00
# define RFTYPE_CTRL BIT(RF_CTRLSHIFT)
2017-07-25 14:14:30 -07:00
# define RFTYPE_MON BIT(RF_MONSHIFT)
2017-09-25 16:39:33 -07:00
# define RFTYPE_TOP BIT(RF_TOPSHIFT)
2017-07-25 14:14:29 -07:00
# define RFTYPE_RES_CACHE BIT(8)
# define RFTYPE_RES_MB BIT(9)
# define RF_CTRL_INFO (RFTYPE_INFO | RFTYPE_CTRL)
2017-07-25 14:14:30 -07:00
# define RF_MON_INFO (RFTYPE_INFO | RFTYPE_MON)
2017-09-25 16:39:33 -07:00
# define RF_TOP_INFO (RFTYPE_INFO | RFTYPE_TOP)
2017-07-25 14:14:29 -07:00
# define RF_CTRL_BASE (RFTYPE_BASE | RFTYPE_CTRL)
2016-10-28 15:04:42 -07:00
/* List of all resource groups */
extern struct list_head rdt_all_groups ;
2017-04-03 14:44:17 -07:00
extern int max_name_width , max_data_width ;
2016-10-28 15:04:42 -07:00
int __init rdtgroup_init ( void ) ;
2018-06-22 15:42:24 -07:00
void __exit rdtgroup_exit ( void ) ;
2016-10-28 15:04:42 -07:00
2016-10-28 15:04:43 -07:00
/**
* struct rftype - describe each file in the resctrl file system
2017-04-10 11:50:11 +02:00
* @ name : File name
* @ mode : Access mode
* @ kf_ops : File operations
2017-04-10 16:52:32 +02:00
* @ flags : File specific RFTYPE_FLAGS_ * flags
2017-07-25 14:14:29 -07:00
* @ fflags : File specific RF_ * or RFTYPE_ * flags
2017-04-10 11:50:11 +02:00
* @ seq_show : Show content of the file
* @ write : Write to the file
2016-10-28 15:04:43 -07:00
*/
struct rftype {
char * name ;
umode_t mode ;
2020-11-11 00:02:28 +01:00
const struct kernfs_ops * kf_ops ;
2017-04-10 16:52:32 +02:00
unsigned long flags ;
2017-07-25 14:14:29 -07:00
unsigned long fflags ;
2016-10-28 15:04:43 -07:00
int ( * seq_show ) ( struct kernfs_open_file * of ,
struct seq_file * sf , void * v ) ;
/*
* write ( ) is the generic write callback which maps directly to
* kernfs write operation and overrides all other operations .
* Maximum write size is determined by - > max_write_len .
*/
ssize_t ( * write ) ( struct kernfs_open_file * of ,
char * buf , size_t nbytes , loff_t off ) ;
} ;
2017-07-25 14:14:45 -07:00
/**
* struct mbm_state - status for each MBM counter in each domain
* @ chunks : Total data moved ( multiply by rdt_group . mon_scale to get bytes )
2021-06-19 00:32:06 +02:00
* @ prev_msr : Value of IA32_QM_CTR for this RMID last time we read it
2018-04-20 15:36:20 -07:00
* @ prev_bw_msr : Value of previous IA32_QM_CTR for bandwidth counting
2021-06-19 00:32:06 +02:00
* @ prev_bw : The most recent bandwidth in MBps
* @ delta_bw : Difference between the current and previous bandwidth
* @ delta_comp : Indicates whether to compute the delta_bw
2017-07-25 14:14:45 -07:00
*/
struct mbm_state {
u64 chunks ;
u64 prev_msr ;
2018-04-20 15:36:20 -07:00
u64 prev_bw_msr ;
u32 prev_bw ;
u32 delta_bw ;
bool delta_comp ;
2017-07-25 14:14:45 -07:00
} ;
2017-04-14 14:14:31 +02:00
/**
2021-07-28 17:06:15 +00:00
* struct rdt_hw_domain - Arch private attributes of a set of CPUs that share
* a resource
* @ d_resctrl : Properties exposed to the resctrl file system
2017-04-14 14:14:31 +02:00
* @ ctrl_val : array of cache or mem ctrl values ( indexed by CLOSID )
2018-04-20 15:36:18 -07:00
* @ mbps_val : When mba_sc is enabled , this holds the bandwidth in MBps
2021-07-28 17:06:15 +00:00
*
* Members of this structure are accessed via helpers that provide abstraction .
2017-04-14 14:14:31 +02:00
*/
2021-07-28 17:06:15 +00:00
struct rdt_hw_domain {
struct rdt_domain d_resctrl ;
2018-06-22 15:42:15 -07:00
u32 * ctrl_val ;
u32 * mbps_val ;
2017-04-14 14:14:31 +02:00
} ;
2021-07-28 17:06:15 +00:00
static inline struct rdt_hw_domain * resctrl_to_arch_dom ( struct rdt_domain * r )
{
return container_of ( r , struct rdt_hw_domain , d_resctrl ) ;
}
2017-04-14 14:14:31 +02:00
/**
* struct msr_param - set a range of MSRs from a domain
* @ res : The resource to use
* @ low : Beginning index from base MSR
* @ high : End index
*/
struct msr_param {
struct rdt_resource * res ;
int low ;
int high ;
} ;
2017-07-25 14:14:27 -07:00
static inline bool is_llc_occupancy_enabled ( void )
{
return ( rdt_mon_features & ( 1 < < QOS_L3_OCCUP_EVENT_ID ) ) ;
}
2017-07-25 14:14:45 -07:00
static inline bool is_mbm_total_enabled ( void )
{
return ( rdt_mon_features & ( 1 < < QOS_L3_MBM_TOTAL_EVENT_ID ) ) ;
}
static inline bool is_mbm_local_enabled ( void )
{
return ( rdt_mon_features & ( 1 < < QOS_L3_MBM_LOCAL_EVENT_ID ) ) ;
}
static inline bool is_mbm_enabled ( void )
{
return ( is_mbm_total_enabled ( ) | | is_mbm_local_enabled ( ) ) ;
}
2017-07-25 14:14:46 -07:00
static inline bool is_mbm_event ( int e )
{
return ( e > = QOS_L3_MBM_TOTAL_EVENT_ID & &
e < = QOS_L3_MBM_LOCAL_EVENT_ID ) ;
}
2018-09-15 14:58:19 -07:00
struct rdt_parse_data {
struct rdtgroup * rdtgrp ;
char * buf ;
} ;
2016-10-22 06:19:55 -07:00
/**
x86/resctrl: Split struct rdt_resource
resctrl is the defacto Linux ABI for SoC resource partitioning features.
To support it on another architecture, it needs to be abstracted from
the features provided by Intel RDT and AMD PQoS, and moved to /fs/.
struct rdt_resource contains a mix of architecture private details
and properties of the filesystem interface user-space uses.
Start by splitting struct rdt_resource, into an architecture private
'hw' struct, which contains the common resctrl structure that would be
used by any architecture. The foreach helpers are most commonly used by
the filesystem code, and should return the common resctrl structure.
for_each_rdt_resource() is changed to walk the common structure in its
parent arch private structure.
Move as much of the structure as possible into the common structure
in the core code's header file. The x86 hardware accessors remain
part of the architecture private code, as do num_closid, mon_scale
and mbm_width.
mon_scale and mbm_width are used to detect overflow of the hardware
counters, and convert them from their native size to bytes. Any
cross-architecture abstraction should be in terms of bytes, making
these properties private.
The hardware's num_closid is kept in the private structure to force the
filesystem code to use a helper to access it. MPAM would return a single
value for the system, regardless of the resource. Using the helper
prevents this field from being confused with the version of num_closid
that is being exposed to user-space (added in a later patch).
After this split, filesystem code touching a 'hw' struct indicates
where an abstraction is needed.
Splitting this structure only moves types around, and should not lead
to any change in behaviour.
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Jamie Iles <jamie@nuviainc.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Tested-by: Babu Moger <babu.moger@amd.com>
Link: https://lkml.kernel.org/r/20210728170637.25610-2-james.morse@arm.com
2021-07-28 17:06:14 +00:00
* struct rdt_hw_resource - arch private attributes of a resctrl resource
2021-07-28 17:06:18 +00:00
* @ conf_type : The type that should be used when configuring . temporary
x86/resctrl: Split struct rdt_resource
resctrl is the defacto Linux ABI for SoC resource partitioning features.
To support it on another architecture, it needs to be abstracted from
the features provided by Intel RDT and AMD PQoS, and moved to /fs/.
struct rdt_resource contains a mix of architecture private details
and properties of the filesystem interface user-space uses.
Start by splitting struct rdt_resource, into an architecture private
'hw' struct, which contains the common resctrl structure that would be
used by any architecture. The foreach helpers are most commonly used by
the filesystem code, and should return the common resctrl structure.
for_each_rdt_resource() is changed to walk the common structure in its
parent arch private structure.
Move as much of the structure as possible into the common structure
in the core code's header file. The x86 hardware accessors remain
part of the architecture private code, as do num_closid, mon_scale
and mbm_width.
mon_scale and mbm_width are used to detect overflow of the hardware
counters, and convert them from their native size to bytes. Any
cross-architecture abstraction should be in terms of bytes, making
these properties private.
The hardware's num_closid is kept in the private structure to force the
filesystem code to use a helper to access it. MPAM would return a single
value for the system, regardless of the resource. Using the helper
prevents this field from being confused with the version of num_closid
that is being exposed to user-space (added in a later patch).
After this split, filesystem code touching a 'hw' struct indicates
where an abstraction is needed.
Splitting this structure only moves types around, and should not lead
to any change in behaviour.
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Jamie Iles <jamie@nuviainc.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Tested-by: Babu Moger <babu.moger@amd.com>
Link: https://lkml.kernel.org/r/20210728170637.25610-2-james.morse@arm.com
2021-07-28 17:06:14 +00:00
* @ r_resctrl : Attributes of the resource used directly by resctrl .
* @ num_closid : Maximum number of closid this hardware can support .
2017-04-14 13:00:36 +02:00
* @ msr_base : Base MSR address for CBMs
2017-04-14 14:14:31 +02:00
* @ msr_update : Function pointer to update QOS MSRs
2018-11-21 20:28:35 +00:00
* @ mon_scale : cqm counter * mon_scale = occupancy in bytes
2021-06-19 00:32:06 +02:00
* @ mbm_width : Monitor width , to detect and correct for overflow .
x86/resctrl: Split struct rdt_resource
resctrl is the defacto Linux ABI for SoC resource partitioning features.
To support it on another architecture, it needs to be abstracted from
the features provided by Intel RDT and AMD PQoS, and moved to /fs/.
struct rdt_resource contains a mix of architecture private details
and properties of the filesystem interface user-space uses.
Start by splitting struct rdt_resource, into an architecture private
'hw' struct, which contains the common resctrl structure that would be
used by any architecture. The foreach helpers are most commonly used by
the filesystem code, and should return the common resctrl structure.
for_each_rdt_resource() is changed to walk the common structure in its
parent arch private structure.
Move as much of the structure as possible into the common structure
in the core code's header file. The x86 hardware accessors remain
part of the architecture private code, as do num_closid, mon_scale
and mbm_width.
mon_scale and mbm_width are used to detect overflow of the hardware
counters, and convert them from their native size to bytes. Any
cross-architecture abstraction should be in terms of bytes, making
these properties private.
The hardware's num_closid is kept in the private structure to force the
filesystem code to use a helper to access it. MPAM would return a single
value for the system, regardless of the resource. Using the helper
prevents this field from being confused with the version of num_closid
that is being exposed to user-space (added in a later patch).
After this split, filesystem code touching a 'hw' struct indicates
where an abstraction is needed.
Splitting this structure only moves types around, and should not lead
to any change in behaviour.
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Jamie Iles <jamie@nuviainc.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Tested-by: Babu Moger <babu.moger@amd.com>
Link: https://lkml.kernel.org/r/20210728170637.25610-2-james.morse@arm.com
2021-07-28 17:06:14 +00:00
*
* Members of this structure are either private to the architecture
* e . g . mbm_width , or accessed via helpers that provide abstraction . e . g .
* msr_update and msr_base .
2016-10-22 06:19:55 -07:00
*/
x86/resctrl: Split struct rdt_resource
resctrl is the defacto Linux ABI for SoC resource partitioning features.
To support it on another architecture, it needs to be abstracted from
the features provided by Intel RDT and AMD PQoS, and moved to /fs/.
struct rdt_resource contains a mix of architecture private details
and properties of the filesystem interface user-space uses.
Start by splitting struct rdt_resource, into an architecture private
'hw' struct, which contains the common resctrl structure that would be
used by any architecture. The foreach helpers are most commonly used by
the filesystem code, and should return the common resctrl structure.
for_each_rdt_resource() is changed to walk the common structure in its
parent arch private structure.
Move as much of the structure as possible into the common structure
in the core code's header file. The x86 hardware accessors remain
part of the architecture private code, as do num_closid, mon_scale
and mbm_width.
mon_scale and mbm_width are used to detect overflow of the hardware
counters, and convert them from their native size to bytes. Any
cross-architecture abstraction should be in terms of bytes, making
these properties private.
The hardware's num_closid is kept in the private structure to force the
filesystem code to use a helper to access it. MPAM would return a single
value for the system, regardless of the resource. Using the helper
prevents this field from being confused with the version of num_closid
that is being exposed to user-space (added in a later patch).
After this split, filesystem code touching a 'hw' struct indicates
where an abstraction is needed.
Splitting this structure only moves types around, and should not lead
to any change in behaviour.
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Jamie Iles <jamie@nuviainc.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Tested-by: Babu Moger <babu.moger@amd.com>
Link: https://lkml.kernel.org/r/20210728170637.25610-2-james.morse@arm.com
2021-07-28 17:06:14 +00:00
struct rdt_hw_resource {
2021-07-28 17:06:18 +00:00
enum resctrl_conf_type conf_type ;
x86/resctrl: Split struct rdt_resource
resctrl is the defacto Linux ABI for SoC resource partitioning features.
To support it on another architecture, it needs to be abstracted from
the features provided by Intel RDT and AMD PQoS, and moved to /fs/.
struct rdt_resource contains a mix of architecture private details
and properties of the filesystem interface user-space uses.
Start by splitting struct rdt_resource, into an architecture private
'hw' struct, which contains the common resctrl structure that would be
used by any architecture. The foreach helpers are most commonly used by
the filesystem code, and should return the common resctrl structure.
for_each_rdt_resource() is changed to walk the common structure in its
parent arch private structure.
Move as much of the structure as possible into the common structure
in the core code's header file. The x86 hardware accessors remain
part of the architecture private code, as do num_closid, mon_scale
and mbm_width.
mon_scale and mbm_width are used to detect overflow of the hardware
counters, and convert them from their native size to bytes. Any
cross-architecture abstraction should be in terms of bytes, making
these properties private.
The hardware's num_closid is kept in the private structure to force the
filesystem code to use a helper to access it. MPAM would return a single
value for the system, regardless of the resource. Using the helper
prevents this field from being confused with the version of num_closid
that is being exposed to user-space (added in a later patch).
After this split, filesystem code touching a 'hw' struct indicates
where an abstraction is needed.
Splitting this structure only moves types around, and should not lead
to any change in behaviour.
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Jamie Iles <jamie@nuviainc.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Tested-by: Babu Moger <babu.moger@amd.com>
Link: https://lkml.kernel.org/r/20210728170637.25610-2-james.morse@arm.com
2021-07-28 17:06:14 +00:00
struct rdt_resource r_resctrl ;
2016-10-22 06:19:55 -07:00
int num_closid ;
2017-04-14 13:00:36 +02:00
unsigned int msr_base ;
2017-04-14 14:14:31 +02:00
void ( * msr_update ) ( struct rdt_domain * d , struct msr_param * m ,
struct rdt_resource * r ) ;
2017-07-25 14:14:27 -07:00
unsigned int mon_scale ;
2020-05-05 15:36:16 -07:00
unsigned int mbm_width ;
2016-10-22 06:19:55 -07:00
} ;
x86/resctrl: Split struct rdt_resource
resctrl is the defacto Linux ABI for SoC resource partitioning features.
To support it on another architecture, it needs to be abstracted from
the features provided by Intel RDT and AMD PQoS, and moved to /fs/.
struct rdt_resource contains a mix of architecture private details
and properties of the filesystem interface user-space uses.
Start by splitting struct rdt_resource, into an architecture private
'hw' struct, which contains the common resctrl structure that would be
used by any architecture. The foreach helpers are most commonly used by
the filesystem code, and should return the common resctrl structure.
for_each_rdt_resource() is changed to walk the common structure in its
parent arch private structure.
Move as much of the structure as possible into the common structure
in the core code's header file. The x86 hardware accessors remain
part of the architecture private code, as do num_closid, mon_scale
and mbm_width.
mon_scale and mbm_width are used to detect overflow of the hardware
counters, and convert them from their native size to bytes. Any
cross-architecture abstraction should be in terms of bytes, making
these properties private.
The hardware's num_closid is kept in the private structure to force the
filesystem code to use a helper to access it. MPAM would return a single
value for the system, regardless of the resource. Using the helper
prevents this field from being confused with the version of num_closid
that is being exposed to user-space (added in a later patch).
After this split, filesystem code touching a 'hw' struct indicates
where an abstraction is needed.
Splitting this structure only moves types around, and should not lead
to any change in behaviour.
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Jamie Iles <jamie@nuviainc.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Tested-by: Babu Moger <babu.moger@amd.com>
Link: https://lkml.kernel.org/r/20210728170637.25610-2-james.morse@arm.com
2021-07-28 17:06:14 +00:00
static inline struct rdt_hw_resource * resctrl_to_arch_res ( struct rdt_resource * r )
{
return container_of ( r , struct rdt_hw_resource , r_resctrl ) ;
}
2018-09-15 14:58:19 -07:00
int parse_cbm ( struct rdt_parse_data * data , struct rdt_resource * r ,
struct rdt_domain * d ) ;
2020-07-08 16:39:27 +00:00
int parse_bw ( struct rdt_parse_data * data , struct rdt_resource * r ,
struct rdt_domain * d ) ;
2017-04-07 17:33:54 -07:00
2016-10-28 15:04:41 -07:00
extern struct mutex rdtgroup_mutex ;
x86/resctrl: Split struct rdt_resource
resctrl is the defacto Linux ABI for SoC resource partitioning features.
To support it on another architecture, it needs to be abstracted from
the features provided by Intel RDT and AMD PQoS, and moved to /fs/.
struct rdt_resource contains a mix of architecture private details
and properties of the filesystem interface user-space uses.
Start by splitting struct rdt_resource, into an architecture private
'hw' struct, which contains the common resctrl structure that would be
used by any architecture. The foreach helpers are most commonly used by
the filesystem code, and should return the common resctrl structure.
for_each_rdt_resource() is changed to walk the common structure in its
parent arch private structure.
Move as much of the structure as possible into the common structure
in the core code's header file. The x86 hardware accessors remain
part of the architecture private code, as do num_closid, mon_scale
and mbm_width.
mon_scale and mbm_width are used to detect overflow of the hardware
counters, and convert them from their native size to bytes. Any
cross-architecture abstraction should be in terms of bytes, making
these properties private.
The hardware's num_closid is kept in the private structure to force the
filesystem code to use a helper to access it. MPAM would return a single
value for the system, regardless of the resource. Using the helper
prevents this field from being confused with the version of num_closid
that is being exposed to user-space (added in a later patch).
After this split, filesystem code touching a 'hw' struct indicates
where an abstraction is needed.
Splitting this structure only moves types around, and should not lead
to any change in behaviour.
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Jamie Iles <jamie@nuviainc.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Tested-by: Babu Moger <babu.moger@amd.com>
Link: https://lkml.kernel.org/r/20210728170637.25610-2-james.morse@arm.com
2021-07-28 17:06:14 +00:00
extern struct rdt_hw_resource rdt_resources_all [ ] ;
2016-10-28 15:04:42 -07:00
extern struct rdtgroup rdtgroup_default ;
2017-07-25 14:14:25 -07:00
DECLARE_STATIC_KEY_FALSE ( rdt_alloc_enable_key ) ;
2016-10-28 15:04:42 -07:00
2018-06-22 15:42:25 -07:00
extern struct dentry * debugfs_resctrl ;
2016-10-22 06:19:55 -07:00
enum {
RDT_RESOURCE_L3 ,
RDT_RESOURCE_L3DATA ,
RDT_RESOURCE_L3CODE ,
RDT_RESOURCE_L2 ,
2017-12-20 14:57:22 -08:00
RDT_RESOURCE_L2DATA ,
RDT_RESOURCE_L2CODE ,
2017-04-07 17:33:53 -07:00
RDT_RESOURCE_MBA ,
2016-10-22 06:19:55 -07:00
/* Must be the last */
RDT_NUM_RESOURCES ,
} ;
x86/resctrl: Split struct rdt_resource
resctrl is the defacto Linux ABI for SoC resource partitioning features.
To support it on another architecture, it needs to be abstracted from
the features provided by Intel RDT and AMD PQoS, and moved to /fs/.
struct rdt_resource contains a mix of architecture private details
and properties of the filesystem interface user-space uses.
Start by splitting struct rdt_resource, into an architecture private
'hw' struct, which contains the common resctrl structure that would be
used by any architecture. The foreach helpers are most commonly used by
the filesystem code, and should return the common resctrl structure.
for_each_rdt_resource() is changed to walk the common structure in its
parent arch private structure.
Move as much of the structure as possible into the common structure
in the core code's header file. The x86 hardware accessors remain
part of the architecture private code, as do num_closid, mon_scale
and mbm_width.
mon_scale and mbm_width are used to detect overflow of the hardware
counters, and convert them from their native size to bytes. Any
cross-architecture abstraction should be in terms of bytes, making
these properties private.
The hardware's num_closid is kept in the private structure to force the
filesystem code to use a helper to access it. MPAM would return a single
value for the system, regardless of the resource. Using the helper
prevents this field from being confused with the version of num_closid
that is being exposed to user-space (added in a later patch).
After this split, filesystem code touching a 'hw' struct indicates
where an abstraction is needed.
Splitting this structure only moves types around, and should not lead
to any change in behaviour.
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Jamie Iles <jamie@nuviainc.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Tested-by: Babu Moger <babu.moger@amd.com>
Link: https://lkml.kernel.org/r/20210728170637.25610-2-james.morse@arm.com
2021-07-28 17:06:14 +00:00
static inline struct rdt_resource * resctrl_inc ( struct rdt_resource * res )
{
struct rdt_hw_resource * hw_res = resctrl_to_arch_res ( res ) ;
hw_res + + ;
return & hw_res - > r_resctrl ;
}
/*
* To return the common struct rdt_resource , which is contained in struct
* rdt_hw_resource , walk the resctrl member of struct rdt_hw_resource .
*/
2018-11-21 20:28:33 +00:00
# define for_each_rdt_resource(r) \
x86/resctrl: Split struct rdt_resource
resctrl is the defacto Linux ABI for SoC resource partitioning features.
To support it on another architecture, it needs to be abstracted from
the features provided by Intel RDT and AMD PQoS, and moved to /fs/.
struct rdt_resource contains a mix of architecture private details
and properties of the filesystem interface user-space uses.
Start by splitting struct rdt_resource, into an architecture private
'hw' struct, which contains the common resctrl structure that would be
used by any architecture. The foreach helpers are most commonly used by
the filesystem code, and should return the common resctrl structure.
for_each_rdt_resource() is changed to walk the common structure in its
parent arch private structure.
Move as much of the structure as possible into the common structure
in the core code's header file. The x86 hardware accessors remain
part of the architecture private code, as do num_closid, mon_scale
and mbm_width.
mon_scale and mbm_width are used to detect overflow of the hardware
counters, and convert them from their native size to bytes. Any
cross-architecture abstraction should be in terms of bytes, making
these properties private.
The hardware's num_closid is kept in the private structure to force the
filesystem code to use a helper to access it. MPAM would return a single
value for the system, regardless of the resource. Using the helper
prevents this field from being confused with the version of num_closid
that is being exposed to user-space (added in a later patch).
After this split, filesystem code touching a 'hw' struct indicates
where an abstraction is needed.
Splitting this structure only moves types around, and should not lead
to any change in behaviour.
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Jamie Iles <jamie@nuviainc.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Tested-by: Babu Moger <babu.moger@amd.com>
Link: https://lkml.kernel.org/r/20210728170637.25610-2-james.morse@arm.com
2021-07-28 17:06:14 +00:00
for ( r = & rdt_resources_all [ 0 ] . r_resctrl ; \
r < = & rdt_resources_all [ RDT_NUM_RESOURCES - 1 ] . r_resctrl ; \
r = resctrl_inc ( r ) )
2018-11-21 20:28:33 +00:00
2017-07-25 14:14:44 -07:00
# define for_each_capable_rdt_resource(r) \
x86/resctrl: Split struct rdt_resource
resctrl is the defacto Linux ABI for SoC resource partitioning features.
To support it on another architecture, it needs to be abstracted from
the features provided by Intel RDT and AMD PQoS, and moved to /fs/.
struct rdt_resource contains a mix of architecture private details
and properties of the filesystem interface user-space uses.
Start by splitting struct rdt_resource, into an architecture private
'hw' struct, which contains the common resctrl structure that would be
used by any architecture. The foreach helpers are most commonly used by
the filesystem code, and should return the common resctrl structure.
for_each_rdt_resource() is changed to walk the common structure in its
parent arch private structure.
Move as much of the structure as possible into the common structure
in the core code's header file. The x86 hardware accessors remain
part of the architecture private code, as do num_closid, mon_scale
and mbm_width.
mon_scale and mbm_width are used to detect overflow of the hardware
counters, and convert them from their native size to bytes. Any
cross-architecture abstraction should be in terms of bytes, making
these properties private.
The hardware's num_closid is kept in the private structure to force the
filesystem code to use a helper to access it. MPAM would return a single
value for the system, regardless of the resource. Using the helper
prevents this field from being confused with the version of num_closid
that is being exposed to user-space (added in a later patch).
After this split, filesystem code touching a 'hw' struct indicates
where an abstraction is needed.
Splitting this structure only moves types around, and should not lead
to any change in behaviour.
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Jamie Iles <jamie@nuviainc.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Tested-by: Babu Moger <babu.moger@amd.com>
Link: https://lkml.kernel.org/r/20210728170637.25610-2-james.morse@arm.com
2021-07-28 17:06:14 +00:00
for_each_rdt_resource ( r ) \
2017-07-25 14:14:44 -07:00
if ( r - > alloc_capable | | r - > mon_capable )
2017-07-25 14:14:25 -07:00
# define for_each_alloc_capable_rdt_resource(r) \
x86/resctrl: Split struct rdt_resource
resctrl is the defacto Linux ABI for SoC resource partitioning features.
To support it on another architecture, it needs to be abstracted from
the features provided by Intel RDT and AMD PQoS, and moved to /fs/.
struct rdt_resource contains a mix of architecture private details
and properties of the filesystem interface user-space uses.
Start by splitting struct rdt_resource, into an architecture private
'hw' struct, which contains the common resctrl structure that would be
used by any architecture. The foreach helpers are most commonly used by
the filesystem code, and should return the common resctrl structure.
for_each_rdt_resource() is changed to walk the common structure in its
parent arch private structure.
Move as much of the structure as possible into the common structure
in the core code's header file. The x86 hardware accessors remain
part of the architecture private code, as do num_closid, mon_scale
and mbm_width.
mon_scale and mbm_width are used to detect overflow of the hardware
counters, and convert them from their native size to bytes. Any
cross-architecture abstraction should be in terms of bytes, making
these properties private.
The hardware's num_closid is kept in the private structure to force the
filesystem code to use a helper to access it. MPAM would return a single
value for the system, regardless of the resource. Using the helper
prevents this field from being confused with the version of num_closid
that is being exposed to user-space (added in a later patch).
After this split, filesystem code touching a 'hw' struct indicates
where an abstraction is needed.
Splitting this structure only moves types around, and should not lead
to any change in behaviour.
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Jamie Iles <jamie@nuviainc.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Tested-by: Babu Moger <babu.moger@amd.com>
Link: https://lkml.kernel.org/r/20210728170637.25610-2-james.morse@arm.com
2021-07-28 17:06:14 +00:00
for_each_rdt_resource ( r ) \
2017-07-25 14:14:25 -07:00
if ( r - > alloc_capable )
2016-10-22 06:19:55 -07:00
2017-07-25 14:14:27 -07:00
# define for_each_mon_capable_rdt_resource(r) \
x86/resctrl: Split struct rdt_resource
resctrl is the defacto Linux ABI for SoC resource partitioning features.
To support it on another architecture, it needs to be abstracted from
the features provided by Intel RDT and AMD PQoS, and moved to /fs/.
struct rdt_resource contains a mix of architecture private details
and properties of the filesystem interface user-space uses.
Start by splitting struct rdt_resource, into an architecture private
'hw' struct, which contains the common resctrl structure that would be
used by any architecture. The foreach helpers are most commonly used by
the filesystem code, and should return the common resctrl structure.
for_each_rdt_resource() is changed to walk the common structure in its
parent arch private structure.
Move as much of the structure as possible into the common structure
in the core code's header file. The x86 hardware accessors remain
part of the architecture private code, as do num_closid, mon_scale
and mbm_width.
mon_scale and mbm_width are used to detect overflow of the hardware
counters, and convert them from their native size to bytes. Any
cross-architecture abstraction should be in terms of bytes, making
these properties private.
The hardware's num_closid is kept in the private structure to force the
filesystem code to use a helper to access it. MPAM would return a single
value for the system, regardless of the resource. Using the helper
prevents this field from being confused with the version of num_closid
that is being exposed to user-space (added in a later patch).
After this split, filesystem code touching a 'hw' struct indicates
where an abstraction is needed.
Splitting this structure only moves types around, and should not lead
to any change in behaviour.
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Jamie Iles <jamie@nuviainc.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Tested-by: Babu Moger <babu.moger@amd.com>
Link: https://lkml.kernel.org/r/20210728170637.25610-2-james.morse@arm.com
2021-07-28 17:06:14 +00:00
for_each_rdt_resource ( r ) \
2017-07-25 14:14:27 -07:00
if ( r - > mon_capable )
2017-07-25 14:14:25 -07:00
# define for_each_alloc_enabled_rdt_resource(r) \
x86/resctrl: Split struct rdt_resource
resctrl is the defacto Linux ABI for SoC resource partitioning features.
To support it on another architecture, it needs to be abstracted from
the features provided by Intel RDT and AMD PQoS, and moved to /fs/.
struct rdt_resource contains a mix of architecture private details
and properties of the filesystem interface user-space uses.
Start by splitting struct rdt_resource, into an architecture private
'hw' struct, which contains the common resctrl structure that would be
used by any architecture. The foreach helpers are most commonly used by
the filesystem code, and should return the common resctrl structure.
for_each_rdt_resource() is changed to walk the common structure in its
parent arch private structure.
Move as much of the structure as possible into the common structure
in the core code's header file. The x86 hardware accessors remain
part of the architecture private code, as do num_closid, mon_scale
and mbm_width.
mon_scale and mbm_width are used to detect overflow of the hardware
counters, and convert them from their native size to bytes. Any
cross-architecture abstraction should be in terms of bytes, making
these properties private.
The hardware's num_closid is kept in the private structure to force the
filesystem code to use a helper to access it. MPAM would return a single
value for the system, regardless of the resource. Using the helper
prevents this field from being confused with the version of num_closid
that is being exposed to user-space (added in a later patch).
After this split, filesystem code touching a 'hw' struct indicates
where an abstraction is needed.
Splitting this structure only moves types around, and should not lead
to any change in behaviour.
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Jamie Iles <jamie@nuviainc.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Tested-by: Babu Moger <babu.moger@amd.com>
Link: https://lkml.kernel.org/r/20210728170637.25610-2-james.morse@arm.com
2021-07-28 17:06:14 +00:00
for_each_rdt_resource ( r ) \
2017-07-25 14:14:25 -07:00
if ( r - > alloc_enabled )
2016-10-28 15:04:41 -07:00
2017-07-25 14:14:30 -07:00
# define for_each_mon_enabled_rdt_resource(r) \
x86/resctrl: Split struct rdt_resource
resctrl is the defacto Linux ABI for SoC resource partitioning features.
To support it on another architecture, it needs to be abstracted from
the features provided by Intel RDT and AMD PQoS, and moved to /fs/.
struct rdt_resource contains a mix of architecture private details
and properties of the filesystem interface user-space uses.
Start by splitting struct rdt_resource, into an architecture private
'hw' struct, which contains the common resctrl structure that would be
used by any architecture. The foreach helpers are most commonly used by
the filesystem code, and should return the common resctrl structure.
for_each_rdt_resource() is changed to walk the common structure in its
parent arch private structure.
Move as much of the structure as possible into the common structure
in the core code's header file. The x86 hardware accessors remain
part of the architecture private code, as do num_closid, mon_scale
and mbm_width.
mon_scale and mbm_width are used to detect overflow of the hardware
counters, and convert them from their native size to bytes. Any
cross-architecture abstraction should be in terms of bytes, making
these properties private.
The hardware's num_closid is kept in the private structure to force the
filesystem code to use a helper to access it. MPAM would return a single
value for the system, regardless of the resource. Using the helper
prevents this field from being confused with the version of num_closid
that is being exposed to user-space (added in a later patch).
After this split, filesystem code touching a 'hw' struct indicates
where an abstraction is needed.
Splitting this structure only moves types around, and should not lead
to any change in behaviour.
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Jamie Iles <jamie@nuviainc.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Tested-by: Babu Moger <babu.moger@amd.com>
Link: https://lkml.kernel.org/r/20210728170637.25610-2-james.morse@arm.com
2021-07-28 17:06:14 +00:00
for_each_rdt_resource ( r ) \
2017-07-25 14:14:30 -07:00
if ( r - > mon_enabled )
2016-10-22 06:19:55 -07:00
/* CPUID.(EAX=10H, ECX=ResID=1).EAX */
union cpuid_0x10_1_eax {
struct {
unsigned int cbm_len : 5 ;
} split ;
unsigned int full ;
} ;
2017-04-07 17:33:52 -07:00
/* CPUID.(EAX=10H, ECX=ResID=3).EAX */
union cpuid_0x10_3_eax {
struct {
unsigned int max_delay : 12 ;
} split ;
unsigned int full ;
} ;
2017-04-07 17:33:51 -07:00
/* CPUID.(EAX=10H, ECX=ResID).EDX */
union cpuid_0x10_x_edx {
2016-10-22 06:19:55 -07:00
struct {
unsigned int cos_max : 16 ;
} split ;
unsigned int full ;
} ;
2016-10-28 15:04:41 -07:00
2017-09-25 16:39:33 -07:00
void rdt_last_cmd_clear ( void ) ;
void rdt_last_cmd_puts ( const char * s ) ;
2020-12-21 08:00:09 -08:00
__printf ( 1 , 2 )
2017-09-25 16:39:33 -07:00
void rdt_last_cmd_printf ( const char * fmt , . . . ) ;
2017-04-07 17:33:51 -07:00
void rdt_ctrl_update ( void * arg ) ;
2016-10-28 15:04:44 -07:00
struct rdtgroup * rdtgroup_kn_lock_live ( struct kernfs_node * kn ) ;
void rdtgroup_kn_unlock ( struct kernfs_node * kn ) ;
2018-06-22 15:42:11 -07:00
int rdtgroup_kn_mode_restrict ( struct rdtgroup * r , const char * name ) ;
2018-06-30 22:17:32 -07:00
int rdtgroup_kn_mode_restore ( struct rdtgroup * r , const char * name ,
umode_t mask ) ;
2017-07-25 14:14:38 -07:00
struct rdt_domain * rdt_find_domain ( struct rdt_resource * r , int id ,
struct list_head * * pos ) ;
2016-10-28 15:04:47 -07:00
ssize_t rdtgroup_schemata_write ( struct kernfs_open_file * of ,
char * buf , size_t nbytes , loff_t off ) ;
int rdtgroup_schemata_show ( struct kernfs_open_file * of ,
struct seq_file * s , void * v ) ;
2018-06-22 15:42:04 -07:00
bool rdtgroup_cbm_overlaps ( struct rdt_resource * r , struct rdt_domain * d ,
2018-10-04 14:05:23 -07:00
unsigned long cbm , int closid , bool exclusive ) ;
2018-06-22 15:42:06 -07:00
unsigned int rdtgroup_cbm_to_size ( struct rdt_resource * r , struct rdt_domain * d ,
2018-10-04 14:05:23 -07:00
unsigned long cbm ) ;
2018-06-22 15:41:55 -07:00
enum rdtgrp_mode rdtgroup_mode_by_closid ( int closid ) ;
2018-06-22 15:42:10 -07:00
int rdtgroup_tasks_assigned ( struct rdtgroup * r ) ;
2018-06-22 15:42:16 -07:00
int rdtgroup_locksetup_enter ( struct rdtgroup * rdtgrp ) ;
int rdtgroup_locksetup_exit ( struct rdtgroup * rdtgrp ) ;
2018-10-04 14:05:23 -07:00
bool rdtgroup_cbm_overlaps_pseudo_locked ( struct rdt_domain * d , unsigned long cbm ) ;
2018-06-22 15:42:19 -07:00
bool rdtgroup_pseudo_locked_in_hierarchy ( struct rdt_domain * d ) ;
2018-06-22 15:42:27 -07:00
int rdt_pseudo_lock_init ( void ) ;
void rdt_pseudo_lock_release ( void ) ;
2018-06-22 15:42:21 -07:00
int rdtgroup_pseudo_lock_create ( struct rdtgroup * rdtgrp ) ;
void rdtgroup_pseudo_lock_remove ( struct rdtgroup * rdtgrp ) ;
2017-07-25 14:14:28 -07:00
struct rdt_domain * get_domain_from_cpu ( int cpu , struct rdt_resource * r ) ;
2018-06-22 15:41:58 -07:00
int update_domains ( struct rdt_resource * r , int closid ) ;
2018-09-15 14:58:21 -07:00
int closids_supported ( void ) ;
2018-06-22 15:41:58 -07:00
void closid_free ( int closid ) ;
2017-07-25 14:14:32 -07:00
int alloc_rmid ( void ) ;
void free_rmid ( u32 rmid ) ;
2017-07-25 14:14:27 -07:00
int rdt_get_mon_l3_config ( struct rdt_resource * r ) ;
2017-07-25 14:14:38 -07:00
void mon_event_count ( void * info ) ;
int rdtgroup_mondata_show ( struct seq_file * m , void * arg ) ;
2017-07-25 14:14:44 -07:00
void rmdir_mondata_subdir_allrdtgrp ( struct rdt_resource * r ,
unsigned int dom_id ) ;
void mkdir_mondata_subdir_allrdtgrp ( struct rdt_resource * r ,
struct rdt_domain * d ) ;
2020-05-05 15:36:16 -07:00
void mon_event_read ( struct rmid_read * rr , struct rdt_resource * r ,
struct rdt_domain * d , struct rdtgroup * rdtgrp ,
int evtid , int first ) ;
2017-08-15 18:00:43 -07:00
void mbm_setup_overflow_handler ( struct rdt_domain * dom ,
unsigned long delay_ms ) ;
2017-07-25 14:14:47 -07:00
void mbm_handle_overflow ( struct work_struct * work ) ;
2020-10-14 00:49:27 +00:00
void __init intel_rdt_mbm_apply_quirk ( void ) ;
2018-04-20 15:36:17 -07:00
bool is_mba_sc ( struct rdt_resource * r ) ;
2018-04-20 15:36:18 -07:00
void setup_default_ctrlval ( struct rdt_resource * r , u32 * dc , u32 * dm ) ;
2018-04-20 15:36:21 -07:00
u32 delay_bw_map ( unsigned long bw , struct rdt_resource * r ) ;
2017-08-15 18:00:43 -07:00
void cqm_setup_limbo_handler ( struct rdt_domain * dom , unsigned long delay_ms ) ;
void cqm_handle_limbo ( struct work_struct * work ) ;
bool has_busy_rmid ( struct rdt_resource * r , struct rdt_domain * d ) ;
void __check_limbo ( struct rdt_domain * d , bool force_free ) ;
2020-02-21 16:21:05 +00:00
void rdt_domain_reconfigure_cdp ( struct rdt_resource * r ) ;
2020-08-24 12:11:21 -07:00
void __init thread_throttle_mode_init ( void ) ;
2016-10-28 15:04:48 -07:00
2018-11-21 20:28:25 +00:00
# endif /* _ASM_X86_RESCTRL_INTERNAL_H */