From: Sean Christopherson <seanjc@google.com>
To: Marc Zyngier <maz@kernel.org>
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 14:11:30 -0700 [thread overview]
Message-ID: <aKzRgp58vU6h02n6@google.com> (raw)
In-Reply-To: <87zfbnyvk9.wl-maz@kernel.org>
On Mon, Aug 25, 2025, Marc Zyngier wrote:
> On Mon, 25 Aug 2025 20:52:21 +0100,
> Sean Christopherson <seanjc@google.com> wrote:
> > 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.
Right, by "sane" I meant: is there a way to instantiate a supported GIC without
making it hard/painful to write tests, and without having to plumb in arm64
specific requirements to common APIs?
E.g. are there tests that use the common vm_create() APIs and rely on NOT having
a GIC?
> 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.
next prev parent reply other threads:[~2025-08-25 21:11 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
2025-08-25 21:11 ` Sean Christopherson [this message]
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=aKzRgp58vU6h02n6@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.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.