From: Ralf Baechle <ralf@linux-mips.org>
To: Stanislaw Skowronek <sskowron@ET.PUT.Poznan.PL>
Cc: linux-mips@linux-mips.org
Subject: Re: TLB on R10k
Date: Wed, 28 Apr 2004 19:27:21 +0200 [thread overview]
Message-ID: <20040428172721.GA28007@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.4.10.10404280734480.9183-100000@helios.et.put.poznan.pl>
On Wed, Apr 28, 2004 at 07:37:06AM +0200, Stanislaw Skowronek wrote:
> > Have you verified that the UX bit is set correctly by your kernel? BEV
> > also plays a role but since you survive BogoMIPS it should be right.
>
> >From what I remember, the UX bit is fixed set. I have made the machine
> print a '*' (no, I didn't use printk, but since it's my own console
> driver I'm pretty sure it can work in interrupts - all it does is
> hardware writes) whenever it gets a TLB refill and flushed the TLB before
> entering usermode. Guess what, I didn't get a single '*' after ERET. To
> verify my method, I've made a single read from the usermode PC from the
> kernel, and the '*' appeared. I don't know what's up.
printk can be used in exceptions.
Be careful when changing the TLB exception handlers. They occupy slots
of just 128 bytes or 32 instructions. Maybe your debugging code just
extended it beyond that maximum?
Ralf
next prev parent reply other threads:[~2004-04-28 17:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-27 18:07 TLB on R10k Stanislaw Skowronek
2004-04-27 18:33 ` Thiemo Seufer
2004-04-27 18:54 ` Stanislaw Skowronek
2004-04-27 19:28 ` Ralf Baechle
2004-04-28 5:37 ` Stanislaw Skowronek
2004-04-28 5:37 ` Stanislaw Skowronek
2004-04-28 17:27 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-28 15:05 Alex Deucher
2004-04-28 15:05 ` Alex Deucher
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=20040428172721.GA28007@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=sskowron@ET.PUT.Poznan.PL \
/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