From: Marc Zyngier <maz@kernel.org>
To: Andrew Scull <ascull@google.com>
Cc: qwandor@google.com, qperret@google.com,
Will Deacon <will@kernel.org>,
Suzuki Poulose <Suzuki.Poulose@arm.com>,
Steven Price <steven.price@arm.com>,
wedsonaf@google.com, tabba@google.com,
James Morse <James.Morse@arm.com>,
dbrazdil@google.com, kernel-team@android.com,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH] arm64: unify WORKAROUND_SPECULATIVE_AT_{NVHE,VHE}
Date: Fri, 27 Mar 2020 17:52:59 +0000 [thread overview]
Message-ID: <e280f3f31bd5edc9db55757fcfa4ec62@kernel.org> (raw)
In-Reply-To: <20200327174838.GD178422@google.com>
Hi Andrew,
On 2020-03-27 17:48, Andrew Scull wrote:
> Thanks, Steven. Could we look into the EPD* caching microarch details
> Marc was referring to for these A55 and A76 cores?
Only the folks that have access to the RTL can tell you, unfortunately.
Thankfully, there is a bunch of people on Cc that should be able to ping
the relevant teams and report back...
Thanks,
M.
--
Jazz is not dead. It just smells funny...
_______________________________________________
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:[~2020-03-27 17:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 14:39 [RFC PATCH] arm64: unify WORKAROUND_SPECULATIVE_AT_{NVHE,VHE} Andrew Scull
2020-03-27 14:59 ` Steven Price
2020-03-27 17:48 ` Andrew Scull
2020-03-27 17:52 ` Marc Zyngier [this message]
2020-03-27 18:09 ` Will Deacon
2020-03-28 11:23 ` Marc Zyngier
2020-03-30 10:06 ` Will Deacon
2020-04-03 12:57 ` Andrew Scull
2020-04-17 16:41 ` Will Deacon
2020-04-20 13:46 ` Steven Price
2020-03-27 16:11 ` James Morse
2020-03-27 16:59 ` Will Deacon
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=e280f3f31bd5edc9db55757fcfa4ec62@kernel.org \
--to=maz@kernel.org \
--cc=James.Morse@arm.com \
--cc=Suzuki.Poulose@arm.com \
--cc=ascull@google.com \
--cc=dbrazdil@google.com \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=qperret@google.com \
--cc=qwandor@google.com \
--cc=steven.price@arm.com \
--cc=tabba@google.com \
--cc=wedsonaf@google.com \
--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).