From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <borislav.petkov@amd.com>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
Ingo Molnar <mingo@elte.hu>, x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] x86: cpu/proc.c adding extended_cpuid_level for /proc/cpuinfo
Date: Tue, 12 May 2009 11:47:32 -0700 [thread overview]
Message-ID: <4A09C444.9070809@zytor.com> (raw)
In-Reply-To: <20090512181358.GC19143@aftab>
Borislav Petkov wrote:
>
>> It hardly "completes" /proc/cpuinfo; especially if you consider that
>> there are at least three additional ranges in wide use (two used by a
>> single vendor only, and the third by virtualization software.)
>
> I think both vendors use the two ranges :-o).
>
No, I'm taking about the 0x8086xxxx and 0xC000xxxx used by two other
vendors (neither of which you and I work for, and at least one of which
is defunct.)
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-05-12 18:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 7:14 [PATCH -tip] x86: cpu/proc.c adding extended_cpuid_level for /proc/cpuinfo Jaswinder Singh Rajput
2009-05-12 13:39 ` Borislav Petkov
2009-05-12 13:49 ` Jaswinder Singh Rajput
2009-05-12 14:10 ` Borislav Petkov
2009-05-12 16:40 ` H. Peter Anvin
2009-05-12 18:13 ` Borislav Petkov
2009-05-12 18:47 ` H. Peter Anvin [this message]
2009-05-12 19:49 ` Borislav Petkov
2009-06-05 19:20 ` Jaswinder Singh Rajput
2009-05-13 6:21 ` Andrew Morton
2009-05-13 8:03 ` Andi Kleen
2009-06-05 18:38 ` Jaswinder Singh Rajput
2009-06-05 20:55 ` H. Peter Anvin
2009-06-06 4:23 ` Jaswinder Singh Rajput
2009-06-10 16:40 ` Jaswinder Singh Rajput
2009-06-10 17:14 ` H. Peter Anvin
2009-06-10 17:42 ` Borislav Petkov
2009-06-10 17:48 ` H. Peter Anvin
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=4A09C444.9070809@zytor.com \
--to=hpa@zytor.com \
--cc=borislav.petkov@amd.com \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox