From: Dan Malek <dan@embeddededge•com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades•com>
Cc: linux-ppc-embedded <linuxppc-embedded@ozlabs•org>
Subject: Re: update DataTLBMiss exception comment
Date: Tue, 19 Apr 2005 12:57:18 -0400 [thread overview]
Message-ID: <305099d2198de69f3cb25ce1a5074bde@embeddededge.com> (raw)
In-Reply-To: <20050419115253.GA2780@logos.cnet>
On Apr 19, 2005, at 7:52 AM, Marcelo Tosatti wrote:
> Since v2.6 DataTLBMiss doesnt jump to the page fault handler, it
> instead
> loads invalid TLB which in turn causes a DataTLBError exception.
Which, of course, is the logically correct way to do it. I guess I just
read too much into the suggestion in the manual to jump to the
"unused" Data Error exception vector under some miss conditions.
I tried to eliminate the immediate error fault that was going to
happen, but I guess we have to force that fault to get the proper
information in the fault registers.
> The comment on top of it haven't been update since the change.
>
> What about this?
Yes, thanks.
-- Dan
prev parent reply other threads:[~2005-04-19 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 11:52 update DataTLBMiss exception comment Marcelo Tosatti
2005-04-19 16:57 ` Dan Malek [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=305099d2198de69f3cb25ce1a5074bde@embeddededge.com \
--to=dan@embeddededge$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=marcelo.tosatti@cyclades$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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