From: Catalin Marinas <catalin.marinas@arm.com>
To: Joey Gouly <joey.gouly@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, nd@arm.com,
broonie@kernel.org, james.morse@arm.com, mark.rutland@arm.com,
maz@kernel.org, oliver.upton@linux.dev, shuah@kernel.org,
suzuki.poulose@arm.com, will@kernel.org, yuzenghui@huawei.com
Subject: Re: [PATCH v3 00/20] Permission Indirection Extension
Date: Mon, 5 Jun 2023 18:58:31 +0100 [thread overview]
Message-ID: <ZH4iR3Ap8whzV5Eu@arm.com> (raw)
In-Reply-To: <20230511110337.3385517-1-joey.gouly@arm.com>
On Thu, May 11, 2023 at 12:03:17PM +0100, Joey Gouly wrote:
> Joey Gouly (20):
> arm64/sysreg: Add ID register ID_AA64MMFR3
> arm64/sysreg: add system registers TCR2_ELx
> arm64/sysreg: update HCRX_EL2 register
> arm64/sysreg: add PIR*_ELx registers
> arm64: cpufeature: add system register ID_AA64MMFR3
> arm64: cpufeature: add TCR2 cpucap
> arm64: cpufeature: add Permission Indirection Extension cpucap
> KVM: arm64: Save/restore TCR2_EL1
> KVM: arm64: Save/restore PIE registers
> KVM: arm64: expose ID_AA64MMFR3_EL1 to guests
> arm64: add PTE_UXN/PTE_WRITE to SWAPPER_*_FLAGS
> arm64: add PTE_WRITE to PROT_SECT_NORMAL
> arm64: reorganise PAGE_/PROT_ macros
> arm64: disable EL2 traps for PIE
> arm64: add encodings of PIRx_ELx registers
> arm64: enable Permission Indirection Extension (PIE)
> arm64: transfer permission indirection settings to EL2
> arm64: Document boot requirements for PIE
> KVM: selftests: get-reg-list: support ID register features
> KVM: selftests: get-reg-list: add Permission Indirection registers
For some reason lore.kernel.org doesn't have this series, though it made
it to infradead (and this archive:
http://lists.openwrt.org/pipermail/linux-arm-kernel/2023-May/833014.html).
I applied it manually to the arm64 for-next/feat_s1pie (I don't have a
b4 automated reply for it).
Patch 14 conflicts with Kristina's series (for-next/feat_mops) and I
solved it in the merge resolution in for-next/core but this would get
lost when I redo the topic branch merges.
You might as well rebase this series on top of the arm64
for-next/feat_mops and repost so that we have the Link: tag as well.
Thanks.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-06-05 17:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230511110337.3385517-1-joey.gouly@arm.com>
[not found] ` <20230511110337.3385517-12-joey.gouly@arm.com>
2023-05-26 9:33 ` [PATCH v3 11/20] arm64: add PTE_UXN/PTE_WRITE to SWAPPER_*_FLAGS Catalin Marinas
2023-06-01 12:02 ` [PATCH v3 00/20] Permission Indirection Extension Mark Brown
[not found] ` <20230511110337.3385517-9-joey.gouly@arm.com>
2023-06-02 14:56 ` [PATCH v3 08/20] KVM: arm64: Save/restore TCR2_EL1 Catalin Marinas
2023-06-03 8:34 ` Marc Zyngier
[not found] ` <20230511110337.3385517-10-joey.gouly@arm.com>
2023-06-02 14:57 ` [PATCH v3 09/20] KVM: arm64: Save/restore PIE registers Catalin Marinas
2023-06-03 8:35 ` Marc Zyngier
[not found] ` <20230511110337.3385517-11-joey.gouly@arm.com>
2023-06-03 8:35 ` [PATCH v3 10/20] KVM: arm64: expose ID_AA64MMFR3_EL1 to guests Marc Zyngier
2023-06-05 17:58 ` Catalin Marinas [this message]
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=ZH4iR3Ap8whzV5Eu@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=james.morse@arm.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=nd@arm.com \
--cc=oliver.upton@linux.dev \
--cc=shuah@kernel.org \
--cc=suzuki.poulose@arm.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 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.