| To: | Carsten Langgaard <carstenl@mips.com> |
|---|---|
| Subject: | Re: Promblem with PREF (prefetching) in memcpy |
| From: | Alan Cox <alan@lxorguk.ukuu.org.uk> |
| Date: | 04 Oct 2002 13:36:08 +0100 |
| Cc: | Dominic Sweetman <dom@algor.co.uk>, Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org |
| In-reply-to: | <3D9D855B.12128FA2@mips.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <3D9D484B.4C149BD8@mips.com> <200210041153.MAA12052@mudchute.algor.co.uk> <3D9D855B.12128FA2@mips.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
On Fri, 2002-10-04 at 13:11, Carsten Langgaard wrote: > Is a bus error exception an address related exception ? > I'm afraid some implementation think it's not. > So you need an option for broken systems, no new news 8) > What about an UART RX register, we might loose a character ? > You can also configure you system, so you get a external interrupt from you > system controller in case of a bus error, there is no way the CPU can > relate this interrupt to the prefetching. The use of memcpy for I/O space isnt permitted in Linux, thats why we have memcpy_*_io stuff. Thus prefetches should never touch 'special' spaces. (On x86 the older Athlons corrupt their cache if you do this so its not a mips specific matter) |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Promblem with PREF (prefetching) in memcpy, Carsten Langgaard |
|---|---|
| Next by Date: | Re: Promblem with PREF (prefetching) in memcpy, Hartvig Ekner |
| Previous by Thread: | Re: Promblem with PREF (prefetching) in memcpy, Carsten Langgaard |
| Next by Thread: | Re: Promblem with PREF (prefetching) in memcpy, Carsten Langgaard |
| Indexes: | [Date] [Thread] [Top] [All Lists] |