From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
libvir-list@redhat.com, "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Reinoud Zandijk" <reinoud@netbsd.org>,
"Ryo ONODERA" <ryoon@netbsd.org>,
"Brad Smith" <brad@comstyle.com>, "Stefan Weil" <sw@weilnetz.de>,
qemu-devel@nongnu.org
Subject: Re: [RFC PATCH] docs/about/deprecated: Deprecate 32-bit host systems
Date: Mon, 30 Jan 2023 20:45:47 +0000 [thread overview]
Message-ID: <87h6w7694t.fsf@linaro.org> (raw)
In-Reply-To: <Y9exrDWT2NUoinu1@redhat.com>
Daniel P. Berrangé <berrange@redhat.com> writes:
> On Mon, Jan 30, 2023 at 11:47:02AM +0000, Peter Maydell wrote:
>> On Mon, 30 Jan 2023 at 11:44, Thomas Huth <thuth@redhat.com> wrote:
>> >
>> > Testing 32-bit host OS support takes a lot of precious time during the QEMU
>> > contiguous integration tests, and considering that many OS vendors stopped
>> > shipping 32-bit variants of their OS distributions and most hardware from
>> > the past >10 years is capable of 64-bit
>>
>> True for x86, not necessarily true for other architectures.
>> Are you proposing to deprecate x86 32-bit, or all 32-bit?
>> I'm not entirely sure about whether we're yet at a point where
>> I'd want to deprecate-and-drop 32-bit arm host support.
>
> Do we have a feeling on which aspects of 32-bit cause us the support
> burden ? The boring stuff like compiler errors from mismatched integer
> sizes is mostly quick & easy to detect simply through a cross compile.
>
> I vaguely recall someone mentioned problems with atomic ops in the past,
> or was it 128-bit ints, caused implications for the codebase ?
Atomic operations on > TARGET_BIT_SIZE and cputlb when
TCG_OVERSIZED_GUEST is set. Also the core TCG code and a bunch of the
backends have TARGET_LONG_BITS > TCG_TARGET_REG_BITS ifdefs peppered
throughout.
>
> With regards,
> Daniel
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-01-30 20:49 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 11:44 [RFC PATCH] docs/about/deprecated: Deprecate 32-bit host systems Thomas Huth
2023-01-30 11:47 ` Peter Maydell
2023-01-30 12:01 ` Daniel P. Berrangé
2023-01-30 12:22 ` Thomas Huth
2023-01-30 12:43 ` Daniel P. Berrangé
2023-01-30 13:07 ` Thomas Huth
2023-01-30 19:19 ` Richard Henderson
2023-01-30 23:14 ` Philippe Mathieu-Daudé
2023-01-30 23:33 ` Richard Henderson
2023-01-31 0:19 ` Philippe Mathieu-Daudé
2023-01-30 20:45 ` Alex Bennée [this message]
2023-02-05 22:12 ` Mark Cave-Ayland
2023-04-04 14:00 ` Thomas Huth
2023-04-04 14:20 ` Cédric Le Goater
2023-04-04 15:58 ` BALATON Zoltan
2023-04-04 14:32 ` Cédric Le Goater
2023-04-04 15:42 ` BALATON Zoltan
2023-04-05 8:01 ` Thomas Huth
2023-04-05 11:54 ` BALATON Zoltan
2023-04-05 12:51 ` Thomas Huth
2023-04-04 15:50 ` BALATON Zoltan
2023-04-05 21:01 ` Mark Cave-Ayland
2023-02-22 9:11 ` Bernhard Beschow
2023-02-22 9:51 ` Daniel P. Berrangé
2023-02-22 12:28 ` Reinoud Zandijk
2023-02-22 13:37 ` Alex Bennée
2023-02-17 10:36 ` Markus Armbruster
2023-02-17 10:40 ` Daniel P. Berrangé
2023-02-17 10:45 ` Claudio Fontana
2023-02-17 10:47 ` Daniel P. Berrangé
2023-02-17 11:05 ` Stefan Weil via
2023-02-17 11:43 ` Markus Armbruster
2023-02-17 11:47 ` Daniel P. Berrangé
2023-02-19 11:27 ` Reinoud Zandijk
2023-02-19 12:12 ` Stefan Weil via
2023-02-17 16:38 ` Paolo Bonzini
2023-02-17 17:43 ` Philippe Mathieu-Daudé
2023-02-17 18:57 ` Thomas Huth
2023-02-18 22:54 ` Jiaxun Yang
2023-02-17 19:49 ` Thomas Huth
2023-02-17 16:06 ` Reinoud Zandijk
2023-02-17 17:20 ` Daniel P. Berrangé
2023-02-17 18:22 ` Richard Henderson
2023-02-19 11:07 ` Reinoud Zandijk
2023-02-17 11:09 ` Claudio Fontana
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=87h6w7694t.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=brad@comstyle.com \
--cc=libvir-list@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=reinoud@netbsd.org \
--cc=richard.henderson@linaro.org \
--cc=ryoon@netbsd.org \
--cc=stefanha@redhat.com \
--cc=sw@weilnetz.de \
--cc=thuth@redhat.com \
/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.