From: Sean Christopherson <seanjc@google.com>
To: David Matlack <dmatlack@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH 0/2] KVM: selftests: Link with VFIO selftests lib and test device interrupts
Date: Mon, 27 Oct 2025 08:47:56 -0700 [thread overview]
Message-ID: <aP-ULL69aQfCOwCb@google.com> (raw)
In-Reply-To: <20250912222525.2515416-1-dmatlack@google.com>
On Fri, Sep 12, 2025, David Matlack wrote:
> This series can be found on GitHub:
>
> https://github.com/dmatlack/linux/tree/kvm/selftests/vfio_pci_irq_test/v1
...
> David Matlack (2):
> KVM: selftests: Build and link sefltests/vfio/lib into KVM selftests
> KVM: selftests: Add a test for vfio-pci device IRQ delivery to vCPUs
>
> tools/testing/selftests/kvm/Makefile.kvm | 6 +-
> .../testing/selftests/kvm/vfio_pci_irq_test.c | 507 ++++++++++++++++++
> 2 files changed, 512 insertions(+), 1 deletion(-)
> create mode 100644 tools/testing/selftests/kvm/vfio_pci_irq_test.c
>
>
> base-commit: 093458c58f830d0a713fab0de037df5f0ce24fef
> prerequisite-patch-id: 72dce9cd586ac36ea378354735d9fabe2f3c445e
> prerequisite-patch-id: a8c7ccfd91ce3208f328e8af7b25c83bff8d464d
Please don't base series on prerequisite patches unless there is a hard dependency.
ffdc6a9d6d9eb20c855404e2c09b6b2ea25b4a04 KVM: selftests: Rename $(ARCH_DIR) to $(SRCARCH)
9dc0c1189dfa1f4eef3856445fa72c9fb1e14d1c Revert "KVM: selftests: Override ARCH for x86_64 instead of using ARCH_DIR"
By all means, do testing on top of such patches if that's what your environment
effectively dictates, but rebase/drop such prereqs before posting, as they add
noise and friction. E.g. these patches don't apply cleanly on kvm-x86/next due
to the prereqs.
next prev parent reply other threads:[~2025-10-27 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 22:25 [PATCH 0/2] KVM: selftests: Link with VFIO selftests lib and test device interrupts David Matlack
2025-09-12 22:25 ` [PATCH 1/2] KVM: selftests: Build and link sefltests/vfio/lib into KVM selftests David Matlack
2025-09-12 22:25 ` [PATCH 2/2] KVM: selftests: Add a test for vfio-pci device IRQ delivery to vCPUs David Matlack
2025-10-27 16:52 ` Sean Christopherson
2025-10-27 17:46 ` David Matlack
2025-10-27 18:50 ` Sean Christopherson
2025-10-27 15:47 ` Sean Christopherson [this message]
2025-10-27 16:03 ` [PATCH 0/2] KVM: selftests: Link with VFIO selftests lib and test device interrupts David Matlack
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=aP-ULL69aQfCOwCb@google.com \
--to=seanjc@google.com \
--cc=alex.williamson@redhat.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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