From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Suzuki K Poulose <Suzuki.Poulose@arm.com>
Subject: Re: [PATCH v4 0/4] E0PD support
Date: Wed, 30 Oct 2019 12:26:32 +0000 [thread overview]
Message-ID: <20191030122631.GC10294@arrakis.emea.arm.com> (raw)
In-Reply-To: <20191024214207.20588-1-broonie@kernel.org>
On Thu, Oct 24, 2019 at 10:42:03PM +0100, Mark Brown wrote:
> This series adds support for E0PD. We enable E0PD unconditionally where
> present on systems where all the CPUs in the system support E0PD and
> change to not enabling KPTI by default on systems where we have enabled
> E0PD. It also converts the runtime checks for use of non-global mappings
> into a variable.
>
> v4: Use a variable to store our decision about using non-global mappings
> rather than rechecking constantly at runtime. I've added this as a
> separate patch mainly for bisection.
> v3: Make E0PD a system wide feature.
>
> Mark Brown (4):
> arm64: Add initial support for E0PD
> arm64: Factor out checks for KASLR in KPTI code into separate function
> arm64: Don't use KPTI where we have E0PD
> arm64: Use a variable to store non-global mappings decision
The patches look fine to me and I'm planning to queue them (with the
additional changes I mentioned on patch 4, I can do them locally).
I can still add acks/reviews in the next couple of days but I'd like to
push them into -next fairly soon to get some exposure.
Thanks.
--
Catalin
_______________________________________________
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-10-30 12:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 21:42 [PATCH v4 0/4] E0PD support Mark Brown
2019-10-24 21:42 ` [PATCH v4 1/4] arm64: Add initial support for E0PD Mark Brown
2019-10-24 21:42 ` [PATCH v4 2/4] arm64: Factor out checks for KASLR in KPTI code into separate function Mark Brown
2019-10-24 21:42 ` [PATCH v4 3/4] arm64: Don't use KPTI where we have E0PD Mark Brown
2019-10-24 21:42 ` [PATCH v4 4/4] arm64: Use a variable to store non-global mappings decision Mark Brown
2019-10-30 12:13 ` Catalin Marinas
2019-10-30 12:41 ` Mark Brown
2019-10-30 14:17 ` Catalin Marinas
2019-10-31 8:18 ` Mark Brown
2019-10-31 10:18 ` Catalin Marinas
2019-10-31 10:35 ` Mark Brown
2019-11-04 17:20 ` Mark Brown
2019-10-30 12:26 ` Catalin Marinas [this message]
2019-10-30 12:54 ` [PATCH v4 0/4] E0PD support Mark Brown
2019-10-31 11:26 ` Will Deacon
2019-10-31 12:13 ` John Garry
2019-10-31 12:42 ` Will Deacon
2019-10-31 13:00 ` Mark Brown
2019-10-31 13:09 ` Will Deacon
2019-10-31 14:13 ` John Garry
2019-10-31 16:06 ` Ard Biesheuvel
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=20191030122631.GC10294@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=Suzuki.Poulose@arm.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@kernel.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).