From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Hugh Dickins <hugh@veritas.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Dave Jones <davej@suse.de>,
Marc Dietrich <Marc.Dietrich@hrz.uni-giessen.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] M386 flush_one_tlb invlpg
Date: 29 Aug 2002 00:17:58 +0100 [thread overview]
Message-ID: <1030576678.7190.80.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0208282059390.2079-100000@localhost.localdomain>
On Wed, 2002-08-28 at 21:30, Hugh Dickins wrote:
> New patch below defines cpu_has_invlpg as (boot_cpu_data.x86 > 3).
> But I do feel safer with that original cpu_has_pge test, which was
> using a decent capability flag, and only changed behaviour of the
> CONFIG_M386 __flush_tlb_one when it's necessary.
>
> Isn't CONFIG_M386 about maximum safe applicability, rather than speed?
> Am I imagining it, or were there a few i386 + i486 SMP machines built?
> Or might there be some i486 clone which didn't really implement invlpg,
> which could be used with a CONFIG_M386 kernel before this change,
> but not after? But perhaps I'm just dreaming up excuses for my
> senselessness - your call.
To answer that
There are no SMP i386 boxes that support Intel MP 1.1
There are a few SMP 486 boxes using MP 1.1
The nx586 processor is a '586' class CPU that has neither wp nor invlpg
by default. I believe however that it reports family '3' if it has the
hypercode loaded which lacks invlpg
prev parent reply other threads:[~2002-08-28 23:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-27 15:39 [PATCH] M386 flush_one_tlb invlpg Hugh Dickins
2002-08-27 19:22 ` Linus Torvalds
2002-08-27 20:45 ` Luca Barbieri
2002-08-27 20:57 ` Linus Torvalds
2002-08-27 21:32 ` Andrea Arcangeli
2002-08-27 21:18 ` Brian Gerst
2002-08-28 20:30 ` Hugh Dickins
2002-08-28 23:17 ` Alan Cox [this message]
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=1030576678.7190.80.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Marc.Dietrich@hrz.uni-giessen.de \
--cc=davej@suse.de \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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).