All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Brown, Len" <len.brown@intel.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
	Prarit Bhargava <prarit@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, X86 ML <x86@kernel.org>,
	"Chandramouli,
	Dasaratharaman"  <dasaratharaman.chandramouli@intel.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Borislav Petkov <bp@alien8.de>, Andy Lutomirski <luto@kernel.org>,
	Denys Vlasenko <dvlasenk@redhat.com>,
	Brian Gerst <brgerst@gmail.com>,
	Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: Re: [PATCH] x86, msr: Allow read access to /dev/cpu/X/msr
Date: Fri, 3 Jul 2015 09:42:08 +0200	[thread overview]
Message-ID: <20150703074208.GA21024@gmail.com> (raw)
In-Reply-To: <1A7043D5F58CCB44A599DFD55ED4C948468A477B@fmsmsx115.amr.corp.intel.com>


* Brown, Len <len.brown@intel.com> wrote:

> > This driver only knows how to handle counters, though.  I'm not sure
> > whether all of the MSRs that turbostat needs are counters.
> 
> turbostat --debug
> dumps a lot of configuration MSRs that are not counters.
>
> "--debug" is not an obscure option, it is the only way that the turbostat is 
> used by advanced users, since it shows not just how fast a system is running, 
> but explains why.

I see no problems there: the main property for perf is read-only access - so it 
will work fine with non-counting MSRs as well.

Really, for system-wide statistics perf is the way to go, it has rich kernel side 
and user side support. We already kind of expose MSRs via the RAPL energy PMU 
bits. All we need is to extend it to an enumerated list of MSRs.

Thanks,

	Ingo

      parent reply	other threads:[~2015-07-03  7:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 17:52 [PATCH] x86, msr: Allow read access to /dev/cpu/X/msr Prarit Bhargava
2015-06-26 18:45 ` H. Peter Anvin
2015-06-26 19:23 ` Brian Gerst
2015-06-26 21:26   ` Prarit Bhargava
2015-06-28 15:13     ` Henrique de Moraes Holschuh
2015-06-27  8:33 ` Ingo Molnar
2015-06-27  8:39   ` Ingo Molnar
2015-06-27 15:52     ` Andy Lutomirski
2015-06-28 14:34       ` Prarit Bhargava
2015-06-28 15:10         ` Henrique de Moraes Holschuh
2015-06-29  6:42           ` Ingo Molnar
2015-06-29 10:58           ` Matt Fleming
2015-06-29 19:51         ` H. Peter Anvin
2015-06-30 12:20           ` Prarit Bhargava
2015-06-30 12:44             ` Peter Zijlstra
2015-06-30 12:57               ` Ingo Molnar
2015-06-30 13:23               ` Prarit Bhargava
2015-07-01 16:38       ` Brown, Len
2015-07-01 17:33         ` Andy Lutomirski
2015-07-02  9:15           ` Ingo Molnar
2015-07-02 19:22         ` H. Peter Anvin
2015-07-02 19:26           ` Andy Lutomirski
2015-07-03  7:42         ` Ingo Molnar [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=20150703074208.GA21024@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@infradead.org \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=dasaratharaman.chandramouli@intel.com \
    --cc=dvlasenk@redhat.com \
    --cc=hpa@zytor.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=prarit@redhat.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.