All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Leon Alrae <leon.alrae@imgtec.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-mips: add ERETNC instruction and Config5.LLB bit
Date: Fri, 5 Jun 2015 11:42:22 +0200	[thread overview]
Message-ID: <20150605094222.GA12018@aurel32.net> (raw)
In-Reply-To: <1433433631-5322-1-git-send-email-leon.alrae@imgtec.com>

On 2015-06-04 17:00, Leon Alrae wrote:
> ERETNC is identical to ERET except that an ERETNC will not clear the LLbit
> that is set by execution of an LL instruction, and thus when placed between
> an LL and SC sequence, will never cause the SC to fail.
> 
> Presence of ERETNC is denoted by the Config5.LLB.
> 
> Signed-off-by: Leon Alrae <leon.alrae@imgtec.com>
> ---
>  disas/mips.c                 |  1 +
>  target-mips/cpu.h            |  1 +
>  target-mips/helper.h         |  1 +
>  target-mips/op_helper.c      | 12 +++++++++++-
>  target-mips/translate.c      | 20 +++++++++++++++-----
>  target-mips/translate_init.c |  4 +++-
>  6 files changed, 32 insertions(+), 7 deletions(-)

Reviewed-by: Aurelien Jarno <aurelien@aurel32.net>

As a side note, I have seen that you have added a check for MIPS2 to the
ERET instruction. This is correct, but given in practice we don't
emulate any MIPS1 CPU, I do wonder if it's not the time to make MIPS2
the basic instruction set and remove all MIPS2 checks.

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

  reply	other threads:[~2015-06-05  9:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 16:00 [Qemu-devel] [PATCH] target-mips: add ERETNC instruction and Config5.LLB bit Leon Alrae
2015-06-05  9:42 ` Aurelien Jarno [this message]
2015-06-05 19:54   ` Leon Alrae
2015-06-22 18:03     ` 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=20150605094222.GA12018@aurel32.net \
    --to=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 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.