All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Sean Christopherson <seanjc@google.com>
Cc: Sebastian Ott <sebott@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Shuah Khan <shuah@kernel.org>,
	Oliver Upton <oliver.upton@linux.dev>,
	kvm@vger.kernel.org, kvmarm@lists.linux.dev,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: selftests: fix irqfd_test on arm64
Date: Mon, 25 Aug 2025 21:51:02 +0100	[thread overview]
Message-ID: <87zfbnyvk9.wl-maz@kernel.org> (raw)
In-Reply-To: <aKy-9eby1OS38uqM@google.com>

On Mon, 25 Aug 2025 20:52:21 +0100,
Sean Christopherson <seanjc@google.com> wrote:
> 
> On Mon, Aug 25, 2025, Sebastian Ott wrote:
> > irqfd_test on arm triggers the following assertion:
> > ==== Test Assertion Failure ====
> >   include/kvm_util.h:527: !ret
> >   pid=3643 tid=3643 errno=11 - Resource temporarily unavailable
> >      1  0x00000000004026d7: kvm_irqfd at kvm_util.h:527
> >      2  0x0000000000402083: main at irqfd_test.c:100
> >      3  0x0000ffffa5aab587: ?? ??:0
> >      4  0x0000ffffa5aab65f: ?? ??:0
> >      5  0x000000000040236f: _start at ??:?
> >   KVM_IRQFD failed, rc: -1 errno: 11 (Resource temporarily unavailable)
> > 
> > Fix this by setting up a vgic for the vm.
> > 
> > Signed-off-by: Sebastian Ott <sebott@redhat.com>
> > ---
> > @@ -86,14 +90,30 @@ static void juggle_eventfd_primary(struct kvm_vm *vm, int eventfd)
> >  	kvm_irqfd(vm, GSI_BASE_PRIMARY + 1, eventfd, KVM_IRQFD_FLAG_DEASSIGN);
> >  }
> >  
> > +static struct kvm_vm *test_vm_create(void)
> > +{
> > +#ifdef __aarch64__
> > +	struct kvm_vm *vm;
> > +	struct kvm_vcpu *vcpu;
> > +	int gic_fd;
> > +
> > +	vm = vm_create_with_one_vcpu(&vcpu, NULL);
> > +	gic_fd = vgic_v3_setup(vm, 1, 64);
> > +	__TEST_REQUIRE(gic_fd >= 0, "Failed to create vgic-v3");
> 
> I don't think this test requires v3+, any GIC will do.

There is no such thing as "any GIC". You need to know what is
available, and ask for something that actually exists. So while the
above is wrong on the ground that this doesn't work on v2 or v5, the
selection has to be explicit.

> Is there a sane way to handle vGIC creation in kvm_arch_vm_post_create()?  E.g.
> could we create a v3 GIC when possible, and fall back to v2?  And then provide a
> way for tests to express a hard v3 GIC dependency?

You can ask KVM what's available. Like an actual VMM does. There is no
shortage of examples in the current code base.

And ideally, this should be made an integral part of creating a viable
VM, which the current VM creation hack makes a point in not providing.

	M.

-- 
Jazz isn't dead. It just smells funny.

  reply	other threads:[~2025-08-25 20:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 15:52 [PATCH] KVM: selftests: fix irqfd_test on arm64 Sebastian Ott
2025-08-25 19:52 ` Sean Christopherson
2025-08-25 20:51   ` Marc Zyngier [this message]
2025-08-25 21:11     ` Sean Christopherson
2025-08-25 21:38       ` Oliver Upton
2025-08-26 18:51         ` Sean Christopherson
2025-08-26 19:24           ` Oliver Upton
2025-08-26 20:41             ` Sean Christopherson
2025-09-30 15:14               ` Sean Christopherson
2025-09-30 18:26                 ` Oliver Upton
2025-09-30 19:29                   ` Sean Christopherson

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=87zfbnyvk9.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=sebott@redhat.com \
    --cc=shuah@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.