[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH] target-mips: fix MIPS64R6-generic configuration
From: |
Aurelien Jarno |
Subject: |
Re: [Qemu-devel] [PATCH] target-mips: fix MIPS64R6-generic configuration |
Date: |
Wed, 1 Jul 2015 16:06:54 +0200 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On 2015-07-01 14:57, Yongbok Kim wrote:
> On 01/07/2015 14:48, Aurelien Jarno wrote:
> > On 2015-06-29 10:11, Yongbok Kim wrote:
> >> Fix core configuration for MIPS64R6-generic to make it as close as
> >> I6400.
> >> I6400 core has 48-bit of Virtual Address available (SEGBITS).
> >> MIPS SIMD Architecture is available.
> >> Rearrange order of bits to match the specification.
> >>
> >> Signed-off-by: Yongbok Kim <address@hidden>
> >> ---
> >> target-mips/mips-defs.h | 2 +-
> >> target-mips/translate_init.c | 18 +++++++++---------
> >> 2 files changed, 10 insertions(+), 10 deletions(-)
> >
> > Reviewed-by: Aurelien Jarno <address@hidden>
> >
> > That said given we are getting closer to the I6400 CPU model, shouldn't
> > we try to directly model a I6400 core (even if we have to disable some
> > features like IEEE 754-2008 FP) instead of a generic MIPS64R6 core?
> >
>
> I fully agree with that but detailed specification of I6400 has not been
> published yet, therefore for the time being we will need to use the generic
Oh ok.
> core name. However we could rename mips32r5-generic into P5600 with such
> restrictions - Hardware page table walk, Virtualization, EVA.
> What do you think?
I think it's a good idea, as long as we keep the config register in sync
with what is actually implemented.
That also reminds me that we should look at implementing hardware page
table walk. That should be relatively easy to implement, and provide a
huge performance boost (exceptions cost a lot on QEMU).
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
address@hidden http://www.aurel32.net