From: "H. Peter Anvin" <hpa@zytor.com>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: tglx@linutronix.de, mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: make clflush a required feature on x86_64
Date: Fri, 18 Jan 2008 00:04:54 -0500 [thread overview]
Message-ID: <47903376.9050204@zytor.com> (raw)
In-Reply-To: <20080118045921.GB974@phobos.i.cabal.ca>
Kyle McMartin wrote:
> Hopefully nobody will be stupid enough to implement a cpu without
> it. Frankly, it seems safe enough given we already require SSE2.
>
> This means the compiler can optimise away "if (!cpu_has_clflush)"
> blocks.
>
> Signed-off-by: Kyle McMartin <kyle@mcmartin.ca>
> ---
> include/asm-x86/cpufeature_64.h | 3 +++
> include/asm-x86/required-features.h | 4 +++-
> 2 files changed, 6 insertions(+), 1 deletions(-)
>
> diff --git a/include/asm-x86/cpufeature_64.h b/include/asm-x86/cpufeature_64.h
> index e18496b..ef11d27 100644
> --- a/include/asm-x86/cpufeature_64.h
> +++ b/include/asm-x86/cpufeature_64.h
> @@ -18,6 +18,9 @@
> #undef cpu_has_mp
> #define cpu_has_mp 1 /* XXX */
>
> +#undef cpu_has_clflush
> +#define cpu_has_clflush 1
> +
> #undef cpu_has_k6_mtrr
> #define cpu_has_k6_mtrr 0
Unnecessary. These overrides are only needed for the anticases (known
to be zero) or for some special hacks.
Stuff that have proper CPUID bits get these defined as constants via the
REQUIRED_MASK macros.
-hpa
next prev parent reply other threads:[~2008-01-18 5:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 4:59 [PATCH] x86: make clflush a required feature on x86_64 Kyle McMartin
2008-01-18 5:04 ` H. Peter Anvin [this message]
2008-01-18 5:25 ` [PATCH] x86_64: remove redundant cpu_has_ definitions Kyle McMartin
2008-01-18 8:07 ` Ingo Molnar
2008-01-18 5:53 ` [PATCH] x86: make clflush a required feature on x86_64 Andi Kleen
2008-01-18 6:01 ` Kyle McMartin
2008-01-18 6:27 ` H. Peter Anvin
2008-01-11 18:16 ` Pavel Machek
2008-01-18 6:54 ` Andi Kleen
2008-01-18 13:56 ` H. Peter Anvin
2008-01-18 14:18 ` Andi Kleen
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=47903376.9050204@zytor.com \
--to=hpa@zytor.com \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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