+23
−0
Loading
The bulk of the MPAM driver lives outside the arch code because it largely manages MMIO devices that generate interrupts. The driver needs a Kconfig symbol to enable it. As MPAM is only found on arm64 platforms, the arm64 tree is the most natural home for the Kconfig option. This Kconfig option will later be used by the arch code to enable or disable the MPAM context-switch code, and to register properties of CPUs with the MPAM driver. Signed-off-by:James Morse <james.morse@arm.com> Reviewed-by:
Jonathan Cameron <jonathan.cameron@huawei.com> Reviewed-by:
Ben Horgan <ben.horgan@arm.com> Reviewed-by:
Fenghua Yu <fenghuay@nvidia.com> Reviewed-by:
Gavin Shan <gshan@redhat.com> Reviewed-by:
Shaopeng Tan <tan.shaopeng@jp.fujitsu.com> Tested-by:
Fenghua Yu <fenghuay@nvidia.com> Tested-by:
Shaopeng Tan <tan.shaopeng@jp.fujitsu.com> Tested-by:
Peter Newman <peternewman@google.com> Tested-by:
Carl Worth <carl@os.amperecomputing.com> Tested-by:
Gavin Shan <gshan@redhat.com> Tested-by:
Zeng Heng <zengheng4@huawei.com> Tested-by:
Hanjun Guo <guohanjun@huawei.com> CC: Dave Martin <dave.martin@arm.com> Signed-off-by:
Ben Horgan <ben.horgan@arm.com> Signed-off-by:
Catalin Marinas <catalin.marinas@arm.com>