summaryrefslogtreecommitdiff
path: root/tools
diff options
context:
space:
mode:
authorZhou Chengming <zhouchengming1@huawei.com>2017-01-16 11:21:11 +0800
committerThomas Gleixner <tglx@linutronix.de>2017-01-17 11:08:36 +0100
commit4e71de7986386d5fd3765458f27d612931f27f5e (patch)
treeb5ca21b15c61a7645057a489271c0daf546e90a1 /tools
parent49def1853334396f948dcb4cedb9347abb318df5 (diff)
downloadlinux-exynos-4e71de7986386d5fd3765458f27d612931f27f5e.tar.gz
linux-exynos-4e71de7986386d5fd3765458f27d612931f27f5e.tar.bz2
linux-exynos-4e71de7986386d5fd3765458f27d612931f27f5e.zip
perf/x86/intel: Handle exclusive threadid correctly on CPU hotplug
The CPU hotplug function intel_pmu_cpu_starting() sets cpu_hw_events.excl_thread_id unconditionally to 1 when the shared exclusive counters data structure is already availabe for the sibling thread. This works during the boot process because the first sibling gets threadid 0 assigned and the second sibling which shares the data structure gets 1. But when the first thread of the core is offlined and onlined again it shares the data structure with the second thread and gets exclusive thread id 1 assigned as well. Prevent this by checking the threadid of the already online thread. [ tglx: Rewrote changelog ] Signed-off-by: Zhou Chengming <zhouchengming1@huawei.com> Cc: NuoHan Qiao <qiaonuohan@huawei.com> Cc: ak@linux.intel.com Cc: peterz@infradead.org Cc: kan.liang@intel.com Cc: dave.hansen@linux.intel.com Cc: eranian@google.com Cc: qiaonuohan@huawei.com Cc: davidcc@google.com Cc: guohanjun@huawei.com Link: http://lkml.kernel.org/r/1484536871-3131-1-git-send-email-zhouchengming1@huawei.com Signed-off-by: Thomas Gleixner <tglx@linutronix.de> --- --- arch/x86/events/intel/core.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions