From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: manfred@colorfullife.com (Manfred Spraul)
Cc: bergsoft@home.com, linux-kernel@vger.kernel.org
Subject: Re: REVISED: Experimentation with Athlon and fast_page_copy
Date: Fri, 4 May 2001 22:43:32 +0100 (BST) [thread overview]
Message-ID: <E14vnMM-00084d-00@the-village.bc.nu> (raw)
In-Reply-To: <3AF2FF93.44A2C49@colorfullife.com> from "Manfred Spraul" at May 04, 2001 09:14:27 PM
> prefetch 320(%0) can fetch memory behind the end of the source page.
> Perhaps it accesses memory in the ISA hole, or beyond the end of memory?
> Could you post the e820 map from dmesg?
>
> It's possible to build manually a memory map.
> Could you build one with wide margins from "dangerous" areas? (untested:
> mem=exactmap mem=620k@0 mem=<your mem in MB-2>M@1M)
>
> Then boot with prefetch enabled.
That might not be the actual bug but for rev 1 Athlon it is a real bug. The
first step athlons have an unfortunate problem in that will prefetch
memory marked uncachable and corrupt their caches with it.
Arjan - care to unroll the tail 320 bytes of copying from the main loop ?
next prev parent reply other threads:[~2001-05-04 21:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 19:14 Manfred Spraul
2001-05-04 19:30 ` Seth Goldberg
2001-05-04 21:43 ` Alan Cox [this message]
2001-05-08 21:15 ` Arjan van de Ven
-- strict thread matches above, loose matches on Subject: below --
2001-05-05 17:34 Jeremy
2001-05-05 2:28 Dieter Nützel
2001-05-05 7:13 ` Alan Cox
2001-05-09 23:56 ` Dieter Nützel
2001-05-04 17:22 Seth Goldberg
2001-05-04 19:48 ` Brian Gerst
2001-05-04 21:09 ` Alan Cox
2001-05-04 22:26 ` Aaron Tiensivu
2001-05-04 18:10 ` Bobby D. Bryant
2001-05-05 6:43 ` John R Lenton
2001-05-05 7:20 ` Alan Cox
2001-05-07 1:26 ` John R Lenton
2001-05-07 1:30 ` Jeremy
2001-05-05 0:26 ` Joseph Carter
2001-05-05 3:51 ` Chris Wedgwood
2001-05-05 4:08 ` Seth Goldberg
2001-05-05 5:45 ` Joseph Carter
2001-05-09 2:11 ` Tom Leete
2001-05-09 8:49 ` Alan Cox
2001-05-09 11:38 ` Tom Leete
2001-05-09 12:38 ` Alan Cox
2001-05-09 13:02 ` Tom Leete
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=E14vnMM-00084d-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bergsoft@home.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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
all inboxes | Powered by JetHome®