Re: [PATCH] vfio: selftests: Fix out-of-tree build with make O=

Re: [PATCH] vfio: selftests: Fix out-of-tree build with make O=

[kernel test robot]

:::::: 
:::::: Manual check reason: "low confidence bisect report"
:::::: Manual check reason: "only suspicious fbc files changed"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <0-v1-79f29139180b+8e-vfio_st_make_o_jgg@nvidia.com>
References: <0-v1-79f29139180b+8e-vfio_st_make_o_jgg@nvidia.com>
TO: Jason Gunthorpe <jgg@nvidia.com>
TO: Alex Williamson <alex@shazbot.org>
TO: kvm@vger.kernel.org
TO: linux-kselftest@vger.kernel.org
TO: Shuah Khan <skhan@linuxfoundation.org>
CC: David Matlack <dmatlack@google.com>
CC: patches@lists.linux.dev

Hi Jason,

kernel test robot noticed the following build errors:

[auto build test ERROR on 681b35420592a2e072d9759254185e72d2e914c8]

url:    https://github.com/intel-lab-lkp/linux/commits/Jason-Gunthorpe/vfio-selftests-Fix-out-of-tree-build-with-make-O/20260813-191912
base:   681b35420592a2e072d9759254185e72d2e914c8
patch link:    https://lore.kernel.org/r/0-v1-79f29139180b%2B8e-vfio_st_make_o_jgg%40nvidia.com
patch subject: [PATCH] vfio: selftests: Fix out-of-tree build with make O=
:::::: branch date: 4 days ago
:::::: commit date: 4 days ago
config: arm64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260817/202608171225.NJO5REjA-lkp@intel.com/config)
compiler: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260817/202608171225.NJO5REjA-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202608171225.NJO5REjA-lkp@intel.com/

All errors (new ones prefixed by >>):

   make[1]: *** [../../lib.mk:225: tools/testing/selftests/drivers/net/psp_responder] Error 1
   make[1]: Target 'all' not remade because of errors.
   make[1]: *** [Makefile:124: tools/testing/selftests/hid/host-tools/sbin/bpftool] Error 2
   make[1]: Target 'all' not remade because of errors.
   make[1]: *** No targets.  Stop.
   make[1]: *** [../lib.mk:225: tools/testing/selftests/net/busy_poller] Error 1
   make[1]: *** [../lib.mk:224: tools/testing/selftests/net/tun] Error 1
   make[1]: Target 'all' not remade because of errors.
   make[1]: *** No targets specified and no makefile found.  Stop.
   Makefile:60: warning: overriding recipe for target 'emit_tests'
   ../lib.mk:182: warning: ignoring old recipe for target 'emit_tests'
   make[1]: *** No targets.  Stop.
   make[1]: *** No targets.  Stop.
   make[1]: *** No targets.  Stop.
>> make[1]: *** No rule to make target 'vfio_dma_mapping_test(OUTPUT)/%.o', needed by 'tools/testing/selftests/vfio/vfio_dma_mapping_test'.
>> make[1]: *** No rule to make target 'vfio_dma_mapping_mmio_test(OUTPUT)/%.o', needed by 'tools/testing/selftests/vfio/vfio_dma_mapping_mmio_test'.
>> make[1]: *** No rule to make target 'vfio_iommufd_setup_test(OUTPUT)/%.o', needed by 'tools/testing/selftests/vfio/vfio_iommufd_setup_test'.
>> make[1]: *** No rule to make target 'vfio_pci_device_test(OUTPUT)/%.o', needed by 'tools/testing/selftests/vfio/vfio_pci_device_test'.
>> make[1]: *** No rule to make target 'vfio_pci_device_init_perf_test(OUTPUT)/%.o', needed by 'tools/testing/selftests/vfio/vfio_pci_device_init_perf_test'.
>> make[1]: *** No rule to make target 'vfio_pci_driver_test(OUTPUT)/%.o', needed by 'tools/testing/selftests/vfio/vfio_pci_driver_test'.
   make[1]: Target 'all' not remade because of errors.

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

[PATCH] vfio: selftests: Fix out-of-tree build with make O=

[Jason Gunthorpe]

The test programs are compiled via a static pattern rule that requires
intermediate .o files:

  $(TEST_GEN_PROGS): %: %.o $(LIBVFIO_O)

After lib.mk prefixes TEST_GEN_PROGS with $(OUTPUT), this creates
dependencies on .o files in the output directory (e.g.
$(OUTPUT)/vfio_dma_mapping_test.o). However, there is no rule to compile
these .o files from the source directory .c files when OUTPUT differs
from the source directory.

Add an explicit chain of pattern rules:
  $(OUTPUT)/% -> $(OUTPUT)/%.o -> %.c

Following the same pattern already used in libvfio.mk for the library
objects.

Fixes: 19faf6fd969c ("vfio: selftests: Add a helper library for VFIO selftests")
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
---
 tools/testing/selftests/vfio/Makefile | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/tools/testing/selftests/vfio/Makefile b/tools/testing/selftests/vfio/Makefile
index 40165d087a0bc4..81c3be8298fdc2 100644
--- a/tools/testing/selftests/vfio/Makefile
+++ b/tools/testing/selftests/vfio/Makefile
@@ -27,10 +27,13 @@ CFLAGS += $(EXTRA_CFLAGS)
 
 LDFLAGS += -pthread
 
-$(TEST_GEN_PROGS): %: %.o $(LIBVFIO_O)
+$(TEST_GEN_PROGS): $(OUTPUT)/%: %(OUTPUT)/%.o $(LIBVFIO_O)
 	$(CC) $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) $< $(LIBVFIO_O) $(LDLIBS) -o $@
 
 TEST_GEN_PROGS_O = $(patsubst %, %.o, $(TEST_GEN_PROGS))
+$(TEST_GEN_PROGS_O): $(OUTPUT)/%.o: %.c
+	$(CC) $(CFLAGS) $(CPPFLAGS) $(TARGET_ARCH) -c $< -o $@
+
 TEST_DEP_FILES = $(patsubst %.o, %.d, $(TEST_GEN_PROGS_O) $(LIBVFIO_O))
 -include $(TEST_DEP_FILES)
 

base-commit: 681b35420592a2e072d9759254185e72d2e914c8
-- 
2.43.0

Re: [PATCH] vfio: selftests: Fix out-of-tree build with make O=

[Jason Gunthorpe]

On Mon, Apr 27, 2026 at 08:07:37PM -0300, Jason Gunthorpe wrote:
> -$(TEST_GEN_PROGS): %: %.o $(LIBVFIO_O)
> +$(TEST_GEN_PROGS): $(OUTPUT)/%: %(OUTPUT)/%.o $(LIBVFIO_O)

I grabbed the wrong version of this, it should be:
                                  v
 +$(TEST_GEN_PROGS): $(OUTPUT)/%: $(OUTPUT)/%.o $(LIBVFIO_O)

Sorry,
Jason

Re: [PATCH] vfio: selftests: Fix out-of-tree build with make O=

[David Matlack]

On 2026-04-27 08:07 PM, Jason Gunthorpe wrote:
> The test programs are compiled via a static pattern rule that requires
> intermediate .o files:
> 
>   $(TEST_GEN_PROGS): %: %.o $(LIBVFIO_O)
> 
> After lib.mk prefixes TEST_GEN_PROGS with $(OUTPUT), this creates
> dependencies on .o files in the output directory (e.g.
> $(OUTPUT)/vfio_dma_mapping_test.o). However, there is no rule to compile
> these .o files from the source directory .c files when OUTPUT differs
> from the source directory.
> 
> Add an explicit chain of pattern rules:
>   $(OUTPUT)/% -> $(OUTPUT)/%.o -> %.c
> 
> Following the same pattern already used in libvfio.mk for the library
> objects.
> 
> Fixes: 19faf6fd969c ("vfio: selftests: Add a helper library for VFIO selftests")
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> ---
>  tools/testing/selftests/vfio/Makefile | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/vfio/Makefile b/tools/testing/selftests/vfio/Makefile
> index 40165d087a0bc4..81c3be8298fdc2 100644
> --- a/tools/testing/selftests/vfio/Makefile
> +++ b/tools/testing/selftests/vfio/Makefile
> @@ -27,10 +27,13 @@ CFLAGS += $(EXTRA_CFLAGS)
>  
>  LDFLAGS += -pthread
>  
> -$(TEST_GEN_PROGS): %: %.o $(LIBVFIO_O)
> +$(TEST_GEN_PROGS): $(OUTPUT)/%: %(OUTPUT)/%.o $(LIBVFIO_O)

Changing this line (with the fix you replied with) is not actually
needed right? I tried the following without it and was able to build:

  $ make OUTPUT=/tmp -C tools/testing/selftests/vfio

$(TEST_GEN_PROGS) has already been prefixed with $(OUTPUT), so %
in the original pattern already included $(OUTPUT).

Is this for readability?

>  	$(CC) $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) $< $(LIBVFIO_O) $(LDLIBS) -o $@
>  
>  TEST_GEN_PROGS_O = $(patsubst %, %.o, $(TEST_GEN_PROGS))
> +$(TEST_GEN_PROGS_O): $(OUTPUT)/%.o: %.c
> +	$(CC) $(CFLAGS) $(CPPFLAGS) $(TARGET_ARCH) -c $< -o $@

Looking at this commit made me confused how this was even working before
and I learned that make has built-in rules to build .o files that
assumes the .c is in the same directory. I see now that we were reying
on those built-in rules to build $(TEST_GEN_PROGS_O). It makes sense to
have an explicit rule to handle the directory mismatch between .c and
.o.

This also got me thinking it might be a nice cleanup to use the
predefined macros $(COMPILE.c) and $(LINK.c) in these rules instead of
$(CC) $(CFLAGS) ... etc. No need to attach that to this fix though.

> +
>  TEST_DEP_FILES = $(patsubst %.o, %.d, $(TEST_GEN_PROGS_O) $(LIBVFIO_O))
>  -include $(TEST_DEP_FILES)
>  
> 
> base-commit: 681b35420592a2e072d9759254185e72d2e914c8
> -- 
> 2.43.0
> 

Re: [PATCH] vfio: selftests: Fix out-of-tree build with make O=

[Jason Gunthorpe]

On Tue, Apr 28, 2026 at 06:27:06PM +0000, David Matlack wrote:
> On 2026-04-27 08:07 PM, Jason Gunthorpe wrote:
> > The test programs are compiled via a static pattern rule that requires
> > intermediate .o files:
> > 
> >   $(TEST_GEN_PROGS): %: %.o $(LIBVFIO_O)
> > 
> > After lib.mk prefixes TEST_GEN_PROGS with $(OUTPUT), this creates
> > dependencies on .o files in the output directory (e.g.
> > $(OUTPUT)/vfio_dma_mapping_test.o). However, there is no rule to compile
> > these .o files from the source directory .c files when OUTPUT differs
> > from the source directory.
> > 
> > Add an explicit chain of pattern rules:
> >   $(OUTPUT)/% -> $(OUTPUT)/%.o -> %.c
> > 
> > Following the same pattern already used in libvfio.mk for the library
> > objects.
> > 
> > Fixes: 19faf6fd969c ("vfio: selftests: Add a helper library for VFIO selftests")
> > Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> > ---
> >  tools/testing/selftests/vfio/Makefile | 5 ++++-
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> > 
> > diff --git a/tools/testing/selftests/vfio/Makefile b/tools/testing/selftests/vfio/Makefile
> > index 40165d087a0bc4..81c3be8298fdc2 100644
> > --- a/tools/testing/selftests/vfio/Makefile
> > +++ b/tools/testing/selftests/vfio/Makefile
> > @@ -27,10 +27,13 @@ CFLAGS += $(EXTRA_CFLAGS)
> >  
> >  LDFLAGS += -pthread
> >  
> > -$(TEST_GEN_PROGS): %: %.o $(LIBVFIO_O)
> > +$(TEST_GEN_PROGS): $(OUTPUT)/%: %(OUTPUT)/%.o $(LIBVFIO_O)
> 
> Changing this line (with the fix you replied with) is not actually
> needed right? I tried the following without it and was able to build:
> 
>   $ make OUTPUT=/tmp -C tools/testing/selftests/vfio
> 
> $(TEST_GEN_PROGS) has already been prefixed with $(OUTPUT), so %
> in the original pattern already included $(OUTPUT).
> 
> Is this for readability?

Yes, it makes more sense to explicitly match the stems through the
flow than to have the implicit $(TEST_GEN_PROGS) == XXX/$(OUTPUT)

> >  	$(CC) $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) $< $(LIBVFIO_O) $(LDLIBS) -o $@
> >  
> >  TEST_GEN_PROGS_O = $(patsubst %, %.o, $(TEST_GEN_PROGS))
> > +$(TEST_GEN_PROGS_O): $(OUTPUT)/%.o: %.c
> > +	$(CC) $(CFLAGS) $(CPPFLAGS) $(TARGET_ARCH) -c $< -o $@
> 
> Looking at this commit made me confused how this was even working before
> and I learned that make has built-in rules to build .o files that
> assumes the .c is in the same directory. 

Yes

> I see now that we were reying
> on those built-in rules to build $(TEST_GEN_PROGS_O). It makes sense to
> have an explicit rule to handle the directory mismatch between .c and
> .o.

