[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABPqkBRtBESMT-+FokR0+JYYL3Q=GUG-e5gZGOeHT3wOOtEaow@mail.gmail.com>
Date: Sat, 30 Nov 2013 00:25:10 +0100
From: Stephane Eranian <eranian@...gle.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Vince Weaver <vince@...ter.net>, Ingo Molnar <mingo@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
"mingo@...e.hu" <mingo@...e.hu>,
"ak@...ux.intel.com" <ak@...ux.intel.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Jiri Olsa <jolsa@...hat.com>,
"Yan, Zheng" <zheng.z.yan@...el.com>,
Maria Dimakopoulou <maria.n.dimakopoulou@...il.com>
Subject: Re: [PATCH v7 3/4] perf,x86: add Intel RAPL PMU support
Vince,
Ok, I have added PP1 now and it works fine on my HSW desktop.
What I want to know now is what is this map to on servers?
And on clients, it is always mapped to the GFX. If so, then
we can use a more specific name: power/energy-gfx/
I will send a patch soon.
Thanks.
On Fri, Nov 29, 2013 at 9:31 PM, Borislav Petkov <bp@...en8.de> wrote:
> On Fri, Nov 29, 2013 at 09:09:46PM +0100, Stephane Eranian wrote:
>> > So in theory it would be harmless to export the values even if not
>> > supported. What is the worst failure mode? That somehow a recent CPU
>> > doesn't support the MSR and we get a GPF when trying to access it?
>> >
>> Yes. I think that's what you get with DRAM on client for instance.
>
> We have rdmsr_safe for non-existent MSRs, in case touching such is the
> issue.
>
> --
> Regards/Gruss,
> Boris.
>
> Sent from a fat crate under my desk. Formatting is fine.
> --
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists