All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex@shazbot.org>
To: Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>
Cc: qemu-devel@nongnu.org, mjt@tls.msk.ru,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Cédric Le Goater" <clg@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@mailo.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	alex@shazbot.org
Subject: Re: [PATCH 0/2] build: fix sparc64 host
Date: Mon, 20 Jul 2026 17:10:31 -0600	[thread overview]
Message-ID: <20260720171031.259f590e@shazbot.org> (raw)
In-Reply-To: <20260720221715.27108-1-pierrick.bouvier@oss.qualcomm.com>

On Mon, 20 Jul 2026 22:17:13 +0000
Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com> wrote:

> It was reported that build on sparc64 host is currently broken, due to inclusion
> of asm/kvm.h, which is not present on this platform:
> https://lore.kernel.org/qemu-devel/c3a7cd83-7666-40c5-9baa-ebe64edacab6@tls.msk.ru/

Isn't is sufficient just to remove the stale <linux/kvm.h> include?

I don't know of a case that fails, platforms that support vfio might
actually be a sub-set of those that support KVM, but being dependent on
a KVM supported host has no technical basis.  KVM and VFIO are
independent features where neither should have a hard dependency on the
other.  Thanks,

Alex

> Problem is that we assumed in Kconfig that VFIO is available for all linux
> hosts, which is wrong. It is limited to linux hosts having kvm support.
> Since we already have a meson.build section identifying those hosts, just define
> a new CONFIG_KVM_HOST in host configuration.
> 
> Pierrick Bouvier (2):
>   meson.build: define CONFIG_KVM_HOST
>   hw/vfio: restrict to kvm hosts
> 
>  Kconfig.host    | 3 +++
>  hw/vfio/Kconfig | 8 ++++----
>  meson.build     | 4 ++++
>  3 files changed, 11 insertions(+), 4 deletions(-)
> 



  parent reply	other threads:[~2026-07-20 23:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 22:17 [PATCH 0/2] build: fix sparc64 host Pierrick Bouvier
2026-07-20 22:17 ` [PATCH 1/2] meson.build: define CONFIG_KVM_HOST Pierrick Bouvier
2026-07-20 22:17 ` [PATCH 2/2] hw/vfio: restrict to kvm hosts Pierrick Bouvier
2026-07-20 23:10 ` Alex Williamson [this message]
2026-07-21  2:48   ` [PATCH 0/2] build: fix sparc64 host Pierrick Bouvier
2026-07-21  3:33     ` Alex Williamson
2026-07-21  5:14       ` Cédric Le Goater
2026-07-21  5:17         ` Pierrick Bouvier
2026-07-21  6:27           ` Cédric Le Goater
2026-07-21  7:42       ` Michael Tokarev
2026-07-21  9:58         ` Michael Tokarev

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=20260720171031.259f590e@shazbot.org \
    --to=alex@shazbot.org \
    --cc=berrange@redhat.com \
    --cc=clg@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=pbonzini@redhat.com \
    --cc=philmd@mailo.com \
    --cc=pierrick.bouvier@oss.qualcomm.com \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.