From: Ralf Baechle <ralf@uni-koblenz.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Chris Wedgwood <cw@f00f.org>, linux-kernel@vger.kernel.org
Subject: Re: Athlon possible fixes
Date: Fri, 11 May 2001 01:02:53 -0300 [thread overview]
Message-ID: <20010511010253.A1257@bacchus.dhis.org> (raw)
In-Reply-To: <20010506142346.C31269@metastasis.f00f.org> <E14wO16-00023N-00@the-village.bc.nu>
In-Reply-To: <E14wO16-00023N-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sun, May 06, 2001 at 01:51:59PM +0100
On Sun, May 06, 2001 at 01:51:59PM +0100, Alan Cox wrote:
> > There really needs to be a hardware fix... this doesn't stop some
> > application having it's owne optimised code from breaking on some
> > hardware (think games and similation software perhaps).
>
> prefetch is virtually addresses. An application would need access to /dev/mem
> or similar. So the only folks I think it might actually bite are the Xserver
> people.
Prefetch bugs in hardware have biten Linux/68k as early as '94; a GVP SCSI
HBA on the Amiga may touch areas beyond the last valid RAM address when
doing DMA to the last page. Being a burned child from that time Linux/MIPS
didn't use the last RAM page just to be on the safe side.
Ralf
next prev parent reply other threads:[~2001-05-11 21:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-05 7:35 Athlon possible fixes Alan Cox
2001-05-05 16:26 ` Rogier Wolff
2001-05-05 16:42 ` Kurt Roeckx
2001-05-05 22:44 ` Seth Goldberg
2001-05-06 16:44 ` Jussi Laako
2001-05-06 17:41 ` Zilvinas Valinskas
2001-05-06 18:16 ` Christian Bornträger
2001-05-06 19:23 ` Marek Pętlicki
2001-05-07 18:54 ` Jussi Laako
2001-05-11 20:09 ` Jussi Laako
2001-05-11 20:22 ` Alan Cox
2001-05-12 9:51 ` Jussi Laako
2001-05-06 2:23 ` Chris Wedgwood
2001-05-06 12:51 ` Alan Cox
2001-05-06 13:00 ` Chris Wedgwood
2001-05-11 4:02 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-12 18:31 Ishikawa
2001-05-12 23:02 ` 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=20010511010253.A1257@bacchus.dhis.org \
--to=ralf@uni-koblenz.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cw@f00f.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.