From: Carsten Langgaard <carstenl@mips.com>
To: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Promblem with PREF (prefetching) in memcpy
Date: Fri, 04 Oct 2002 09:50:36 +0200 [thread overview]
Message-ID: <3D9D484B.4C149BD8@mips.com> (raw)
I think we have a problem with the PREF instructions spread out in the
memcpy function.
We are prefetching outside the area we are copying. That's usually not a
problem, but if we are prefetching outside the physical memory area
(with an unmapped kseg address), anything could happen.
We could get a bus error (which we potentially could handle), but even
worse we could have mapped the PCI space immediately following the the
RAM area and then anything could happen.
So I think, we either need to make sure not to prefetch outside a page
boundary or we make sure the last page in physical memory doesn't get
use for unmapped kernel addresses.
Any comments ?
/Carsten
--
_ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com
|\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
| \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556
Denmark http://www.mips.com
next reply other threads:[~2002-10-04 7:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 7:50 Carsten Langgaard [this message]
2002-10-04 11:53 ` Promblem with PREF (prefetching) in memcpy Dominic Sweetman
2002-10-04 12:11 ` Carsten Langgaard
2002-10-04 12:35 ` Dr. David Alan Gilbert
2002-10-04 12:36 ` Alan Cox
2002-10-04 12:35 ` Carsten Langgaard
2002-10-04 13:09 ` Alan Cox
2002-10-04 13:07 ` Hartvig Ekner
2002-10-04 13:07 ` Hartvig Ekner
2002-10-04 13:00 ` Kevin D. Kissell
2002-10-04 13:00 ` Kevin D. Kissell
2002-10-04 13:15 ` Alan Cox
2002-10-04 13:15 ` Kevin D. Kissell
2002-10-04 13:15 ` Kevin D. Kissell
2002-10-04 13:44 ` Alan Cox
2002-10-04 14:17 ` Kevin D. Kissell
2002-10-04 14:17 ` Kevin D. Kissell
2002-10-04 14:54 ` Alan Cox
2002-10-04 13:01 ` Maciej W. Rozycki
2002-10-04 13:17 ` Ralf Baechle
2002-10-04 13:32 ` Maciej W. Rozycki
2002-10-04 13:29 ` Dominic Sweetman
2002-10-04 13:46 ` Maciej W. Rozycki
2002-10-04 12:33 ` Hartvig Ekner
2002-10-04 12:33 ` Hartvig Ekner
2002-10-04 12:38 ` Ralf Baechle
2002-10-04 12:36 ` Kevin D. Kissell
2002-10-04 12:36 ` Kevin D. Kissell
2002-10-04 14:24 ` Dominic Sweetman
2002-10-04 14:24 ` Dominic Sweetman
2002-10-04 23:43 ` Ralf Baechle
2002-10-05 15:12 ` Hartvig Ekner
2002-10-05 15:12 ` Hartvig Ekner
2002-10-05 15:56 ` Alan Cox
2002-10-04 12:37 ` Kevin D. Kissell
2002-10-04 12:37 ` Kevin D. Kissell
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=3D9D484B.4C149BD8@mips.com \
--to=carstenl@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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