From: Will Deacon <will@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
John Garry <john.garry@huawei.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/4] E0PD support
Date: Thu, 31 Oct 2019 13:09:48 +0000 [thread overview]
Message-ID: <20191031130948.GA27196@willie-the-truck> (raw)
In-Reply-To: <20191031130018.GQ4568@sirena.org.uk>
On Thu, Oct 31, 2019 at 02:00:18PM +0100, Mark Brown wrote:
> On Thu, Oct 31, 2019 at 12:42:18PM +0000, Will Deacon wrote:
> > On Thu, Oct 31, 2019 at 12:13:35PM +0000, John Garry wrote:
>
> > > I booted our D05 and D06 boards with that branch and did not experience the
> > > pauses which we reported some time ago.
>
> > Hmm. So I annotated the code locally and I see that we do rewrite swapper
> > in this case, so I'm surprised you're not seeing the performance issue
> > you ran into with this before. Have you got KASLR enabled and are you
> > passing a non-zero seed?
>
> Gah, sorry - I tested change which sets arm64_use_ng_mappings
> early, should be sitting on my machine at home, in mm/init.c.
> That will mean that there's only a slowdown in cases where we
> have a mix of E0PD and non-E0PD CPUs with the boot CPU having
> E0PD, hopefully no such systems have very large amounts of
> memory.
>
> I'll post it Monday at the latest.
Thanks, Mark.
Will
_______________________________________________
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-31 13:09 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 ` [PATCH v4 0/4] E0PD support Catalin Marinas
2019-10-30 12:54 ` 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 [this message]
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=20191031130948.GA27196@willie-the-truck \
--to=will@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=john.garry@huawei.com \
--cc=linux-arm-kernel@lists.infradead.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).