From: Richard Henderson <rth@twiddle.net>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Peter Crosthwaite" <crosthwaite.peter@gmail.com>,
"Peter Crosthwaite" <crosthwaitepeter@gmail.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Edgar Iglesias" <edgari@xilinx.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] microblaze: Remove uses of TCGv and target_ulong
Date: Mon, 18 May 2015 11:37:58 -0700 [thread overview]
Message-ID: <555A3186.7000200@twiddle.net> (raw)
In-Reply-To: <CAEgOgz6aDHdqowjejgbqnjbshAXEJfctH1UNqNmusrstNR69mw@mail.gmail.com>
On 05/15/2015 01:52 PM, Peter Crosthwaite wrote:
> 2: Core code is converted to not use "target_ulong" (tcg_core_ulong?)
> and target_ulong becomes a target-specific code concept.
This is my favorite.
I did poke around with new tcg opcodes to break some of the TARGET_LONG_BITS
usage in the tcg backend. It wasn't terribly difficult until I reached the
memory helpers.
Aside from target_ulong addr, there's also TARGET_PAGE_MASK, TARGET_PAGE_SIZE,
TARGET_PAGE_BITS, CPU_TLB_SIZE. What's our position on the compatibility of
the mmu between the multi-arch platforms? I assume at the moment they must be
all the same?
Of course, I've mentioned before that ARM might well benefit from having these
values be variable and not constant at all. Primarily because of the armv5 1K
pages affecting aarch64.
r~
next prev parent reply other threads:[~2015-05-18 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 4:49 [Qemu-devel] [PATCH] microblaze: Remove uses of TCGv and target_ulong Peter Crosthwaite
2015-05-15 5:56 ` Edgar E. Iglesias
2015-05-15 15:41 ` Richard Henderson
2015-05-15 16:48 ` Peter Crosthwaite
2015-05-15 17:17 ` Richard Henderson
2015-05-15 20:52 ` Peter Crosthwaite
2015-05-18 18:37 ` Richard Henderson [this message]
2015-05-18 18:43 ` Peter Maydell
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=555A3186.7000200@twiddle.net \
--to=rth@twiddle.net \
--cc=afaerber@suse.de \
--cc=crosthwaite.peter@gmail.com \
--cc=crosthwaitepeter@gmail.com \
--cc=edgari@xilinx.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--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).