From: Borislav Petkov <bp@alien8.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
"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 15:01:33 +0100 [thread overview]
Message-ID: <20160209140133.GD4119@pd.tnic> (raw)
In-Reply-To: <20160209122300.GA4878@gmail.com>
On Tue, Feb 09, 2016 at 01:23:00PM +0100, Ingo Molnar wrote:
> Ease of use I suspect, no need to locate some separate utility.
Yeah, that is IMO the main reason which speaks against parsing in
userspace.
> 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.
... and ontop it is a debugging aid module so won't be present on
production systems.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
prev parent reply other threads:[~2016-02-09 14:01 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
2016-02-09 14:01 ` Borislav Petkov [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=20160209140133.GD4119@pd.tnic \
--to=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--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 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.