linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>,
	Steven Price <steven.price@arm.com>,
	James Morse <james.morse@arm.com>,
	Andrew Scull <ascull@google.com>,
	kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] arm64: Unify WORKAROUND_SPECULATIVE_AT_{NVHE,VHE}
Date: Mon, 04 May 2020 12:13:02 +0100	[thread overview]
Message-ID: <7b3cc0b0a3fa6d08d8c8413e4498d485@kernel.org> (raw)
In-Reply-To: <20200504105539.GA4879@willie-the-truck>

On 2020-05-04 11:55, Will Deacon wrote:
> On Mon, May 04, 2020 at 10:48:58AM +0100, Andrew Scull wrote:
>> Errata 1165522, 1319367 and 1530923 each allow TLB entries to be
>> allocated as a result of a speculative AT instruction. In order to
>> avoid mandating VHE on certain affected CPUs, apply the workaround to
>> both the nVHE and the VHE case for all affected CPUs.
>> 
>> Signed-off-by: Andrew Scull <ascull@google.com>
>> CC: Marc Zyngier <maz@kernel.org>
>> CC: James Morse <james.morse@arm.com>
>> CC: Suzuki K Poulose <suzuki.poulose@arm.com>
>> CC: Will Deacon <will@kernel.org>
>> CC: Steven Price <steven.price@arm.com>
>> ---
>> From v2 <20200422161346.67325-1-ascull@google.com>:
>>  - const_cap -> final_cap merge correction
>>  - based on 5.7 rc4
>> ---
>>  arch/arm64/Kconfig                | 39 
>> ++++++++++++++-----------------
>>  arch/arm64/include/asm/cpucaps.h  | 15 ++++++------
>>  arch/arm64/include/asm/kvm_host.h |  4 ----
>>  arch/arm64/include/asm/kvm_hyp.h  |  2 +-
>>  arch/arm64/kernel/cpu_errata.c    | 25 +++++++++-----------
>>  arch/arm64/kvm/hyp/switch.c       |  6 ++---
>>  arch/arm64/kvm/hyp/sysreg-sr.c    |  6 +++--
>>  arch/arm64/kvm/hyp/tlb.c          | 11 +++++----
>>  8 files changed, 50 insertions(+), 58 deletions(-)
> 
> Acked-by: Will Deacon <will@kernel.org>
> 
> We'll probably run into some trivial conflicts with the arm64 tree, but
> I'm happy to put this on a branch if it helps. Marc?

I'd rather we avoid the conflicts by not repainting all the capabilities
and just leave a capability unused until the next one fills in the slot.
But otherwise, I'll take a stable branch.

Also the current state of the KVM/arm tree is a bit crap as none of the
fixes have made it into Linus' tree yet, and I don't have a good base
for the current queue (the welcome-home branch could create havoc).

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

  reply	other threads:[~2020-05-04 11:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04  9:48 [PATCH v3] arm64: Unify WORKAROUND_SPECULATIVE_AT_{NVHE,VHE} Andrew Scull
2020-05-04 10:55 ` Will Deacon
2020-05-04 11:13   ` Marc Zyngier [this message]
2020-05-04 11:26     ` Will Deacon
2020-05-04 15:33 ` 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=7b3cc0b0a3fa6d08d8c8413e4498d485@kernel.org \
    --to=maz@kernel.org \
    --cc=ascull@google.com \
    --cc=james.morse@arm.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=steven.price@arm.com \
    --cc=suzuki.poulose@arm.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).