qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Cédric Le Goater" <clg@redhat.com>
Cc: "BALATON Zoltan" <balaton@eik.bme.hu>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	qemu-devel@nongnu.org,
	"Alex Williamson" <alex.williamson@redhat.com>,
	"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
	"Tony Krowiak" <akrowiak@linux.ibm.com>,
	"Eric Farman" <farman@linux.ibm.com>,
	"Eric Auger" <eric.auger@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 1/2] vfio: Make vfio-pci available on 64-bit host platforms only
Date: Wed, 5 Mar 2025 07:38:43 +0100	[thread overview]
Message-ID: <c37bff90-72f2-4f82-94b0-e2ea63684b35@redhat.com> (raw)
In-Reply-To: <2ccd4a87-68f3-4eb1-bc2a-dbc424bc8d34@linaro.org>

On 03/03/2025 18.32, Philippe Mathieu-Daudé wrote:
> On 3/3/25 17:57, Peter Maydell wrote:
>> On Mon, 3 Mar 2025 at 15:49, Cédric Le Goater <clg@redhat.com> wrote:
>>> Why are we keeping qemu-system-ppc and qemu-system-i386, and arm,
>>> since qemu-system-ppc64 and qemu-system-x86_64 should be able to
>>> run the same machines ?
>>
>> They're not identical -- for example "-cpu max" on
>> qemu-system-arm is a 32-bit CPU but on qemu-system-aarch64
>> it is a 64-bit CPU.
>>
>> There's definitely a lot of overlap but we can't just drop
>> the -arm executable until/unless we figure out what to do
>> about the corner cases where they are different. Plus there's
>> a lot of users out there with existing command lines and
>> configs that assume the existence of a qemu-system-arm
>> executable.
> 
> Thomas and myself have been trying to sort that out. Now with the
> single-binary effort, it gained new interest. This hasn't be a trivial
> task so far, due to as you mentioned the legacy CLI uses and migration.

FWIW, here's my former attempt to see whether we could move into that direction:

  https://lore.kernel.org/qemu-devel/20230425133851.489283-1-thuth@redhat.com/

In the end, it was too frustrating to struggle with the 
backwards-compatibility questions (do we really need to keep 
qemu-system-i386 around forever?), so I pretty much gave up on that patch 
series.

  Thomas



  reply	other threads:[~2025-03-05  6:39 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 [this message]
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 ` [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=c37bff90-72f2-4f82-94b0-e2ea63684b35@redhat.com \
    --to=thuth@redhat.com \
    --cc=akrowiak@linux.ibm.com \
    --cc=alex.bennee@linaro.org \
    --cc=alex.williamson@redhat.com \
    --cc=balaton@eik.bme.hu \
    --cc=berrange@redhat.com \
    --cc=clg@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=farman@linux.ibm.com \
    --cc=harshpb@linux.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --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).