From: Yongbok Kim <yongbok.kim@imgtec.com>
To: Leon Alrae <leon.alrae@imgtec.com>, qemu-devel@nongnu.org
Cc: aurelien@aurel32.net
Subject: Re: [Qemu-devel] [PATCH 6/6] target-mips: enable features in MIPS64R6-generic CPU
Date: Mon, 20 Oct 2014 15:23:59 +0100 [thread overview]
Message-ID: <54451AFF.5010302@imgtec.com> (raw)
In-Reply-To: <1405354795-25884-7-git-send-email-leon.alrae@imgtec.com>
On 14/07/2014 17:19, Leon Alrae wrote:
> Signed-off-by: Leon Alrae<leon.alrae@imgtec.com>
> ---
> target-mips/translate_init.c | 11 +++++++++--
> 1 files changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/target-mips/translate_init.c b/target-mips/translate_init.c
> index bcfc46a..0b70d05 100644
> --- a/target-mips/translate_init.c
> +++ b/target-mips/translate_init.c
> @@ -519,7 +519,7 @@ static const mips_def_t mips_defs[] =
> },
> {
> /* A generic CPU supporting MIPS64 Release 6 ISA.
> - FIXME: It does not support all the MIPS64R6 features yet.
> + FIXME: Support IEEE 754-2008 FP and misaligned memory accesses.
> Eventually this should be replaced by a real CPU model. */
> .name = "MIPS64R6-generic",
> .CP0_PRid = 0x00010000,
> @@ -530,12 +530,19 @@ static const mips_def_t mips_defs[] =
> (2 << CP0C1_DS) | (4 << CP0C1_DL) | (3 << CP0C1_DA) |
> (0 << CP0C1_PC) | (1 << CP0C1_WR) | (1 << CP0C1_EP),
> .CP0_Config2 = MIPS_CONFIG2,
> - .CP0_Config3 = MIPS_CONFIG3,
> + .CP0_Config3 = MIPS_CONFIG3 | (1 << CP0C3_RXI) | (1 << CP0C3_BP) |
> + (1 << CP0C3_BI) | (1 << CP0C3_ULRI) | (1U << CP0C3_M),
> + .CP0_Config4 = MIPS_CONFIG4 | (0xfc << CP0C4_KScrExist) |
> + (3 << CP0C4_IE) | (1 << CP0C4_M),
> + .CP0_Config5_rw_bitmask = (1 << CP0C5_SBRI),
> .CP0_LLAddr_rw_bitmask = 0,
> .CP0_LLAddr_shift = 0,
> .SYNCI_Step = 32,
> .CCRes = 2,
> .CP0_Status_rw_bitmask = 0x30D8FFFF,
> + .CP0_PageGrain = (1 << CP0PG_IEC) | (1 << CP0PG_XIE) |
> + (1U << CP0PG_RIE),
> + .CP0_PageGrain_rw_bitmask = 0,
> .CP1_fcr0 = (1 << FCR0_F64) | (1 << FCR0_L) | (1 << FCR0_W) |
> (1 << FCR0_D) | (1 << FCR0_S) | (0x00 << FCR0_PRID) |
> (0x0 << FCR0_REV),
Reviewed-by: Yongbok Kim <yongbok.kim@imgtec.com>
Regards,
Yongbok
prev parent reply other threads:[~2014-10-20 14:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 16:19 [Qemu-devel] [PATCH 0/6] target-mips: implement new MIPS64 Release 6 features Leon Alrae
2014-07-14 16:19 ` [Qemu-devel] [PATCH 1/6] target-mips: add Config5.SBRI Leon Alrae
2014-10-16 14:32 ` Yongbok Kim
2014-07-14 16:19 ` [Qemu-devel] [PATCH 2/6] target-mips: implement forbidden slot Leon Alrae
2014-10-20 11:10 ` Yongbok Kim
2014-07-14 16:19 ` [Qemu-devel] [PATCH 3/6] target-mips: CP0_Status.CU0 no longer allows the user to access CP0 Leon Alrae
2014-10-17 9:58 ` Yongbok Kim
2014-07-14 16:19 ` [Qemu-devel] [PATCH 4/6] target-mips: add restrictions for possible values in registers Leon Alrae
2014-10-20 10:19 ` Yongbok Kim
2014-10-21 13:54 ` Leon Alrae
2014-07-14 16:19 ` [Qemu-devel] [PATCH 5/6] target-mips: correctly handle access to unimplemented CP0 register Leon Alrae
2014-10-20 10:49 ` Yongbok Kim
2014-07-14 16:19 ` [Qemu-devel] [PATCH 6/6] target-mips: enable features in MIPS64R6-generic CPU Leon Alrae
2014-10-20 14:23 ` Yongbok Kim [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=54451AFF.5010302@imgtec.com \
--to=yongbok.kim@imgtec.com \
--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).