From: Richard Henderson <rth@twiddle.net>
To: Artyom Tarasenko <atar4qemu@gmail.com>,
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH 12/25] target-sparc: Add MMU_REAL_IDX
Date: Fri, 15 Jan 2016 10:03:24 -0800 [thread overview]
Message-ID: <5699346C.9030402@twiddle.net> (raw)
In-Reply-To: <CACXAS8AmwFHn6t9GyS4pgDpDkDXi1U_7PpKGK0tzzBfz5pzybg@mail.gmail.com>
On 01/15/2016 05:17 AM, Artyom Tarasenko wrote:
> Hi Richard,
>
> please ignore my 2 previous mails: I've misread the commit message.
> The actual problem and a possible solution below.
>
> On Thu, Dec 17, 2015 at 9:57 PM, Richard Henderson <rth@twiddle.net> wrote:
>> This gives us a trivial way to access physical addresses
>> (aka "real addresses", in sun4v terminology)
>
> In sun4v terminology "real address" is not "physical addresses".
> There is just one more level of translation:
> VA->RA->PA
> which it's only visible from the hypervisor mode.
Correct, but...
> With MMU_REAL_IDX renamed to MMU_PHYS_IDX, I think we are fine.
... no. REAL is currently implemented as PHYS, true, but that's only because
we don't actually implemnet sun4v.
If we ever properly implement a sun4v platform, we will implement the bulk of
the hypervisor within qemu itself, for speed. At which point REAL will in fact
undergo that final layer of translation exactly as expected.
I think the naming is exactly correct, for the current sun4u implementation.
> (As I was reading this patch the last time, I thought the plan was to
> use the MMU_REAL_IDX for both real and physical accesses, hence the
> confusion. But using one index for two modes would have been a bad
> idea because we'd have to flush the translations every time we switch
> to/from hypervisor mode which is too often).
And that is exactly why hypervisor mode would not be implemented like you
think, but within qemu itself.
r~
next prev parent reply other threads:[~2016-01-15 18:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 13:17 [Qemu-devel] [PATCH 12/25] target-sparc: Add MMU_REAL_IDX Artyom Tarasenko
2016-01-15 18:03 ` Richard Henderson [this message]
2016-01-15 20:32 ` Artyom Tarasenko
2016-01-15 21:47 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2015-12-17 20:54 [Qemu-devel] [PATCH 00/25] target-sparc improvements Richard Henderson
2015-12-17 20:57 ` [Qemu-devel] [PATCH 12/25] target-sparc: Add MMU_REAL_IDX Richard Henderson
2016-01-11 11:15 ` Artyom Tarasenko
2016-01-11 12:01 ` Artyom Tarasenko
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=5699346C.9030402@twiddle.net \
--to=rth@twiddle.net \
--cc=atar4qemu@gmail.com \
--cc=aurelien@aurel32.net \
--cc=mark.cave-ayland@ilande.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.