From: Sean Christopherson <seanjc@google.com>
To: sashiko-reviews@lists.linux.dev
Cc: kvm@vger.kernel.org, David Matlack <dmatlack@google.com>,
Josh Hilke <jrhilke@google.com>
Subject: Re: [PATCH v6 01/18] KVM: selftests: Build and link selftests/vfio/lib into KVM selftests
Date: Wed, 10 Jun 2026 12:18:46 -0700 [thread overview]
Message-ID: <aim4lld49oqLrthg@google.com> (raw)
In-Reply-To: <20260610010314.DB8861F00893@smtp.kernel.org>
On Wed, Jun 10, 2026, sashiko-bot@kernel.org wrote:
> > diff --git a/tools/testing/selftests/kvm/Makefile.kvm b/tools/testing/selftests/kvm/Makefile.kvm
> > index e0ddd3ff9472d..14316358fd9fb 100644
> > --- a/tools/testing/selftests/kvm/Makefile.kvm
> > +++ b/tools/testing/selftests/kvm/Makefile.kvm
> > @@ -257,6 +257,7 @@ OVERRIDE_TARGETS = 1
> > # which causes the environment variable to override the makefile).
> > include ../lib.mk
> > include ../cgroup/lib/libcgroup.mk
> > +include ../vfio/lib/libvfio.mk
>
> [Severity: Low]
> Does including libvfio.mk here break the "make clean all" sequence for KVM
> selftests?
David and/or Josh, can you verify whether Sashiko is hallucinating or has a
legitimate concern?
> In tools/testing/selftests/vfio/lib/libvfio.mk, the output directory is
> eagerly created at parse time:
>
> LIBVFIO_O_DIRS := $(shell dirname $(LIBVFIO_O) | uniq)
> $(shell mkdir -p $(LIBVFIO_O_DIRS))
>
> The directory is also added to EXTRA_CLEAN.
>
> If a developer runs "make clean all", Make will parse the included libvfio.mk
> and run the shell mkdir command at parse time. Then it executes the clean
> target, which deletes the newly created libvfio directory. Finally, it
> executes the all target, but the compilation fails with a "No such file or
> directory" error because the output directory was deleted and isn't recreated
> in the build recipe.
>
> >
> > INSTALL_HDR_PATH = $(top_srcdir)/usr
>
> [ ... ]
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260610005338.2967132-1-seanjc@google.com?part=1
next prev parent reply other threads:[~2026-06-10 19:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 0:53 [PATCH v6 00/18] KVM: selftests: Add eventfd+VFIO IRQ test Sean Christopherson
2026-06-10 0:53 ` [PATCH v6 01/18] KVM: selftests: Build and link selftests/vfio/lib into KVM selftests Sean Christopherson
2026-06-10 1:03 ` sashiko-bot
2026-06-10 19:18 ` Sean Christopherson [this message]
2026-06-10 20:14 ` David Matlack
2026-06-10 20:15 ` David Matlack
2026-06-11 0:29 ` Sean Christopherson
2026-06-10 0:53 ` [PATCH v6 02/18] KVM: selftests: Add macros to read/write+sync to/from guest memory Sean Christopherson
2026-06-10 0:53 ` [PATCH v6 03/18] KVM: selftests: Rename guest_rng to kvm_rng Sean Christopherson
2026-06-10 0:53 ` [PATCH v6 04/18] KVM: selftests: Add helper to generate random u64 in range [min,max] Sean Christopherson
2026-06-10 1:01 ` sashiko-bot
2026-06-10 0:53 ` [PATCH v6 05/18] KVM: selftests: Add an irqfd send+receive (and later IRQ bypass) test Sean Christopherson
2026-06-10 1:08 ` sashiko-bot
2026-06-10 19:35 ` Sean Christopherson
2026-06-10 0:53 ` [PATCH v6 06/18] KVM: selftests: Add helper to get host IRQ from device MSI-X for IRQ bypass test Sean Christopherson
2026-06-10 1:01 ` sashiko-bot
2026-06-10 0:53 ` [PATCH v6 07/18] KVM: selftests: Add VFIO device support to eventfd IRQ test Sean Christopherson
2026-06-10 1:05 ` sashiko-bot
2026-06-10 18:06 ` Sean Christopherson
2026-06-10 0:53 ` [PATCH v6 08/18] KVM: selftests: Add a helper to set proc IRQ affinity for " Sean Christopherson
2026-06-10 0:53 ` [PATCH v6 09/18] KVM: selftests: Verify interrupts are received when IRQ affinity changes in " Sean Christopherson
2026-06-10 1:06 ` sashiko-bot
2026-06-10 19:20 ` Sean Christopherson
2026-06-10 0:53 ` [PATCH v6 10/18] KVM: selftests: Add option to set empty routing between IRQs in eventfd " Sean Christopherson
2026-06-10 0:53 ` [PATCH v6 11/18] KVM: selftests: Make number of IRQs configurable in " Sean Christopherson
2026-06-10 0:53 ` [PATCH v6 12/18] KVM: selftests: Verify non-postable IRQ remapping " Sean Christopherson
2026-06-10 0:53 ` [PATCH v6 13/18] KVM: selftests: Add kvm_gettid() wrapper and convert users Sean Christopherson
2026-06-10 0:53 ` [PATCH v6 14/18] KVM: selftests: Add kvm_sched_getaffinity() " Sean Christopherson
2026-06-10 0:53 ` [PATCH v6 15/18] KVM: selftests: Add a utility to pin a task to a random CPU, given a CPU set Sean Christopherson
2026-06-10 0:53 ` [PATCH v6 16/18] KVM: selftests: Verify vCPU migration during IRQ delivery in IRQ test Sean Christopherson
2026-06-10 0:53 ` [PATCH v6 17/18] KVM: selftests: Make number of vCPUs configurable " Sean Christopherson
2026-06-10 0:53 ` [PATCH v6 18/18] KVM: selftests: Add xAPIC support in eventfd " 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=aim4lld49oqLrthg@google.com \
--to=seanjc@google.com \
--cc=dmatlack@google.com \
--cc=jrhilke@google.com \
--cc=kvm@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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