Commit faf9a4c3 authored by Wang ShaoBo's avatar Wang ShaoBo Committed by Zheng Zengkai
Browse files

arm64/mpam: Pick MPAM resources and events for resctrl_res exported



hulk inclusion
category: feature
feature: ARM MPAM support
bugzilla: 48265
CVE: NA

--------------------------------

Pick available classes and exported as well-known caches and MBA():

1) System with MPAM support may have a variety of control types at any
   point of their system layout. We can only expose certain types of
   control, and only if they exist at particular locations.

   Start with the well-know caches. These have to be depth 2 or 3
   and support MPAM's cache portion bitmap controls, with a number
   of portions fewer that resctrl's limit.

2) Picking which MPAM component we can expose via resctrl as MBA
   (Memory Bandwidth Allocation) is tricky. The ABI is a percentage of
   available bandwidth.

   We can either do this with the memory bandwidth portion bitmaps, or
   the memory bandwidth maximum control. If both are implemented we
   prefer the bitmap.

   We require and candidate for this resource type to support bandwidth
   monitoring too.

   For 'MBA's position in the toplogy, we want it to be at, or after,
   the last level cache that is being exposed via resctrl. If there
   are multiple candidates, we prefer the one closer to the outermost
   exposed cache.

Signed-off-by: default avatarJames Morse <james.morse@arm.com>
Link: http://www.linux-arm.org/git?p=linux-jm.git;a=patch;h=b6870246e25f8f6f9c7b275f0aaa50fc772094a6
Link: http://www.linux-arm.org/git?p=linux-jm.git;a=patch;h=676d9aee8c2b27a17dd9cbebe5c9ecdd63c6281f


Signed-off-by: default avatarWang ShaoBo <bobo.shaobowang@huawei.com>
Reviewed-by: default avatarXiongfeng Wang <wangxiongfeng2@huawei.com>
Reviewed-by: default avatarCheng Jian <cj.chengjian@huawei.com>
Signed-off-by: default avatarYang Yingliang <yangyingliang@huawei.com>
Signed-off-by: default avatarZheng Zengkai <zhengzengkai@huawei.com>
parent 8a6445f7
Loading
Loading
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please to comment