From: Oliver Upton <oliver.upton@linux.dev>
To: linux-kernel@vger.kernel.org, Mostafa Saleh <smostafa@google.com>,
linux-arm-kernel@lists.infradead.org, maz@kernel.org,
kvmarm@lists.linux.dev
Cc: Oliver Upton <oliver.upton@linux.dev>,
bgardon@google.com, suzuki.poulose@arm.com, gshan@redhat.com,
tabba@google.com, yuzenghui@huawei.com, will@kernel.org,
james.morse@arm.com, qperret@google.com, catalin.marinas@arm.com
Subject: Re: [PATCH v3] KVM: arm64: Use BTI for nvhe
Date: Tue, 30 May 2023 18:01:40 +0000 [thread overview]
Message-ID: <168546969288.1201076.8549235994369669662.b4-ty@linux.dev> (raw)
In-Reply-To: <20230530150845.2856828-1-smostafa@google.com>
On Tue, 30 May 2023 15:08:45 +0000, Mostafa Saleh wrote:
> CONFIG_ARM64_BTI_KERNEL compiles the kernel to support ARMv8.5-BTI.
> However, the nvhe code doesn't make use of it as it doesn't map any
> pages with Guarded Page(GP) bit.
>
> kvm pgtable code is modified to map executable pages with GP bit
> if BTI is enabled for the kernel.
>
> [...]
Applied to kvmarm/next, thanks!
[1/1] KVM: arm64: Use BTI for nvhe
https://git.kernel.org/kvmarm/kvmarm/c/b53d4a272349
--
Best,
Oliver
next prev parent reply other threads:[~2023-05-30 18:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 15:08 Mostafa Saleh
2023-05-30 18:01 ` Oliver Upton [this message]
2023-07-04 13:41 ` Sudeep Holla
2023-07-04 14:18 ` Mostafa Saleh
2023-07-04 14:33 ` Sudeep Holla
2023-07-04 16:27 ` Mostafa Saleh
2023-07-04 19:25 ` Sudeep Holla
2023-07-05 15:56 ` Mostafa Saleh
2023-07-06 12:49 ` Mostafa Saleh
2023-07-06 14:27 ` Marc Zyngier
2023-07-06 15:23 ` Mostafa Saleh
2023-07-12 10:34 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-12 10:44 ` Marc Zyngier
2023-07-12 10:52 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-12 11:01 ` Marc Zyngier
2023-07-12 11:16 ` Linux regression tracking (Thorsten Leemhuis)
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=168546969288.1201076.8549235994369669662.b4-ty@linux.dev \
--to=oliver.upton@linux.dev \
--cc=bgardon@google.com \
--cc=catalin.marinas@arm.com \
--cc=gshan@redhat.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=qperret@google.com \
--cc=smostafa@google.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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
all inboxes | Powered by JetHome®