From: Jun Sun <jsun@mvista.com>
To: Nathan Field <ndf@ghs.com>
Cc: Daniel Jacobowitz <dan@debian.org>,
linux-mips@linux-mips.org, jsun@mvista.com
Subject: Re: ptrace induced instruction cache bug?
Date: Wed, 14 Jan 2004 16:40:11 -0800 [thread overview]
Message-ID: <20040114164011.F13471@mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0401141619110.1969-100000@zcar.ghs.com>; from ndf@ghs.com on Wed, Jan 14, 2004 at 04:22:01PM -0800
On Wed, Jan 14, 2004 at 04:22:01PM -0800, Nathan Field wrote:
> > There are too many things related to cache are wrong in 2.4.17. For
> > example,
> >
> > . flush_page_indexed() is not right for multi-way cache
> > . when you map user pages into kernel, you are sufferring potential cache
> > aliasing problem (BTW, we still suffer from this right now to a less degree)
> > . flush_page_to_ram() has a broken semantic, because it is not clear whether
> > the area mapped into user virt spaces should be flushed or not
> > ...
> >
> > In short, it is not worth your time to fix old bugs. Last time I
> > checked malta was working fine around 2.4.21. It shouldn't be too hard
> > to get it working again in the latest 2.4 branch.
> Is this the 2.4.21 from ftp.kernel.org, or do I need to get
> specific patches to get it to work? I looked at the cvs tree but it's
> currently a 2.6 release. Should I just check out the linux_2_4_branch
> version from linux-mips.org?
>
Yes. "linux_2_4" branch to be exact.
Jun
prev parent reply other threads:[~2004-01-15 0:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 2:34 ptrace induced instruction cache bug? Nathan Field
2004-01-13 15:01 ` Daniel Jacobowitz
2004-01-13 18:35 ` Nathan Field
2004-01-13 20:58 ` Daniel Jacobowitz
2004-01-14 23:36 ` Nathan Field
2004-01-15 0:07 ` Jun Sun
2004-01-15 0:22 ` Nathan Field
2004-01-15 0:22 ` Nathan Field
2004-01-15 0:40 ` Jun Sun [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=20040114164011.F13471@mvista.com \
--to=jsun@mvista.com \
--cc=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=ndf@ghs.com \
/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.