Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Alex Williamson <alex@shazbot.org>
To: David Matlack <dmatlack@google.com>
Cc: Sean Christopherson <seanjc@google.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Raghavendra Rao Ananta <rananta@google.com>,
	Vipin Sharma <vipinsh@google.com>,
	alex@shazbot.org
Subject: Re: [PATCH] vfio: selftests: Add luuid to libvfio.mk's list of libraries, not to the Makefile
Date: Tue, 30 Jun 2026 15:50:23 -0600	[thread overview]
Message-ID: <20260630155023.2ffb3226@shazbot.org> (raw)
In-Reply-To: <akQ4p3sPdNzSnAc9@google.com>

On Tue, 30 Jun 2026 21:44:07 +0000
David Matlack <dmatlack@google.com> wrote:

> On 2026-06-30 02:28 PM, Sean Christopherson wrote:
> > Link to the uuid library as part of libvfio.mk instead of as only linking
> > it via VFIO selftests' Makefile, as the whole point of providing libvfio.mk
> > is to allow linking the VFIO library functionality into KVM selftests,
> > without KVM selftests having to know the gory details or duplicate code.
> > 
> > Cc: Raghavendra Rao Ananta <rananta@google.com>
> > Cc: David Matlack <dmatlack@google.com>
> > Cc: Vipin Sharma <vipinsh@google.com>
> > Cc: Alex Williamson <alex@shazbot.org>
> > Fixes: e65f1bf8a2db ("vfio: selftests: Extend container/iommufd setup for passing vf_token")
> > Signed-off-by: Sean Christopherson <seanjc@google.com>  
> 
> Reviewed-by: David Matlack <dmatlack@google.com>
> 
> > ---
> > 
> > I would either like to land this in 7.2-rcN (ideally rc2 or rc3), or take it
> > through the KVM x86 tree for 7.3, as it's blocking a KVM selftest[*] that's
> > been in the works for more than a year.  I can throw the IRQ selftest in its
> > own topic branch, so even 7.2-rc5 would be "fine", but I would much prefer to
> > get this (or an equivalent fix) into Linus' tree sooner than later.
> > 
> > [*] https://lore.kernel.org/all/20260626213534.3866178-1-seanjc@google.com  
> 
> Sounds good to me. Alex can we take this in one of the next RCs?

I'm intending a pull request this week with the bitfield and module
option latching fixes that are currently in linux-next, I'll pull this
into that as well.  Thanks,

Alex

      reply	other threads:[~2026-06-30 21:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 21:28 [PATCH] vfio: selftests: Add luuid to libvfio.mk's list of libraries, not to the Makefile Sean Christopherson
2026-06-30 21:44 ` David Matlack
2026-06-30 21:50   ` Alex Williamson [this message]

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=20260630155023.2ffb3226@shazbot.org \
    --to=alex@shazbot.org \
    --cc=dmatlack@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rananta@google.com \
    --cc=seanjc@google.com \
    --cc=vipinsh@google.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