From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-arm@nongnu.org, "Maxim Levitsky" <mlevitsk@redhat.com>,
libvir-list@redhat.com,
"Richard Henderson" <richard.henderson@linaro.org>,
xen-devel@lists.xenproject.org,
"Reinoud Zandijk" <reinoud@netbsd.org>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>
Subject: Re: [PATCH 1/2] docs/about: Deprecate 32-bit x86 hosts and qemu-system-i386
Date: Tue, 28 Feb 2023 08:59:52 +0000 [thread overview]
Message-ID: <Y/3CiEKKoG06t9rr@redhat.com> (raw)
In-Reply-To: <20230228031026-mutt-send-email-mst@kernel.org>
On Tue, Feb 28, 2023 at 03:19:20AM -0500, Michael S. Tsirkin wrote:
> On Tue, Feb 28, 2023 at 08:49:09AM +0100, Thomas Huth wrote:
> > On 27/02/2023 21.12, Michael S. Tsirkin wrote:
> > > On Mon, Feb 27, 2023 at 11:50:07AM +0000, Daniel P. Berrangé wrote:
> > > > I feel like we should have separate deprecation entries for the
> > > > i686 host support, and for qemu-system-i386 emulator binary, as
> > > > although they're related they are independant features with
> > > > differing impact. eg removing qemu-system-i386 affects all
> > > > host architectures, not merely 32-bit x86 host, so I think we
> > > > can explain the impact more clearly if we separate them.
> > >
> > > Removing qemu-system-i386 seems ok to me - I think qemu-system-x86_64 is
> > > a superset.
> > >
> > > Removing support for building on 32 bit systems seems like a pity - it's
> > > one of a small number of ways to run 64 bit binaries on 32 bit systems,
> > > and the maintainance overhead is quite small.
> >
> > Note: We're talking about 32-bit *x86* hosts here. Do you really think that
> > someone is still using QEMU usermode emulation
> > to run 64-bit binaries on a 32-bit x86 host?? ... If so, I'd be very surprised!
>
> I don't know - why x86 specifically? One can build a 32 bit binary on any host.
> I think 32 bit x86 environments are just more common in the cloud.
Can you point to anything that backs up that assertion. Clouds I've
seen always give you a 64-bit environment, and many OS no longer
even ship 32-bit installable media. I would be surprised if 32-bit
is above very very low single digits usage compared to x86_64.
> > > In fact, keeping this support around forces correct use of
> > > posix APIs such as e.g. PRIx64 which makes the code base
> > > more future-proof.
> >
> > If you're concerned about PRIx64 and friends: We still continue to do
> > compile testing with 32-bit MIPS cross-compilers and Windows 32-bit
> > cross-compilers for now. The only thing we'd lose is the 32-bit "make check"
> > run in the CI.
> >
> > Thomas
>
> Yes - fundamentally 32 bit does not seem that different from e.g.
> windows builds - we presumably support these but AFAIK CI does not
> test these.
We do compile test windows in CI via mingw, and we also do build
and unit tests via msys.
Even Windows has dropped 32-bit support though, and so the only
reason we keep 32-bit Windows around is because of Windows 10.
Once a Windows 12 comes along, we'll not need to support 32-bit
Windows either.
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 :|
next prev parent reply other threads:[~2023-02-28 9:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 11:10 [PATCH 0/2] Deprecate support for 32-bit x86 and arm hosts Thomas Huth
2023-02-27 11:10 ` [PATCH 1/2] docs/about: Deprecate 32-bit x86 hosts and qemu-system-i386 Thomas Huth
2023-02-27 11:50 ` Daniel P. Berrangé
2023-02-27 20:12 ` Michael S. Tsirkin
2023-02-27 20:21 ` Richard Henderson
2023-02-28 8:59 ` Michael S. Tsirkin
2023-02-28 12:26 ` Philippe Mathieu-Daudé
2023-02-28 9:00 ` Michael S. Tsirkin
2023-02-28 16:57 ` Richard Henderson
2023-02-27 22:32 ` Philippe Mathieu-Daudé
2023-02-28 7:43 ` Thomas Huth
2023-02-28 7:49 ` Thomas Huth
2023-02-28 8:19 ` Michael S. Tsirkin
2023-02-28 8:59 ` Daniel P. Berrangé [this message]
2023-02-28 9:03 ` Michael S. Tsirkin
2023-02-28 9:14 ` Thomas Huth
2023-02-28 9:40 ` Daniel P. Berrangé
2023-02-28 10:11 ` Michael S. Tsirkin
2023-02-28 10:39 ` Markus Armbruster
2023-02-28 10:51 ` Michael S. Tsirkin
2023-02-28 11:12 ` Thomas Huth
2023-02-28 11:24 ` Michael S. Tsirkin
2023-02-28 11:27 ` Daniel P. Berrangé
2023-02-28 11:34 ` Markus Armbruster
2023-02-28 11:45 ` Michael S. Tsirkin
2023-02-27 20:25 ` Richard Henderson
2023-02-28 7:52 ` Thomas Huth
2023-02-27 11:10 ` [PATCH 2/2] docs/about: Deprecate 32-bit arm hosts and qemu-system-arm Thomas Huth
2023-02-27 18:38 ` [PATCH 0/2] Deprecate support for 32-bit x86 and arm hosts Daniel P. Berrangé
2023-02-28 7:39 ` Thomas Huth
2023-02-28 9:01 ` Daniel P. Berrangé
2023-02-28 11:46 ` Michael S. Tsirkin
2023-02-28 20:05 ` Thomas Huth
2023-02-28 21:32 ` Michael S. Tsirkin
2023-03-01 6:38 ` Thomas Huth
2023-03-01 7:35 ` Markus Armbruster
2023-03-01 7:46 ` Warner Losh
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=Y/3CiEKKoG06t9rr@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=libvir-list@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mlevitsk@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=reinoud@netbsd.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
--cc=xen-devel@lists.xenproject.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.