From: Michael Ellerman <michael@ellerman.id.au>
To: Bruce_Leonard@selinc.com
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Question regarding the DTLB Miss exceptions
Date: Thu, 08 Apr 2010 23:59:30 +1000 [thread overview]
Message-ID: <1270735170.19546.2.camel@concordia> (raw)
In-Reply-To: <OF788A7534.456B03AA-ON882576F6.00228BC4-882576F6.00233EC1@selinc.com>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
On Mon, 2010-03-29 at 23:24 -0700, Bruce_Leonard@selinc.com wrote:
> I'm tracking a problem that's leading me through DSI and DTLB miss
> exceptions on an MPC8347 (e300c1 core), and I've come across an oddity
> that I'm hoping someone can explain.
>
> When a DTLB Miss exception can't find a PTE for the virtual address being
> written/read, it dummies up the SPRs for a DSI exception and then calls
> directly into the DSI exception code. Just before the DTLB miss code
> stores a value into DSISR it sets bit 2, which for a DSI exception is a
> reserved bit and should be cleared. There's no comment on the code
> (.../arch/powerpc/kernel/head_32.S line 619 of the 2.6.33-rc1 kernel). Can
> anyone tell me why this bit is getting set?
You mean:
616 DataAddressInvalid:
617 mfspr r3,SPRN_SRR1
618 rlwinm r1,r3,9,6,6 /* Get load/store bit */
619 addis r1,r1,0x2000
620 mtspr SPRN_DSISR,r1
Is it trying to set DSISR_ISSTORE?
#define DSISR_ISSTORE 0x02000000 /* access was a store */
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-04-08 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 6:24 Question regarding the DTLB Miss exceptions Bruce_Leonard
2010-03-31 15:44 ` Joakim Tjernlund
2010-04-08 13:59 ` Michael Ellerman [this message]
2010-04-08 19:33 ` Bruce_Leonard
2010-04-11 8:39 ` Benjamin Herrenschmidt
2010-04-12 3:46 ` Bruce_Leonard
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=1270735170.19546.2.camel@concordia \
--to=michael@ellerman.id.au \
--cc=Bruce_Leonard@selinc.com \
--cc=linuxppc-dev@lists.ozlabs.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).