From: "H. Peter Anvin" <hpa@zytor.com>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Andi Kleen <andi@firstfloor.org>,
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 01:27:06 -0500 [thread overview]
Message-ID: <479046BA.7090903@zytor.com> (raw)
In-Reply-To: <20080118060124.GC1726@phobos.i.cabal.ca>
Kyle McMartin wrote:
> On Fri, Jan 18, 2008 at 06:53:53AM +0100, Andi Kleen wrote:
>> One problem that we had in the past is that some simulators
>> only implement the absolutely minimum feature set and you
>> might have well broken one of these with this.
>
> Yeah, true. Please ignore the patch folks.
>
> cheers, Kyle
Simulators can be fixed, even if it takes time; for something like
clflush this is easier since clflush can be implemented as a simple noop
for most of them.
I just verified that Bochs 2.3.0 lacks this CPUID bit whereas the
current version, 2.3.6, enables CLFLUSH iff SSE2 is enabled. Qemu 0.9.0
has CLFLUSH. Andi, do you happen to know of any specific simulators
which are problematic? I would assume any recent version of SimNow is
up to date.
-hpa
next prev parent reply other threads:[~2008-01-18 6:34 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
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 [this message]
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=479046BA.7090903@zytor.com \
--to=hpa@zytor.com \
--cc=andi@firstfloor.org \
--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