From: Christopher Covington <cov@codeaurora.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 0/5] AArch64 TLB performance improvements
Date: Mon, 04 Aug 2014 09:11:48 -0400 [thread overview]
Message-ID: <53DF8694.4040107@codeaurora.org> (raw)
In-Reply-To: <CAFEAcA_zLOsOiQiNbuA9n6Dc2DrHPK7Uqes12dU=54YKAYKvpA@mail.gmail.com>
On 08/04/2014 06:32 AM, Peter Maydell wrote:
> On 4 August 2014 11:23, Alex Bennée <alex.bennee@linaro.org> wrote:
>> Peter Maydell writes:
>>> So:
>>> * there's clearly a big perf win to be had here
>>> * this patchset gives us that for 4K pages on AArch64
>>> * but it doesn't help for 4K pages on AArch32 (really
>>> common)
>>
>> Well for the AArch32 profile if you ran under qemu-system-aarch64 you
>> would be OK surely?
>
> Yes, but that's pretty non-obvious, and also it doesn't
> make much sense to the user to say "these 32 bit
> CPUs should be run under qemu-system-aarch64 but
> these other ones should be under qemu-system-arm".
>
>>> * and it's not going to be good for 64K pages on AArch64
>>> either (which I suspect will not be a rare choice)
>>
>> Does the kernel already use 64k pages for it's code?
>
> There's a config option, which will cause it to use 64K
> pages for everything including userspace.
> (There's also 16K pages but I forget if Linux has support
> for those.) I think the kernel can also use 64K pages in
> some cases even in a 4K page config, but I don't know the
> details.
Linux support for the 16K granule has not been merged nor have I seen any
patches for it.
With a 4K granule one can early out to 1GiB blocks ("gigabyte kernel logical
mappings") [1] or 2MiB blocks ("huge pages") [2].
With a 64K granule, one can early out to 512MiB blocks ("huge pages") [2].
1. http://permalink.gmane.org/gmane.linux.ports.arm.kernel/322436
2. http://comments.gmane.org/gmane.linux.kernel.mm/100651
Regards,
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2014-08-04 13:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 15:20 [Qemu-devel] [PATCH v2 0/5] AArch64 TLB performance improvements Alex Bennée
2014-07-30 15:20 ` [Qemu-devel] [PATCH v2 1/5] target-arm: don't hardcode mask values in arm_cpu_handle_mmu_fault Alex Bennée
2014-07-30 15:20 ` [Qemu-devel] [PATCH v2 2/5] target-arm: A64: fix TLB flush instructions Alex Bennée
2014-07-30 15:20 ` [Qemu-devel] [PATCH v2 3/5] target-arm: A64: fix use 12 bit page tables for AArch64 Alex Bennée
2014-07-30 15:20 ` [Qemu-devel] [PATCH v2 4/5] scripts/make_device_config.sh: inline includes Alex Bennée
2014-07-30 15:20 ` [Qemu-devel] [PATCH v2 5/5] target-arm: A64: disable a bunch of ARMv5 machines Alex Bennée
2014-08-01 16:45 ` Christopher Covington
2014-08-01 17:32 ` Peter Maydell
2014-08-01 16:06 ` [Qemu-devel] [PATCH v2 0/5] AArch64 TLB performance improvements Peter Maydell
2014-08-01 22:26 ` Peter Maydell
2014-08-04 10:23 ` Alex Bennée
2014-08-04 10:32 ` Peter Maydell
2014-08-04 13:11 ` Christopher Covington [this message]
2014-08-06 20:32 ` Richard Henderson
2014-08-01 19:35 ` Paolo Bonzini
2014-08-04 10:29 ` Alex Bennée
2014-08-04 11:34 ` Alex Bennée
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=53DF8694.4040107@codeaurora.org \
--to=cov@codeaurora.org \
--cc=alex.bennee@linaro.org \
--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).