From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
Sebastian Siewior <bigeasy@linutronix.de>,
Yasuaki Ishimatsu <yasu.isimatu@gmail.com>
Subject: [patch 0/3] perf/x86/intel: Fix RAPL and UNCORE hotplug issues
Date: Tue, 31 Jan 2017 23:58:37 +0100 [thread overview]
Message-ID: <20170131225837.646254998@linutronix.de> (raw)
Yasuaki reported a RAPL failure vs. CPU hotplug. This is caused by the
recent rework of the package mapping code. The same issue along with other
fallouts from the hotplug conversion is present in the UNCORE code.
The following series addresses those problems.
Thanks,
tglx
---
arch/x86/events/intel/rapl.c | 60 ++++------
arch/x86/events/intel/uncore.c | 232 ++++++++++++++++-------------------------
include/linux/cpuhotplug.h | 3
3 files changed, 117 insertions(+), 178 deletions(-)
next reply other threads:[~2017-01-31 23:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 22:58 Thomas Gleixner [this message]
2017-01-31 22:58 ` [patch 1/3] perf/x86/intel/rapl: Make package handling more robust Thomas Gleixner
2017-02-01 9:43 ` [tip:perf/urgent] " tip-bot for Thomas Gleixner
2017-01-31 22:58 ` [patch 2/3] perf/x86/intel/uncore: Cleanup hotplug conversion fallout Thomas Gleixner
2017-02-01 9:43 ` [tip:perf/urgent] perf/x86/intel/uncore: Clean up " tip-bot for Thomas Gleixner
2017-01-31 22:58 ` [patch 3/3] perf/x86/intel/uncore: Make package handling more robust Thomas Gleixner
2017-02-01 9:44 ` [tip:perf/urgent] " tip-bot for Thomas Gleixner
2017-02-01 19:52 ` [patch 0/3] perf/x86/intel: Fix RAPL and UNCORE hotplug issues Yasuaki Ishimatsu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170131225837.646254998@linutronix.de \
--to=tglx@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
--cc=yasu.isimatu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox