From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Micha? Miros?aw <mirq-linux@rere.qmqm.pl>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org
Subject: Re: [PATCH 3/7] mtrr: Remove use_intel()
Date: Wed, 09 Dec 2009 11:03:39 -0800 [thread overview]
Message-ID: <4B1FF48B.4020202@zytor.com> (raw)
In-Reply-To: <86802c440912091032q5fabe27ag9a699e484828a0e6@mail.gmail.com>
On 12/09/2009 10:32 AM, Yinghai Lu wrote:
> /*
> * Generic structure...
> */
> struct mtrr_ops generic_mtrr_ops = {
> .use_intel_if = 1,
> .set_all = generic_set_all,
>
> so all cpus that cpuid tell us that there is mtrr support, will all
> have use_intel() == 1
Yes, because the right thing to check isn't the CPU vendor bit but the
CPU feature bits -- all CPUs that have the MTRR feature bit are using
the "Intel interface" -- regardless of if they are made by Intel, AMD,
VIA, or Transmeta. The older AMD, Cyrix etc. interfaces use different bits.
-hpa
next prev parent reply other threads:[~2009-12-09 19:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 7:34 [PATCH 0/7] mtrr: cleanups and CONFIG_EMBEDDED usage Michał Mirosław
2009-12-09 4:51 ` [PATCH 1/7] x86/mtrr: Remove mtrr_ops[] Michał Mirosław
2009-12-09 4:57 ` [PATCH 2/7] mtrr: constify struct mtrr_ops Michał Mirosław
2009-12-09 5:00 ` [PATCH 3/7] mtrr: Remove use_intel() Michał Mirosław
2009-12-09 8:10 ` Yinghai Lu
2009-12-09 8:34 ` Michał Mirosław
2009-12-09 8:52 ` Ingo Molnar
2009-12-09 18:32 ` Yinghai Lu
2009-12-09 19:03 ` H. Peter Anvin [this message]
2009-12-09 5:04 ` [PATCH 4/7] x86/Kconfig.cpu: add CPU_SUP_AMD_32 and CPU_SUP_CENTAUR_32 Michał Mirosław
2009-12-09 5:10 ` [PATCH 5/7] mtrr: use CONFIG_CPU_SUP_* to select MTRR implementations Michał Mirosław
2009-12-09 5:17 ` [PATCH 6/7] mtrr: introduce HAVE_MTRR_VENDOR_SPECIFIC Michał Mirosław
2009-12-09 7:32 ` [PATCH 7/7] mtrr: mark mtrr_if as __read_mostly Michał Mirosław
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=4B1FF48B.4020202@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yhlu.kernel@gmail.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).