From: Hollis Blanchard <hollisb@us.ibm.com>
To: David Gibson <dwg@au1.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: 44x bug: funny TLB writes?
Date: Fri, 21 Sep 2007 01:38:34 -0500 [thread overview]
Message-ID: <1190356714.25483.19.camel@basalt> (raw)
In-Reply-To: <20070921054218.GA13470@localhost.localdomain>
On Fri, 2007-09-21 at 15:42 +1000, David Gibson wrote:
> On Thu, Sep 20, 2007 at 10:34:12PM -0500, Hollis Blanchard wrote:
> > I seem to have come across a strange bug while doing KVM development. It
> > seems that the final tlbwe in finish_tlb (head_44x.S) is actually
> > leaking RPN bits into the "attribute" word.
> >
> > When I set a breakpoint there and press enter on the serial console, I
> > see r12=ef600703, which is the physical address of the UART on this chip
> > (440EP), plus the correct permission bits at the bottom.
> >
> > Am I crazy? I'm not really looking to step through that assembly right
> > now... Clearly (current) hardware is just ignoring these errant writes,
> > but it should be fixed.
>
> A quick glance at the code suggests this is indeed wrong. Hurrah.
> Another reason to rewrite the 44x tlb miss handling.
Just a quick fix would be fine too... ;)
I'm just glad it's not a KVM bug, because when I dumped the TLB state
and saw bizarre values I was getting really worried.
> PS. "errant" and "error" are not cognate, even if the chip doc
> writers think so...
According to Merriam Webster, errant 2c is "c : behaving wrongly <an
errant child>", so I'm OK with it.
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2007-09-21 6:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 3:34 44x bug: funny TLB writes? Hollis Blanchard
2007-09-21 5:42 ` David Gibson
2007-09-21 6:38 ` Hollis Blanchard [this message]
2007-09-21 6:47 ` David Gibson
2007-09-21 17:37 ` Hollis Blanchard
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=1190356714.25483.19.camel@basalt \
--to=hollisb@us.ibm.com \
--cc=dwg@au1.ibm.com \
--cc=linuxppc-dev@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).