lkml.org 
[lkml]   [2003]   [Oct]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRE: [PATCH 2.4.23-pre8] Remove broken prefetching in free_one_pgd()
Date
From
> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:58    [W:0.030 / U:0.096 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site