All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Donnefort <vdonnefort@google.com>
To: kvmarm@lists.linux.dev, maz@kernel.org, broonie@kernel.org
Cc: catalin.marinas@arm.com, will@kernel.org
Subject: Hang with nVHE mode and SME
Date: Wed, 26 Oct 2022 15:29:44 +0100	[thread overview]
Message-ID: <Y1lEWJ7rO4m1CKWL@google.com> (raw)

Hi All,

I'm experiencing hangs when running a guest on a Qemu platform and a host
started with nVHE mode.

The hang occurs in 

  static void __activate_traps(struct kvm_vcpu *vcpu)
  {
      ...
      if (cpus_have_final_cap(ARM64_SME)) {
           // HANG !

No problem though with either VHE or if the host boots with arm64.nosme.

The host (and the guest) are 6.1-rc1. My Qemu is 7.1.

My Qemu setup:

     $ qemu-system-aarch64 \
      -M virt \
      -machine virtualization=true -machine virt,gic-version=3  \
      -cpu max,pauth=off -smp 1 -m 16384                 \
      -drive file=rootfs.ext4,if=none,format=raw,id=hd0 \
      -device virtio-blk-device,drive=hd0 \
      -object rng-random,filename=/dev/urandom,id=rng0 \
      -netdev user,id=eth0,hostfwd=tcp::8022-:22,hostfwd=tcp::1234-:1234 \
      -device virtio-net-pci,netdev=eth0                \
      -nographic \
      -kernel arm64/boot/Image -append "earlycon root=/dev/vda kvm-arm.mode=nvhe nokaslr" \

The guest is run with kvm-tools:

     $ lkvm run -p "break=mount arm64.nosme" -k ~/Image --force-pci

Is it a known issue?

--
Vincent

             reply	other threads:[~2022-10-26 14:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 14:29 Vincent Donnefort [this message]
2022-10-26 15:07 ` Hang with nVHE mode and SME Mark Brown
2022-10-26 16:13   ` Marc Zyngier
2022-10-26 16:34     ` Mark Brown
2022-10-27  9:44       ` Peter Maydell
2022-10-27 12:01         ` Mark Brown
2022-10-27 21:16         ` Richard Henderson

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=Y1lEWJ7rO4m1CKWL@google.com \
    --to=vdonnefort@google.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=maz@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.