qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Cédric Le Goater" <clg@redhat.com>
Cc: qemu-devel@nongnu.org, Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH 0/2] vfio: Restrict to 64-bit host platforms
Date: Wed, 26 Feb 2025 14:01:39 +0000	[thread overview]
Message-ID: <Z78ew0NSNMNmcM0W@redhat.com> (raw)
In-Reply-To: <20250226084721.232703-1-clg@redhat.com>

On Wed, Feb 26, 2025 at 09:47:19AM +0100, Cédric Le Goater wrote:
> Hello,
> 
> This series avoids compiling VFIO on 32-bit host platforms where it is
> not needed.

If it was previously enabled on 32-bit and was possible to successfully
build & use, then it needs to go through the deprecation process - we
can't just rip out features with no prior warning.

In any case this recently merged:

  commit 6d701c9bac1d3571e9ad511e01b27df7237f0b13
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   Mon Jan 27 16:22:24 2025 -0800

    meson: Deprecate 32-bit host support
    
    We deprecated i686 system mode support for qemu 8.0.  However, to
    make real cleanups to TCG we need to deprecate all 32-bit hosts.

so 32-bit host support in general is nearing end of life. Given that,
I don't think we need to further limit 32-bit host for individual
features, just let it die all at once.


With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  parent reply	other threads:[~2025-02-26 14:02 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
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 ` Daniel P. Berrangé [this message]
2025-02-26 15:49   ` [PATCH 0/2] vfio: Restrict to 64-bit host platforms 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=Z78ew0NSNMNmcM0W@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=clg@redhat.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 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).