From: Luca Barbieri <ldb@ldb.ods.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "J.A. Magallon" <jamagallon@able.es>,
Linux-Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [RFC] [2.5 i386] GCC 3.1 -march support, PPRO_FENCE reduction, prefetch fixes and other CPU-related changes
Date: 04 Aug 2002 22:43:34 +0200 [thread overview]
Message-ID: <1028493814.26332.9.camel@ldb> (raw)
In-Reply-To: <1028498075.15200.29.camel@irongate.swansea.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
On Sun, 2002-08-04 at 23:54, Alan Cox wrote:
> On Sun, 2002-08-04 at 21:23, Luca Barbieri wrote:
> > Added, with the exception that sfence is only used if CONFIG_X86_OOSTORE
> > is not defined (currently never).
>
> Ok sorry I follow what you are doing. What I don't understand is why you
> are generating unneeded sfence/mfence instructions in the other cases ?
It was my fault: I explained it incorrectly. sfence is only used if both
CONFIG_X86_OOSTORE and CONFIG_MMXEXT are set, which currently never
happens with the existing processors.
> When we use MMX/SSE we need the view to be consistent anyway so the
> various copying routines already handle this internally.
That's why sfence is not used unless CONFIG_X86_OOSTORE (and
CONFIG_X86_MMXEXT) is defined.
mfence and lfence instead replace the "lock; addl $0,0(%%esp)". Is this
wrong?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-08-04 20:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 14:27 [PATCH] [RFC] [2.5 i386] GCC 3.1 -march support, PPRO_FENCE reduction, prefetch fixes and other CPU-related changes Luca Barbieri
2002-08-04 14:36 ` Thunder from the hill
2002-08-04 15:32 ` Sebastian Droege
2002-08-04 15:43 ` Luca Barbieri
2002-08-04 15:50 ` Alan Cox
2002-08-04 14:44 ` Luca Barbieri
2002-08-04 18:59 ` J.A. Magallon
2002-08-04 20:23 ` Luca Barbieri
2002-08-04 21:51 ` Alan Cox
2002-08-04 21:54 ` Alan Cox
2002-08-04 20:43 ` Luca Barbieri [this message]
2002-08-05 0:02 ` Alan Cox
2002-08-05 8:12 ` Luca Barbieri
2002-08-05 9:49 ` Alan Cox
2002-08-05 9:31 ` Luca Barbieri
2002-08-05 11:05 ` Alan Cox
2002-08-05 9:53 ` Luca Barbieri
2002-08-05 11:26 ` Alan Cox
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=1028493814.26332.9.camel@ldb \
--to=ldb@ldb.ods.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jamagallon@able.es \
--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