From: Olof Johansson <olof@lixom.net>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] Make instruction dumping work in real mode.
Date: Mon, 24 Sep 2007 20:41:32 -0500 [thread overview]
Message-ID: <20070925014132.GA31979@lixom.net> (raw)
In-Reply-To: <20070924190100.GB4761@loki.buserror.net>
On Mon, Sep 24, 2007 at 02:01:00PM -0500, Scott Wood wrote:
> On non-book-E, if a faulting PC is in the first few pages, and it's not an
> ITLB miss, it's likely executing in real mode, probably at an exception vector.
>
> Rather than print a useless XXXXXXXX, it is assumed that this is the case, and
> the address is treated as physical. This helps when debugging corruption at
> the beginning of memory.
Please use regs->msr & MSR_IR instead.
-Olof
prev parent reply other threads:[~2007-09-25 1:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 19:01 [PATCH] Make instruction dumping work in real mode Scott Wood
2007-09-25 1:41 ` Olof Johansson [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=20070925014132.GA31979@lixom.net \
--to=olof@lixom.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
/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).