From: Leon Alrae <leon.alrae@imgtec.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: qemu-devel@nongnu.org, aurelien@aurel32.net
Subject: Re: [Qemu-devel] [PATCH] target-mips: fix CP0.BadVAddr by stopping translation on Address error
Date: Thu, 19 Feb 2015 11:32:32 +0000 [thread overview]
Message-ID: <54E5C9D0.6010700@imgtec.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1501280027470.28301@eddie.linux-mips.org>
On 28/01/2015 00:39, Maciej W. Rozycki wrote:
> On Mon, 26 Jan 2015, Leon Alrae wrote:
>
>> BadVAddr is supposed to capture the most recent address that caused
>> the exception. Currently this is not happening as translation is not stopped
>> and BadVAddr is updated with subsequent addresses.
>>
>> Signed-off-by: Leon Alrae <leon.alrae@imgtec.com>
>> ---
>
> I think this deserves a better description as it is about the specific
> case of an unaligned standard MIPS instruction fetch. Address Error
> exceptions can also happen for other reasons: unaligned data accesses or
> any accesses outside memory segments the current execution mode is allowed
> to reach.
I believe that the one line change in the patch makes that clear. I
agree however that the description itself could be more precise.
> While at it I think it may be worth double-checking if the other places
> that trigger this exception get it right.
Other places seem to look fine. Even decode_micromips_opc handles it
correctly whereas decode_opc -– which obviously was implemented before
microMIPS -- never got fixed.
Regards,
Leon
next prev parent reply other threads:[~2015-02-19 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 16:10 [Qemu-devel] [PATCH] target-mips: fix CP0.BadVAddr by stopping translation on Address error Leon Alrae
2015-01-28 0:39 ` Maciej W. Rozycki
2015-02-19 11:32 ` Leon Alrae [this message]
2015-02-20 13:11 ` Maciej W. Rozycki
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=54E5C9D0.6010700@imgtec.com \
--to=leon.alrae@imgtec.com \
--cc=aurelien@aurel32.net \
--cc=macro@linux-mips.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.