From: Brian Gerst <bgerst@didntduck.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Hugh Dickins <hugh@veritas.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: Tue, 27 Aug 2002 17:18:02 -0400 [thread overview]
Message-ID: <3D6BEC8A.5030905@didntduck.org> (raw)
In-Reply-To: Pine.LNX.4.44.0208271216440.1419-100000@home.transmeta.com
Linus Torvalds wrote:
> On Tue, 27 Aug 2002, Hugh Dickins wrote:
>
>>I just sent the 2.4.20-pre4 asm-i386/pgtable.h patch to Marcelo:
>>here's patch against 2.5.31 or current BK: please apply.
>
>
> This test is senseless, in my opinion:
>
>
>>+ if (cpu_has_pge) \
>>+ __flush_tlb_single(addr); \
>
>
> The test _should_ be for something like
>
> if (cpu_has_invlpg)
> __flush_tlb_single(addr);
>
> since we want to use the invlpg instruction regardless of any PGE issues
> if it is available.
>
> There's another issue, which is the fact that I do not believe that invlpg
> is even guaranteed to invalidate a G page at all - although obviously all
> current CPU's seem to work that way. However, I don't see that documented
> anywhere.
P4 System Programming Guide, Section 10.9:
The INVLPG instruction invalidates the TLB for a specific page. This
instruction is the most efficient in cases where software only needs to
invalidate a specific page, because it improves performance over
invalidating the whole TLB. This instruction is not affected by the
state of the G flag in a page-directory or page-table entry.
next prev parent reply other threads:[~2002-08-27 21:14 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 [this message]
2002-08-28 20:30 ` Hugh Dickins
2002-08-28 23:17 ` 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=3D6BEC8A.5030905@didntduck.org \
--to=bgerst@didntduck.org \
--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