mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Athlon possible fixes
Date: Mon, 7 May 2001 01:00:22 +1200	[thread overview]
Message-ID: <20010507010022.A32198@metastasis.f00f.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:

    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.

depends, maybe it depends on what part of the northbridge it
traverses, so it may only affect RAM and not PCI/AGP memory

it should be possible to write a test program that uses /dev/mem to
test for this is someone has a buggy MB (or wants to send me one,
I'll gladly do it -- my MBs work perfect it seems)


  --cw
    
    
    

  reply	other threads:[~2001-05-06 13:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-05  7:35 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 [this message]
2001-05-11  4:02     ` Ralf Baechle
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=20010507010022.A32198@metastasis.f00f.org \
    --to=cw@f00f.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 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®