From: Yongbok Kim <yongbok.kim@imgtec.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: leon.alrae@imgtec.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-mips: fix MIPS64R6-generic configuration
Date: Wed, 1 Jul 2015 15:21:53 +0100 [thread overview]
Message-ID: <5593F781.7090307@imgtec.com> (raw)
In-Reply-To: <20150701140654.GP931@aurel32.net>
On 01/07/2015 15:06, Aurelien Jarno wrote:
> 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 <yongbok.kim@imgtec.com>
>>>> ---
>>>> target-mips/mips-defs.h | 2 +-
>>>> target-mips/translate_init.c | 18 +++++++++---------
>>>> 2 files changed, 10 insertions(+), 10 deletions(-)
>>>
>>> Reviewed-by: Aurelien Jarno <aurelien@aurel32.net>
>>>
>>> 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.
>
I will form a patch to do that.
> 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).
>
Actually I have implemented HTW (for MIPS32 only) but due to lack of
resources, I couldn't upstream it for 2.4. Please have a look at below commits.
https://github.com/yongbok/prpl-qemu/commit/b39e60b4039bb72ab5eccabfb75f6e6389d89bfd
https://github.com/yongbok/prpl-qemu/commit/4fd75126c1d78d84a91c659de17a5bc45efdef27
Regards,
Yongbok
prev parent reply other threads:[~2015-07-01 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 9:11 [Qemu-devel] [PATCH] target-mips: fix MIPS64R6-generic configuration Yongbok Kim
2015-06-30 13:03 ` Leon Alrae
2015-07-01 13:48 ` Aurelien Jarno
2015-07-01 13:57 ` Yongbok Kim
2015-07-01 14:06 ` Aurelien Jarno
2015-07-01 14:21 ` 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=5593F781.7090307@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).