From: "Joerg Roedel" <joerg.roedel@amd.com>
To: "Andi Kleen" <ak@suse.de>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86_64: add reporting of SVM flags to /proc/cpuinfo
Date: Tue, 6 Mar 2007 13:46:52 +0100 [thread overview]
Message-ID: <20070306124652.GK30318@amd.com> (raw)
In-Reply-To: <200703051625.31449.ak@suse.de>
On Mon, Mar 05, 2007 at 04:25:31PM +0100, Andi Kleen wrote:
> On Monday 05 March 2007 15:39, Joerg Roedel wrote:
> > From: Joerg Roedel <joerg.roedel@amd.com>
> >
> > This patch adds the advanced SVM reporting to /proc/cpuinfo on the x86_64
> > architecture.
>
> Adding more fields to /proc/cpuinfo is always somewhat risky because
> there are lots of badly written parsers for it.
Can you point me to some really broken parsers of /proc/cpuinfo to test
with?
> I considered adding the SVM fields myself, but decided against it because
> it didn't seem generally useful enough.
I don't see that this is less important than the power flags in that
file. Some users might be interested to see if their processor has npt
for example by simply looking into cpuinfo.
As I said, would be interested to know more about these badly written
parsers.
Joerg
--
Joerg Roedel
Operating System Research Center
AMD Saxony LLC & Co. KG
next prev parent reply other threads:[~2007-03-06 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 14:36 [PATCH 0/2] add reporting of SVM flags to /proc/cpuinfo Joerg Roedel
2007-03-05 14:39 ` [PATCH 1/2] x86_64: " Joerg Roedel
2007-03-05 14:46 ` Michael Tokarev
2007-03-05 15:06 ` Joerg Roedel
2007-03-05 15:25 ` Andi Kleen
2007-03-05 15:58 ` [discuss] " Dave Jones
2007-03-06 12:46 ` Joerg Roedel [this message]
2007-03-05 14:42 ` [PATCH 2/2] i386: " Joerg Roedel
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=20070306124652.GK30318@amd.com \
--to=joerg.roedel@amd.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox