qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Leon Alrae <leon.alrae@imgtec.com>
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: Fri, 20 Feb 2015 13:11:57 +0000 (GMT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1502200216190.1995@eddie.linux-mips.org> (raw)
In-Reply-To: <54E5C9D0.6010700@imgtec.com>

On Thu, 19 Feb 2015, Leon Alrae wrote:

> >  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.

 I agree the patch itself is clear, but someone reading the commit might 
infer this is the only place the Address Error exception happens.  Also 
the patch itself does not show up in some places, e.g. `git log' where -p 
hasn't been also supplied, to complement information provided in the log.

> >  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.

 Great that you checked, thanks!

  Maciej

      reply	other threads:[~2015-02-20 13:12 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
2015-02-20 13:11     ` Maciej W. Rozycki [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=alpine.LFD.2.11.1502200216190.1995@eddie.linux-mips.org \
    --to=macro@linux-mips.org \
    --cc=aurelien@aurel32.net \
    --cc=leon.alrae@imgtec.com \
    --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 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).