From: Peter Zijlstra <peterz@infradead.org>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
rjw@rjwysocki.net, x86@kernel.org, bp@alien8.de,
linux-kernel@vger.kernel.org, jacob.jun.pan@linux.intel.com,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v4 1/2] perf/x86/intel/rapl: support Skylake RAPL domains
Date: Wed, 20 Apr 2016 17:43:20 +0200 [thread overview]
Message-ID: <20160420154320.GE3408@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1460930581-29748-2-git-send-email-srinivas.pandruvada@linux.intel.com>
On Sun, Apr 17, 2016 at 03:03:00PM -0700, Srinivas Pandruvada wrote:
> @@ -729,6 +771,11 @@ static int __init rapl_pmu_init(void)
> rapl_cntr_mask = RAPL_IDX_SRV;
> rapl_pmu_events_group.attrs = rapl_events_srv_attr;
> break;
> + case 78: /* Skylake client */
> + case 94: /* Skylake H/S */
> + rapl_cntr_mask = RAPL_IDX_SKL_CLN;
> + rapl_pmu_events_group.attrs = rapl_events_skl_attr;
> + break;
> case 87: /* Knights Landing */
> apply_quirk = true;
> rapl_cntr_mask = RAPL_IDX_KNL;
Please post this against tip/perf/core, all this code got munged in
patch:
4b6e2571bf00 ("x86/perf/intel/rapl: Make the Intel RAPL PMU driver modular")
Also; what about 85 (skl-server)?
next prev parent reply other threads:[~2016-04-20 15:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 22:02 [PATCH v4 0/2] Skylake PSys support Srinivas Pandruvada
2016-04-17 22:03 ` [PATCH v4 1/2] perf/x86/intel/rapl: support Skylake RAPL domains Srinivas Pandruvada
2016-04-20 15:43 ` Peter Zijlstra [this message]
2016-04-20 15:54 ` Srinivas Pandruvada
2016-04-23 12:55 ` [tip:perf/core] perf/x86/intel/rapl: Support " tip-bot for Srinivas Pandruvada
2016-04-17 22:03 ` [PATCH v4 2/2] powercap: intel_rapl: PSys support Srinivas Pandruvada
2016-04-28 10:26 ` [tip:perf/core] powercap, perf/x86/intel/rapl: Add " tip-bot for Srinivas Pandruvada
2016-04-20 13:59 ` [PATCH v4 0/2] Skylake " Peter Zijlstra
2016-04-20 18:28 ` Srinivas Pandruvada
2016-04-20 20:21 ` Rafael J. Wysocki
2016-04-21 13:10 ` Peter Zijlstra
2016-04-21 14:48 ` Srinivas Pandruvada
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=20160420154320.GE3408@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--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 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.