From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Leon Alrae <leon.alrae@imgtec.com>
Cc: qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH] target-mips: use CP0EnLo_XI instead of magic number
Date: Wed, 28 Jan 2015 23:11:49 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.11.1501280055020.28301@eddie.linux-mips.org> (raw)
In-Reply-To: <1422289059-6849-1-git-send-email-leon.alrae@imgtec.com>
On Mon, 26 Jan 2015, Leon Alrae wrote:
> Signed-off-by: Leon Alrae <leon.alrae@imgtec.com>
> ---
Enthusiastically:
Reviewed-by: Maciej W. Rozycki <macro@linux-mips.org>
However...
> diff --git a/target-mips/translate.c b/target-mips/translate.c
> index 635192c..77d89be 100644
> --- a/target-mips/translate.c
> +++ b/target-mips/translate.c
> @@ -4947,7 +4947,7 @@ static void gen_mfc0(DisasContext *ctx, TCGv arg, int reg, int sel)
> #if defined(TARGET_MIPS64)
> if (ctx->rxi) {
> TCGv tmp = tcg_temp_new();
> - tcg_gen_andi_tl(tmp, arg, (3ull << 62));
> + tcg_gen_andi_tl(tmp, arg, (3ull << CP0EnLo_XI));
> tcg_gen_shri_tl(tmp, tmp, 32);
... don't we need to do:
tcg_gen_andi_tl(arg, arg, ~(3ull << CP0EnLo_XI));
here and for EntryLo1 as well (for LPA-enabled processors)?
> tcg_gen_or_tl(arg, arg, tmp);
> tcg_temp_free(tmp);
And do we want to have CP0C3_LPA set in the few templates that do in the
first place? AFAICT we don't really implement LPA so this bit will
confuse software. Of course implementing it would be another option, not
very complicated AFAICS, and if we can track the requirement to update
MFC0 at that time, then the clean-up I mentioned above can be deferred
until then.
Maciej
next prev parent reply other threads:[~2015-01-28 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 16:17 [Qemu-devel] [PATCH] target-mips: use CP0EnLo_XI instead of magic number Leon Alrae
2015-01-28 23:11 ` Maciej W. Rozycki [this message]
2015-01-29 10:02 ` Leon Alrae
2015-01-29 11:08 ` 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=alpine.LFD.2.11.1501280055020.28301@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).