linux-kernel - Re: [PATCH] vfio: selftests: Store libvfio build outputs in $(OUTPUT)/libvfio

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20251106213422.1632efef.alex@shazbot.org>
Date: Thu, 6 Nov 2025 21:34:22 -0700
From: Alex Williamson <alex@...zbot.org>
To: David Matlack <dmatlack@...gle.com>
Cc: Alex Williamson <alex.williamson@...hat.com>, Dave Jiang
 <dave.jiang@...el.com>, kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-kselftest@...r.kernel.org, Shuah Khan <shuah@...nel.org>, Vinicius
 Costa Gomes <vinicius.gomes@...el.com>
Subject: Re: [PATCH] vfio: selftests: Store libvfio build outputs in
 $(OUTPUT)/libvfio

On Mon, 22 Sep 2025 22:48:57 +0000
David Matlack <dmatlack@...gle.com> wrote:

> Store the tools/testing/selftests/vfio/lib outputs (e.g. object files)
> in $(OUTPUT)/libvfio rather than in $(OUTPUT)/lib. This is in
> preparation for building the VFIO selftests library into the KVM
> selftests (see Link below).
> 
> Specifically this will avoid name conflicts between
> tools/testing/selftests/{vfio,kvm/lib and also avoid leaving behind
> empty directories under tools/testing/selftests/kvm after a make clean.
> 
> Link: https://lore.kernel.org/kvm/20250912222525.2515416-2-dmatlack@google.com/
> Signed-off-by: David Matlack <dmatlack@...gle.com>
> ---
> 
> Note: This patch applies on top of vfio/next.
> 
> https://github.com/awilliam/linux-vfio/tree/next
> 
>  tools/testing/selftests/vfio/lib/libvfio.mk | 20 +++++++++++---------
>  1 file changed, 11 insertions(+), 9 deletions(-)

Applied to vfio next branch for v6.19.  Thanks,

Alex