From: Richard Henderson <richard.henderson@linaro.org>
To: Dave Martin <Dave.Martin@arm.com>, linux-arm-kernel@lists.infradead.org
Cc: "Paul Elliott" <paul.elliott@arm.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Szabolcs Nagy" <szabolcs.nagy@arm.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will.deacon@arm.com>,
"Kristina Martšenko" <kristina.martsenko@arm.com>,
"Sudakshina Das" <sudi.das@arm.com>
Subject: Re: [PATCH 0/8] arm64: ARMv8.5-A: Branch Target Identification support
Date: Wed, 5 Jun 2019 16:12:03 -0500 [thread overview]
Message-ID: <935adf9b-0609-8dc6-5439-719422f4cd40@linaro.org> (raw)
In-Reply-To: <1558693533-13465-1-git-send-email-Dave.Martin@arm.com>
On 5/24/19 5:25 AM, Dave Martin wrote:
> Various things need nailing down before this can be upstreamable:
>
> * Not tested with hugepages yet. (If anyone has any suggestions about
> how best to do that, please shout!)
The qemu code_gen_buffer is generally between 32MB and 2GB, contiguous. It
usually gets AnonHugePage'd. I assume there's no difference in where the
hugepages come from on your side?
It won't be too difficult to modify qemu to make it's own code generation
BTI-safe, and is on the schedule to do eventually anyway.
r~
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-05 21:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 10:25 [PATCH 0/8] arm64: ARMv8.5-A: Branch Target Identification support Dave Martin
2019-05-24 10:25 ` [PATCH 1/8] binfmt_elf: Extract .note.gnu.property from an ELF file Dave Martin
2019-05-24 10:25 ` [PATCH 2/8] mm: Reserve asm-generic prot flag 0x10 for arch use Dave Martin
2019-05-24 10:25 ` [PATCH 3/8] arm64: docs: cpu-feature-registers: Document ID_AA64PFR1_EL1 Dave Martin
2019-05-24 10:25 ` [PATCH 4/8] arm64: Basic Branch Target Identification support Dave Martin
2019-05-24 13:02 ` Mark Rutland
2019-05-24 14:53 ` Dave Martin
2019-05-24 15:38 ` Mark Rutland
2019-05-24 16:12 ` Dave Martin
2019-05-24 17:19 ` Mark Rutland
2019-05-28 10:52 ` Dave P Martin
2019-06-06 17:11 ` Catalin Marinas
2019-06-06 17:23 ` Dave Martin
2019-06-06 17:34 ` Yu-cheng Yu
2019-06-06 17:56 ` Dave Martin
2019-05-24 10:25 ` [PATCH 5/8] elf: Parse program properties before destroying the old process Dave Martin
2019-05-24 10:25 ` [PATCH 6/8] elf: Allow arch to tweak initial mmap prot flags Dave Martin
2019-05-24 10:25 ` [PATCH 7/8] arm64: elf: Enable BTI at exec based on ELF program properties Dave Martin
2019-05-24 10:25 ` [PATCH 8/8] arm64: BTI: Decode BYTPE bits when printing PSTATE Dave Martin
2019-06-05 21:12 ` Richard Henderson [this message]
2019-06-06 9:34 ` [PATCH 0/8] arm64: ARMv8.5-A: Branch Target Identification support Dave Martin
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=935adf9b-0609-8dc6-5439-719422f4cd40@linaro.org \
--to=richard.henderson@linaro.org \
--cc=Dave.Martin@arm.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=kristina.martsenko@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=paul.elliott@arm.com \
--cc=sudi.das@arm.com \
--cc=szabolcs.nagy@arm.com \
--cc=will.deacon@arm.com \
/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).