linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Thomas Tai <thomas.tai@oracle.com>
Cc: kvmarm@lists.cs.columbia.edu, james.morse@arm.com,
	linux-arm-kernel@lists.infradead.org,
	julien.thierry.kdev@gmail.com, suzuki.poulose@arm.com
Subject: Re: [PATCH] KVM: arm64: Fixes ARM VM hangs at boot
Date: Thu, 01 Oct 2020 09:30:58 +0100	[thread overview]
Message-ID: <f906ecd23609bbdf4a1db991624943d5@kernel.org> (raw)
In-Reply-To: <20200930221239.488744-1-thomas.tai@oracle.com>

Hi Thomas,

On 2020-09-30 23:12, Thomas Tai wrote:
> When using the latest kernel v5.9-rc7 on an ARM server, VMs could
> hang at boot with no output. The commit a0e50aa3f4a8 removed
> asm(ALTERNATIVE("isb", "nop", ARM64_WORKAROUND_SPECULATIVE_AT)),
> it looks like isb is still needed for non
> ARM64_WORKAROUND_SPECULATIVE_AT host when switching to guest.

Is that on an eMAG system, by any chance?

> 
> The code fragment for the original patch:
> -       /* __load_guest_stage2() includes an ISB for the workaround. */
> -       __load_guest_stage2(kvm);
> -       asm(ALTERNATIVE("isb", "nop", 
> ARM64_WORKAROUND_SPECULATIVE_AT));
> +       __load_guest_stage2(mmu);
> 
> The code should have been:
> -       /* __load_guest_stage2() includes an ISB for the workaround. */
> -       __load_guest_stage2(kvm);
> -       asm(ALTERNATIVE("isb", "nop", 
> ARM64_WORKAROUND_SPECULATIVE_AT));
> +       __load_guest_stage2(mmu);
> +       asm(ALTERNATIVE("isb", "nop", 
> ARM64_WORKAROUND_SPECULATIVE_AT));
> ie, the workaround is still needed.
> 
> Fixes: a0e50aa3f4a8 ("KVM: arm64: Factor out stage 2 page table data 
> from
> struct kvm")
> 
> Signed-off-by: Thomas Tai <thomas.tai@oracle.com>
> ---
>  arch/arm64/kvm/hyp/nvhe/tlb.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm64/kvm/hyp/nvhe/tlb.c 
> b/arch/arm64/kvm/hyp/nvhe/tlb.c
> index 69eae60..536496e 100644
> --- a/arch/arm64/kvm/hyp/nvhe/tlb.c
> +++ b/arch/arm64/kvm/hyp/nvhe/tlb.c
> @@ -32,6 +32,7 @@ static void __tlb_switch_to_guest(struct kvm_s2_mmu 
> *mmu,
>  	}
> 
>  	__load_guest_stage2(mmu);
> +	asm(ALTERNATIVE("isb", "nop", ARM64_WORKAROUND_SPECULATIVE_AT));
>  }
> 
>  static void __tlb_switch_to_host(struct tlb_inv_context *cxt)

Ouch. I remember fixing this a while ago, but somehow dropped it
after applying it and *not* merging it...

Thanks a lot for the heads up!

         M.

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/commit/?h=kvm-arm64/pre-nv-5.9
-- 
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-10-01  8:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 22:12 [PATCH] KVM: arm64: Fixes ARM VM hangs at boot Thomas Tai
2020-10-01  8:30 ` Marc Zyngier [this message]
2020-10-01 12:59   ` Thomas Tai

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=f906ecd23609bbdf4a1db991624943d5@kernel.org \
    --to=maz@kernel.org \
    --cc=james.morse@arm.com \
    --cc=julien.thierry.kdev@gmail.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=suzuki.poulose@arm.com \
    --cc=thomas.tai@oracle.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 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).