From: Pete Zaitcev <zaitcev@redhat.com>
To: Jiri Gaisler <jiri@gaisler.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Clean kernel patch for LEON/SPARC
Date: Wed, 20 Aug 2003 13:50:54 -0400 [thread overview]
Message-ID: <20030820135054.E6511@devserv.devel.redhat.com> (raw)
In-Reply-To: <3F43B061.3010805@gaisler.com>; from jiri@gaisler.com on Wed, Aug 20, 2003 at 07:31:13PM +0200
> Date: Wed, 20 Aug 2003 19:31:13 +0200
> From: Jiri Gaisler <jiri@gaisler.com>
> > Did you guys figure out the cause of the severe problem
> > with cache corruption?
>
> Yes, this was a virtual address aliasing problem. Leon2 has
> virtual caches but the MMU has no aliasing detection, so we
> are forced to flush the cache on each task switch. Our next
> processor (leon3) will have to switch to either physical caches
> or have some form of aliasing detection ...
Physical cache is always welcome, but I'm wondering if it's
really that needed, as you're not doing SMP. Do you have
the Schimmel's book?
-- Pete
prev parent reply other threads:[~2003-08-20 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F43551A.1060901@gaisler.com>
[not found] ` <20030820123311.A6511@devserv.devel.redhat.com>
2003-08-20 17:31 ` Clean kernel patch for LEON/SPARC Jiri Gaisler
2003-08-20 17:50 ` Pete Zaitcev [this message]
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=20030820135054.E6511@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=jiri@gaisler.com \
--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