All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: kan.liang@linux.intel.com
Cc: mingo@kernel.org, Linux-kernel@vger.kernel.org, ak@linux.intel.com
Subject: Re: [PATCH] perf/x86/rapl: Fix Haswell and Broadwell server RAPL event
Date: Thu, 11 Jan 2018 20:54:37 +0100	[thread overview]
Message-ID: <20180111195437.GC3397@worktop> (raw)
In-Reply-To: <1515698143-366708-1-git-send-email-kan.liang@linux.intel.com>

On Thu, Jan 11, 2018 at 11:15:43AM -0800, kan.liang@linux.intel.com wrote:
> From: Kan Liang <kan.liang@linux.intel.com>
> 
> Perf-fuzzer triggers non-existent MSR access in RAPL driver on
> Haswell-EX.
> 
> Haswell/Broadwell server and client have differnt RAPL events.
> Since 'commit 7f2236d0bf9a ("perf/x86/rapl: Use Intel family macros for
> RAPL")', it accidentally assign RAPL client events to server.

Thanks!

      reply	other threads:[~2018-01-11 19:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 19:15 [PATCH] perf/x86/rapl: Fix Haswell and Broadwell server RAPL event kan.liang
2018-01-11 19:54 ` Peter Zijlstra [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=20180111195437.GC3397@worktop \
    --to=peterz@infradead.org \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=ak@linux.intel.com \
    --cc=kan.liang@linux.intel.com \
    --cc=mingo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.