linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Borislav Petkov <bp@alien8.de>,
	"Luck, Tony" <tony.luck@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andy Lutomirski <luto@amacapital.net>,
	Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Brian Gerst <brgerst@gmail.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -v2] x86: Add an archinfo dumper module
Date: Tue, 9 Feb 2016 13:23:00 +0100	[thread overview]
Message-ID: <20160209122300.GA4878@gmail.com> (raw)
In-Reply-To: <56B7DAC2.2030506@zytor.com>


* H. Peter Anvin <hpa@zytor.com> wrote:

> On 02/04/16 07:22, Borislav Petkov wrote:
> > Here's v2 with the stuff we talked about, implemented. I've added
> > 'control_regs' file too so that you can do:
> > 
> > $ cat /sys/kernel/debug/x86/archinfo/control_regs
> > CR4: [-|-|SMEP|OSXSAVE|-|-|-|-|OSXMMEXCPT|OSFXSR|-|PGE|MCE|PAE|PSE|-|-|-|-]: 0x1406f0
> > 
> > for example. Yeah, only CR4 right now.
> > 
> > Off the top of my head, we would need "msrs" which dumps EFER and a
> > bunch of other interesting MSRs along with the names of the set bits.
> 
> Is there a reason why all this parsing has to be done in kernel space?

Ease of use I suspect, no need to locate some separate utility. Also, no need to 
define an ABI for the information displayed - which keeps things simpler. Since 
it's a kernel module there's no real bloat argument.

Thanks,

	Ingo

  parent reply	other threads:[~2016-02-09 12:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 11:56 [RFC] Dump interesting arch/platform info Borislav Petkov
2016-02-01 23:29 ` Luck, Tony
2016-02-02  9:41   ` Borislav Petkov
2016-02-03 10:48     ` Ingo Molnar
2016-02-03 11:00       ` Borislav Petkov
2016-02-04 15:22         ` [PATCH -v2] x86: Add an archinfo dumper module Borislav Petkov
2016-02-04 19:07           ` Luck, Tony
2016-02-07 10:51             ` Borislav Petkov
2016-02-09 19:17               ` Luck, Tony
2016-02-09 19:46                 ` Borislav Petkov
2016-02-05 19:51           ` Luck, Tony
2016-02-05 22:24             ` Luck, Tony
2016-02-08  0:01           ` H. Peter Anvin
2016-02-08  7:50             ` Boris Petkov
2016-02-09 12:23             ` Ingo Molnar [this message]
2016-02-09 14:01               ` Borislav Petkov

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=20160209122300.GA4878@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=brgerst@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).