Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: Marc Zyngier <maz@kernel.org>
Cc: kvmarm@lists.linux.dev, Joey Gouly <joey.gouly@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>,
	Jiaqi Yan <jiaqiyan@google.com>
Subject: Re: [PATCH] KVM: arm64: nv: Handle SEAs due to VNCR redirection
Date: Wed, 30 Jul 2025 10:34:21 -0700	[thread overview]
Message-ID: <aIpXnURI112162jC@linux.dev> (raw)
In-Reply-To: <8634ae80lx.wl-maz@kernel.org>

On Wed, Jul 30, 2025 at 10:54:50AM +0100, Marc Zyngier wrote:
> > diff --git a/arch/arm64/kvm/nested.c b/arch/arm64/kvm/nested.c
> > index efb37aad11ec..4f741ba24b48 100644
> > --- a/arch/arm64/kvm/nested.c
> > +++ b/arch/arm64/kvm/nested.c
> > @@ -1289,6 +1289,9 @@ int kvm_handle_vncr_abort(struct kvm_vcpu *vcpu)
> >  
> >  	BUG_ON(!(esr & ESR_ELx_VNCR_SHIFT));
> 
> Urgh. This is hilarious. We don't trigger this thing by pure luck (13
> is a lucky number, apparently...). I'll post a separate fix for that.

LOL! I totally missed this when I wrote the patch. I'll grab your fix,
thx for posting.

> >  
> > +	if (kvm_vcpu_abt_issea(vcpu))
> > +		return kvm_handle_guest_sea(vcpu);
> > +
> >  	if (esr_fsc_is_permission_fault(esr)) {
> >  		inject_vncr_perm(vcpu);
> >  	} else if (esr_fsc_is_translation_fault(esr)) {
> > 
> 
> Reviewed-by: Marc Zyngier <maz@kernel.org>

Appreciated :)

Thanks,
Oliver

  reply	other threads:[~2025-07-30 17:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-29 18:23 [PATCH] KVM: arm64: nv: Handle SEAs due to VNCR redirection Oliver Upton
2025-07-30  9:54 ` Marc Zyngier
2025-07-30 17:34   ` Oliver Upton [this message]
2025-08-08 17:51 ` Oliver Upton

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=aIpXnURI112162jC@linux.dev \
    --to=oliver.upton@linux.dev \
    --cc=jiaqiyan@google.com \
    --cc=joey.gouly@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=maz@kernel.org \
    --cc=suzuki.poulose@arm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox