diff options
| author | James Morse <[email protected]> | 2024-02-13 18:44:21 +0000 |
|---|---|---|
| committer | Borislav Petkov (AMD) <[email protected]> | 2024-02-16 19:18:31 +0100 |
| commit | c4c0376eefe185b790d89ca8016b7f837ebf25da (patch) | |
| tree | 2b938bf606cdf1725fadb5d3727512c22155fb57 /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | 6791e0ea30711b937d5cb6e2b17f59a2a2af5386 (diff) | |
x86/resctrl: Allow RMID allocation to be scoped by CLOSID
MPAMs RMID values are not unique unless the CLOSID is considered as well.
alloc_rmid() expects the RMID to be an independent number.
Pass the CLOSID in to alloc_rmid(). Use this to compare indexes when
allocating. If the CLOSID is not relevant to the index, this ends up comparing
the free RMID with itself, and the first free entry will be used. With MPAM the
CLOSID is included in the index, so this becomes a walk of the free RMID
entries, until one that matches the supplied CLOSID is found.
Signed-off-by: James Morse <[email protected]>
Signed-off-by: Borislav Petkov (AMD) <[email protected]>
Reviewed-by: Shaopeng Tan <[email protected]>
Reviewed-by: Reinette Chatre <[email protected]>
Reviewed-by: Babu Moger <[email protected]>
Tested-by: Shaopeng Tan <[email protected]>
Tested-by: Peter Newman <[email protected]>
Tested-by: Babu Moger <[email protected]>
Tested-by: Carl Worth <[email protected]> # arm64
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Borislav Petkov (AMD) <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions