diff options
author | Oliver Upton <oliver.upton@linux.dev> | 2023-02-07 02:52:29 +0300 |
---|---|---|
committer | Oliver Upton <oliver.upton@linux.dev> | 2023-02-07 16:56:18 +0300 |
commit | 5f623a598d128dacadf95c9d14f7c8b1313a3dc4 (patch) | |
tree | 83304ccc4bedf9b3379247a3164df00631b7aad2 /tools/perf/scripts/python/stackcollapse.py | |
parent | 7af0c2534f4c57b16e92dfca8c5f40fa90fbb3f3 (diff) | |
download | linux-5f623a598d128dacadf95c9d14f7c8b1313a3dc4.tar.xz |
KVM: arm64: Mark some VM-scoped allocations as __GFP_ACCOUNT
Generally speaking, any memory allocations that can be associated with a
particular VM should be charged to the cgroup of its process.
Nonetheless, there are a couple spots in KVM/arm64 that aren't currently
accounted:
- the ccsidr array containing the virtualized cache hierarchy
- the cpumask of supported cpus, for use of the vPMU on heterogeneous
systems
Go ahead and set __GFP_ACCOUNT for these allocations.
Reviewed-by: Marc Zyngier <maz@kernel.org>
Reviewed-by: Akihiko Odaki <akihiko.odaki@daynix.com>
Reviewed-by: Gavin Shan <gshan@redhat.com>
Link: https://lore.kernel.org/r/20230206235229.4174711-1-oliver.upton@linux.dev
Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions