qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Auger <eric.auger@redhat.com>
To: "Cédric Le Goater" <clg@redhat.com>,
	qemu-devel@nongnu.org, "Will Deacon" <will@kernel.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Marc Zyngier" <maz@kernel.org>,
	"Peter Maydell" <peter.maydell@linaro.org>
Cc: Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH 2/2] vfio: Make vfio-platform available on Aarch64 platforms only
Date: Thu, 27 Feb 2025 09:32:46 +0100	[thread overview]
Message-ID: <291bf12d-18bc-444f-b09d-3fb80e0f144a@redhat.com> (raw)
In-Reply-To: <20250226084721.232703-3-clg@redhat.com>

Hi Cédric,

On 2/26/25 9:47 AM, Cédric Le Goater wrote:
> VFIO Platforms was designed for Aarch64. Restrict availability to
> 64-bit host platforms.
>
> Cc: Eric Auger <eric.auger@redhat.com>
> Signed-off-by: Cédric Le Goater <clg@redhat.com>
Reviewed-by: Eric Auger <eric.auger@redhat.com>

As an outcome from last KVM forum, next step may be to simply remove
VFIO_PLATFORM from the qemu tree.

We also need to make a decision wrt linux vfio platform driver. As I
can't test it anymore without hacks (my last tegra234 mgbe works are
unlikely to land on qemu side and lack traction on kernel side too),
either someone who can test it volunteers to take over the kernel
maintainership or we remove it from kernel too.

Taking this opportunity to add Will, Marc, Peter in CC

Thanks

Eric
> ---
>  hw/vfio/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/vfio/Kconfig b/hw/vfio/Kconfig
> index 6ed825429a9151fcdff33e95d1a310210689b258..885630e8d30c656500fcd7dbb3f26a4c0113a17a 100644
> --- a/hw/vfio/Kconfig
> +++ b/hw/vfio/Kconfig
> @@ -19,7 +19,7 @@ config VFIO_PLATFORM
>      bool
>      default y
>      select VFIO
> -    depends on LINUX && PLATFORM_BUS
> +    depends on LINUX && PLATFORM_BUS && AARCH64
>  
>  config VFIO_XGMAC
>      bool



  reply	other threads:[~2025-02-27  8:33 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26  8:47 [PATCH 0/2] vfio: Restrict to 64-bit host platforms Cédric Le Goater
2025-02-26  8:47 ` [PATCH 1/2] vfio: Make vfio-pci available on 64-bit host platforms only Cédric Le Goater
2025-02-26 14:12   ` BALATON Zoltan
2025-02-26 16:26     ` Cédric Le Goater
2025-02-26 17:57       ` BALATON Zoltan
2025-03-03 14:30         ` Philippe Mathieu-Daudé
2025-03-03 14:45           ` BALATON Zoltan
2025-03-03 14:46           ` Paolo Bonzini
2025-03-03 15:05             ` Cédric Le Goater
2025-03-03 15:26               ` BALATON Zoltan
2025-03-03 15:48                 ` Cédric Le Goater
2025-03-03 16:04                   ` Cédric Le Goater
2025-03-03 16:57                   ` Peter Maydell
2025-03-03 17:32                     ` Philippe Mathieu-Daudé
2025-03-05  6:38                       ` Thomas Huth
2025-03-05 13:21                         ` BALATON Zoltan
2025-03-03 17:34                     ` Cédric Le Goater
2025-03-03 16:50               ` Paolo Bonzini
2025-03-03 17:32                 ` Cédric Le Goater
2025-03-03 18:11         ` Cédric Le Goater
2025-03-03 14:43       ` Paolo Bonzini
2025-03-03 14:53         ` Philippe Mathieu-Daudé
2025-03-03 16:51           ` Daniel P. Berrangé
2025-03-03 15:07         ` Cédric Le Goater
2025-02-26  8:47 ` [PATCH 2/2] vfio: Make vfio-platform available on Aarch64 " Cédric Le Goater
2025-02-27  8:32   ` Eric Auger [this message]
2025-02-27 17:27     ` Alex Williamson
2025-03-03 14:32       ` Philippe Mathieu-Daudé
2025-03-03 18:07         ` Eric Auger
2025-02-26 14:01 ` [PATCH 0/2] vfio: Restrict to 64-bit host platforms Daniel P. Berrangé
2025-02-26 15:49   ` Cédric Le Goater

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=291bf12d-18bc-444f-b09d-3fb80e0f144a@redhat.com \
    --to=eric.auger@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=clg@redhat.com \
    --cc=maz@kernel.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=will@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).