From: David Gibson <david@gibson.dropbear.id.au>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Some more 4xx exception fixes
Date: Fri, 14 Sep 2001 08:26:35 +1000 [thread overview]
Message-ID: <20010914082635.F3851@zax> (raw)
In-Reply-To: <3BA11A49.A94ACBE@mvista.com>
On Thu, Sep 13, 2001 at 04:42:49PM -0400, Dan Malek wrote:
>
> David Gibson wrote:
>
> > Sorry, can you elaborate on that?
>
> No, you are right. We need to find a way to fix this, but
> I sure don't want yet another test and branch in the TLB handler.
There isn't one - check the patch. If we test ESPRN_DIZ, we don't
need to check ESPRN_DST because the fault must be a write fault.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-09-13 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-12 3:33 Some more 4xx exception fixes David Gibson
2001-09-12 15:42 ` Dan Malek
2001-09-13 7:51 ` David Gibson
2001-09-13 20:42 ` Dan Malek
2001-09-13 22:26 ` David Gibson [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=20010914082635.F3851@zax \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).