Hmm now that I think about it, I wonder if it used the right flags..

> This also got me thinking it might be a nice cleanup to use the
> predefined macros $(COMPILE.c) and $(LINK.c) in these rules instead of
> $(CC) $(CFLAGS) ... etc. No need to attach that to this fix though.

Yeah probably

Jason

Re: [PATCH] vfio: selftests: Fix out-of-tree build with make O=

[David Matlack]

On 2026-04-28 04:04 PM, Jason Gunthorpe wrote:
> On Tue, Apr 28, 2026 at 06:27:06PM +0000, David Matlack wrote:
> > On 2026-04-27 08:07 PM, Jason Gunthorpe wrote:
> > > The test programs are compiled via a static pattern rule that requires
> > > intermediate .o files:
> > > 
> > >   $(TEST_GEN_PROGS): %: %.o $(LIBVFIO_O)
> > > 
> > > After lib.mk prefixes TEST_GEN_PROGS with $(OUTPUT), this creates
> > > dependencies on .o files in the output directory (e.g.
> > > $(OUTPUT)/vfio_dma_mapping_test.o). However, there is no rule to compile
> > > these .o files from the source directory .c files when OUTPUT differs
> > > from the source directory.
> > > 
> > > Add an explicit chain of pattern rules:
> > >   $(OUTPUT)/% -> $(OUTPUT)/%.o -> %.c
> > > 
> > > Following the same pattern already used in libvfio.mk for the library
> > > objects.
> > > 
> > > Fixes: 19faf6fd969c ("vfio: selftests: Add a helper library for VFIO selftests")
> > > Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>

With the fix applied from your reply,

Reviewed-by: David Matlack <dmatlack@google.com>

> > > ---
> > >  tools/testing/selftests/vfio/Makefile | 5 ++++-
> > >  1 file changed, 4 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/tools/testing/selftests/vfio/Makefile b/tools/testing/selftests/vfio/Makefile
> > > index 40165d087a0bc4..81c3be8298fdc2 100644
> > > --- a/tools/testing/selftests/vfio/Makefile
> > > +++ b/tools/testing/selftests/vfio/Makefile
> > > @@ -27,10 +27,13 @@ CFLAGS += $(EXTRA_CFLAGS)
> > >  
> > >  LDFLAGS += -pthread
> > >  
> > > -$(TEST_GEN_PROGS): %: %.o $(LIBVFIO_O)
> > > +$(TEST_GEN_PROGS): $(OUTPUT)/%: %(OUTPUT)/%.o $(LIBVFIO_O)
> > 
> > Changing this line (with the fix you replied with) is not actually
> > needed right? I tried the following without it and was able to build:
> > 
> >   $ make OUTPUT=/tmp -C tools/testing/selftests/vfio
> > 
> > $(TEST_GEN_PROGS) has already been prefixed with $(OUTPUT), so %
> > in the original pattern already included $(OUTPUT).
> > 
> > Is this for readability?
> 
> Yes, it makes more sense to explicitly match the stems through the
> flow than to have the implicit $(TEST_GEN_PROGS) == XXX/$(OUTPUT)

Sounds good.

> 
> > >  	$(CC) $(CFLAGS) $(CPPFLAGS) $(LDFLAGS) $< $(LIBVFIO_O) $(LDLIBS) -o $@
> > >  
> > >  TEST_GEN_PROGS_O = $(patsubst %, %.o, $(TEST_GEN_PROGS))
> > > +$(TEST_GEN_PROGS_O): $(OUTPUT)/%.o: %.c
> > > +	$(CC) $(CFLAGS) $(CPPFLAGS) $(TARGET_ARCH) -c $< -o $@
> > 
> > Looking at this commit made me confused how this was even working before
> > and I learned that make has built-in rules to build .o files that
> > assumes the .c is in the same directory. 
> 
> Yes
> 
> > I see now that we were reying
> > on those built-in rules to build $(TEST_GEN_PROGS_O). It makes sense to
> > have an explicit rule to handle the directory mismatch between .c and
> > .o.
> 
> Hmm now that I think about it, I wonder if it used the right flags..

It looks like it used the same command that we will be using after this
patch, just with the wrong path to the .c file.

 $ make -p -f /dev/null
 ...
 COMPILE.c = $(CC) $(CFLAGS) $(CPPFLAGS) $(TARGET_ARCH) -c
 ...
 OUTPUT_OPTION = -o $@
 ...
  %.o: %.c
  #  recipe to execute (built-in):
          $(COMPILE.c) $(OUTPUT_OPTION) $<