All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Fuad Tabba <tabba@google.com>
Cc: Mark Brown <broonie@kernel.org>,
	kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	oliver.upton@linux.dev, will@kernel.org, mark.rutland@arm.com,
	joey.gouly@arm.com, suzuki.poulose@arm.com, yuzenghui@huawei.com,
	catalin.marinas@arm.com, vdonnefort@google.com,
	qperret@google.com, sebastianene@google.com, keirf@google.com,
	smostafa@google.com
Subject: Re: [PATCH v3 9/9] KVM: arm64: Reserve pKVM handle during pkvm_init_host_vm()
Date: Mon, 08 Sep 2025 19:57:53 +0100	[thread overview]
Message-ID: <86qzwgdb66.wl-maz@kernel.org> (raw)
In-Reply-To: <CA+EHjTxMKS=b-yAJWzDN9iOFmdis5PH2P_8q7ejWsDmhpYyxiQ@mail.gmail.com>

On Mon, 08 Sep 2025 19:43:37 +0100,
Fuad Tabba <tabba@google.com> wrote:
> 
> Hi Mark,
> 
> On Mon, 8 Sept 2025 at 17:05, Mark Brown <broonie@kernel.org> wrote:
> >
> > On Wed, Aug 27, 2025 at 11:19:49AM +0100, Fuad Tabba wrote:
> >
> > > When a pKVM guest is active, TLB invalidations triggered by host MMU
> > > notifiers require a valid hypervisor handle. Currently, this handle is
> > > only allocated when the first vCPU is run.
> >
> > I'm seeing the KVM selftests failing in -next on multiple nVHE
> > platforms (pretty sure it's all of them) which bisect down to this
> > commit, when booted in standard nVHE mode the selftests are all failing
> > to initialise with:
> 
> Thanks for pointing this out to me. I think I now know what the issue
> might be, and I'll send out a fix soon.

I'll drop the series from -next until we have clarity on this.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2025-09-08 18:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-27 10:19 [PATCH v3 0/9] KVM: arm64: Reserve pKVM VM handle during initial VM setup Fuad Tabba
2025-08-27 10:19 ` [PATCH v3 1/9] KVM: arm64: Add build-time check for duplicate DECLARE_REG use Fuad Tabba
2025-08-27 10:19 ` [PATCH v3 2/9] KVM: arm64: Rename pkvm.enabled to pkvm.is_protected Fuad Tabba
2025-08-27 10:19 ` [PATCH v3 3/9] KVM: arm64: Rename 'host_kvm' to 'kvm' in pKVM host code Fuad Tabba
2025-08-27 10:19 ` [PATCH v3 4/9] KVM: arm64: Clarify comments to distinguish pKVM mode from protected VMs Fuad Tabba
2025-08-27 10:19 ` [PATCH v3 5/9] KVM: arm64: Decouple hyp VM creation state from its handle Fuad Tabba
2025-08-27 10:19 ` [PATCH v3 6/9] KVM: arm64: Separate allocation and insertion of pKVM VM table entries Fuad Tabba
2025-08-27 10:19 ` [PATCH v3 7/9] KVM: arm64: Consolidate pKVM hypervisor VM initialization logic Fuad Tabba
2025-08-27 10:19 ` [PATCH v3 8/9] KVM: arm64: Introduce separate hypercalls for pKVM VM reservation and initialization Fuad Tabba
2025-08-27 10:19 ` [PATCH v3 9/9] KVM: arm64: Reserve pKVM handle during pkvm_init_host_vm() Fuad Tabba
2025-09-08 16:05   ` Mark Brown
2025-09-08 18:43     ` Fuad Tabba
2025-09-08 18:57       ` Marc Zyngier [this message]
2025-09-08 18:52     ` Mark Brown
2025-09-08 18:54       ` Fuad Tabba

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=86qzwgdb66.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=keirf@google.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=oliver.upton@linux.dev \
    --cc=qperret@google.com \
    --cc=sebastianene@google.com \
    --cc=smostafa@google.com \
    --cc=suzuki.poulose@arm.com \
    --cc=tabba@google.com \
    --cc=vdonnefort@google.com \
    --cc=will@kernel.org \
    --cc=yuzenghui@huawei.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 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.