From: Thomas Gleixner <tglx@linutronix.de>
To: Kan Liang <kan.liang@intel.com>
Cc: peterz@infradead.org, ak@linux.intel.com, eranian@google.com,
mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 2/2] x86/perf/intel/uncore: Make Intel rapl modular
Date: Sun, 20 Mar 2016 13:04:05 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1603201301330.3978@nanos> (raw)
In-Reply-To: <1458372050-2420-2-git-send-email-kan.liang@intel.com>
On Sat, 19 Mar 2016, kan.liang@intel.com wrote:
>
> +static struct notifier_block rapl_cpu_nb = {
> + .notifier_call = rapl_cpu_notifier,
Hmm. Missed that in the first round. That lacks
.priority = CPU_PRI_PERF + 1,
because the driver needs to migrate its stuff away before the core code gets
notified about the cpu going down.
Thanks,
tglx
next prev parent reply other threads:[~2016-03-20 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 7:20 [PATCH V3 1/2] x86/perf/intel/uncore: Make Intel uncore modular kan.liang
2016-03-19 7:20 ` [PATCH V3 2/2] x86/perf/intel/uncore: Make Intel rapl modular kan.liang
2016-03-20 12:04 ` Thomas Gleixner [this message]
2016-03-31 9:20 ` [tip:perf/core] x86/perf/intel/rapl: Make the Intel RAPL PMU driver modular tip-bot for Kan Liang
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=alpine.DEB.2.11.1603201301330.3978@nanos \
--to=tglx@linutronix.de \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/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
all inboxes | Powered by JetHome®