From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [PATCH 2.4.23-pre8] Remove broken prefetching in free_one_pgd()
Date: Thu, 30 Oct 2003 21:36:23 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106755041809902@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106702916015259@msgid-missing>
> On Friday 24 October 2003 4:21 pm, David Mosberger wrote:
> > >>>>> On Fri, 24 Oct 2003 15:16:59 -0700, "Luck, Tony"
> <tony.luck@intel.com> said:
> > >> Different arches behave differently, though. In the
> case of ia64,
> > >> it'a always safe to prefetch (even with lfetch.fault).
> >
> > Tony> Not quite always ... this was how I found the efi
> trim.bottom
> > Tony> bug, since Linux had allocated a pgd at
> 0xa00000-16k, and the
> > Tony> lfetch that reached out beyond the end of the page to the
> > Tony> uncacheable address 0xa00000 took an MCA.
> >
> > But don't confuse cause and effect! The MCA was caused by a bad TLB
> > entry. The lfetch only triggered the latent bug (as might have a
> > instruction-prefetch).
>
> I'm assuming that the EFI memory map trim fixes prevent the bad
> TLB entry, and hence, the prefetching patch is not required by ia64
> in 2.4. Tony, let me know if otherwise.
If EFI trim is doing its job (and the current version now seems
to be handling all cases correctly), then you should no longer
be able to have a TLB entry erroneously marking an uncacheable
area of memory for cacheable access ... so you can keep the prefetch
for ia64 (David pointed out that dropping this prefetch has a
severe negative impact on lmbench fork+execve test).
-Tony
prev parent reply other threads:[~2003-10-30 21:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-24 20:56 [PATCH 2.4.23-pre8] Remove broken prefetching in free_one_pgd() Luck, Tony
2003-10-24 22:01 ` David Mosberger
2003-10-24 22:16 ` Luck, Tony
2003-10-24 22:21 ` David Mosberger
2003-10-25 20:10 ` Pavel Machek
2003-10-26 14:51 ` Dave Jones
2003-10-27 9:52 ` Pavel Machek
2003-10-27 11:58 ` Dave Jones
2003-10-30 20:57 ` Bjorn Helgaas
2003-10-30 21:36 ` Luck, Tony [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=marc-linux-ia64-106755041809902@msgid-missing \
--to=tony.luck@intel.com \
--cc=linux-ia64@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