From: Leon Alrae <leon.alrae@imgtec.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-mips: add ERETNC instruction and Config5.LLB bit
Date: Fri, 5 Jun 2015 20:54:53 +0100 [thread overview]
Message-ID: <5571FE8D.2090706@imgtec.com> (raw)
In-Reply-To: <20150605094222.GA12018@aurel32.net>
On 05/06/15 10:42, Aurelien Jarno wrote:
> 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>
Thanks for your review!
> 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.
Yes, in current codebase the MIPS2 checks don't seem to have much value
and the removal makes sense. On the other hand I'm wondering if there
are QEMU users who maintain artificial MIPS1 CPU templates locally to
test if their compiler doesn't emit any non-MIPS1 instructions.
Leon
next prev parent reply other threads:[~2015-06-05 19:55 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
2015-06-05 19:54 ` Leon Alrae [this message]
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=5571FE8D.2090706@imgtec.com \
--to=leon.alrae@imgtec.com \
--cc=aurelien@aurel32.net \
--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).