From: Yasuaki Ishimatsu <yasu.isimatu@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Cc: x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
Sebastian Siewior <bigeasy@linutronix.de>
Subject: Re: [patch 0/3] perf/x86/intel: Fix RAPL and UNCORE hotplug issues
Date: Wed, 1 Feb 2017 14:52:55 -0500 [thread overview]
Message-ID: <8f873a83-8836-6f3b-3534-a67233e186da@gmail.com> (raw)
In-Reply-To: <20170131225837.646254998@linutronix.de>
Hi Thomas,
Thank you for posting the patch-set.
On 01/31/2017 05:58 PM, Thomas Gleixner wrote:
> 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(-)
I tested physical CPU hot-add and remove with your patch-set.
And I confirmed that the patch-set works good to me.
Tested-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Thanks,
Yasuaki Ishimatsu
>
>
prev parent reply other threads:[~2017-02-01 19:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 22:58 Thomas Gleixner
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 ` Yasuaki Ishimatsu [this message]
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=8f873a83-8836-6f3b-3534-a67233e186da@gmail.com \
--to=yasu.isimatu@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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®