All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
	Martin Schrodt <martin@schrodt.org>,
	Thomas Huth <thuth@redhat.com>, Max Reitz <mreitz@redhat.com>,
	qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] Drop support for 32bit hosts in qemu? (was: [PULL 1/6] audio/hda: create millisecond timers that handle IO)
Date: Wed, 27 Jun 2018 14:03:24 +0100	[thread overview]
Message-ID: <87d0wcwfdv.fsf@linaro.org> (raw)
In-Reply-To: <20180627110923.GG30628@redhat.com>


Daniel P. Berrangé <berrange@redhat.com> writes:

> On Wed, Jun 27, 2018 at 09:57:09AM +0200, Markus Armbruster wrote:
>> Thomas Huth <thuth@redhat.com> writes:
>>
>> > On 27.06.2018 08:51, Gerd Hoffmann wrote:
>> [...]
>> >> Drop support for 32bit hosts in qemu?
>> >
>> > I guess the only way to answer that question reliably is to send a patch
>> > to mark 32-bit hosts as deprecated...
>> >
>> > Anyway, you still have got to fix that problem with -m32 now somehow
>> > since we certainly can not drop 32-bit immediately.
>>
>> We certainly can if we want to.
>>
>> Our formal deprecation policy codifies our compromise between the need
>> to evolve QEMU and the need of its users for stable external interfaces.
>>
>> "Compiles on host X" is also a need, but it's a different one.
>> Evidence: "Supported build platforms" has its own appendix, separate
>> from "Deprecated features".  It's mum on 32-bit hosts.
>
> It is silent on host architecture coverage in general in fact. It was
> only really focusing on operating systems and so any arch coverage is
> at best inferred from what those OS target. Fedora covers 32-bit & 64-bit
> arches for example, so you could take that to imply we need to support
> both in QEMU.
>
> It is fuzzier though because while Peter has good OS coverage for his
> merge testing, I don't think he has full host arch coverage for everything
> that downstreams expect QEMU to build on ?

We do however have cross build infrastructure for all tcg/foo backends.
They are run by the shippable CI framework (which is how I noticed):

  https://app.shippable.com/github/qemu/qemu/runs?branchName=master

Once we have the changes made to the wiki I'd like to use:

  https://wiki.qemu.org/Template:CIStatus

In a few choice places on the wiki, including the front page, for better
visibility.

>> I'm not saying we *should* drop 32-bit hosts immediately.  Only that the
>> feature deprecation policy does not apply.
>>
>> Is QEMU still useful on 32-bit hosts?  Honest question!
>
> That answer varies depending on what you're using QEMU for I think. It
> could be that people see tools like qemu-img/qemu-nbd as useful even
> if they don't use system emulators. And of course userspace emulators
> are enough distinct use case.
>
> IMHO as long as distros are shipping 32-bit support, it is reasonable
> to assume there will be people who find QEMU useful to some degree.
>
> Personally I don't have any need for 32-bit hosts, but clearly some
> people do since otherwise distros would  have killed their 32-bit
> arches already.

I know of at least one kernel developer who uses qemu-system-aarch64 on
their 32 bit ARM Chromebook to test their 64 bit code. Next time I see
them I'll see if they are still using it.

My feeling is although probably not widespread it certainly can be handy.

>
> Regards,
> Daniel


--
Alex Bennée

  reply	other threads:[~2018-06-27 13:03 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-25 13:12 [Qemu-devel] [PULL 0/6] Audio 20180625 patches Gerd Hoffmann
2018-06-25 13:12 ` [Qemu-devel] [PULL 1/6] audio/hda: create millisecond timers that handle IO Gerd Hoffmann
2018-06-26 19:55   ` Max Reitz
2018-06-27  6:51     ` Gerd Hoffmann
2018-06-27  7:24       ` Thomas Huth
2018-06-27  7:57         ` [Qemu-devel] Drop support for 32bit hosts in qemu? (was: [PULL 1/6] audio/hda: create millisecond timers that handle IO) Markus Armbruster
2018-06-27  8:09           ` [Qemu-devel] Drop support for 32bit hosts in qemu? Thomas Huth
2018-06-27  8:56             ` Gerd Hoffmann
2018-06-27 11:08             ` Alex Bennée
2018-06-27 11:09               ` Thomas Huth
2018-06-27  8:15           ` [Qemu-devel] Drop support for 32bit hosts in qemu? (was: [PULL 1/6] audio/hda: create millisecond timers that handle IO) BALATON Zoltan
2018-06-27  8:52             ` Gerd Hoffmann
2018-06-27  9:09               ` Thomas Huth
2018-06-27 13:33                 ` Philippe Mathieu-Daudé
2018-06-27 15:41                   ` Laurent Vivier
2018-06-27 18:44                     ` Dr. David Alan Gilbert
2018-06-27 19:55                       ` Laurent Vivier
2018-06-27 10:49               ` Peter Maydell
2018-06-27 11:09                 ` Dr. David Alan Gilbert
2018-06-27 13:08                   ` Alex Bennée
2018-06-27 13:09                     ` Alex Bennée
2018-06-27 11:09           ` Daniel P. Berrangé
2018-06-27 13:03             ` Alex Bennée [this message]
2018-06-27 13:38               ` Philippe Mathieu-Daudé
2018-06-27 13:02           ` [Qemu-devel] Drop support for 32bit hosts in qemu? Juan Quintela
2018-06-27 13:11             ` Daniel P. Berrangé
2018-06-27 11:13       ` [Qemu-devel] [PULL 1/6] audio/hda: create millisecond timers that handle IO Gerd Hoffmann
2018-06-27 13:15         ` Paolo Bonzini
2018-06-27 12:21       ` Eric Blake
2018-06-29  8:19   ` Peter Maydell
2018-06-29 15:11     ` Eric Blake
2018-06-25 13:12 ` [Qemu-devel] [PULL 2/6] audio/hda: turn some dprintfs into trace points Gerd Hoffmann
2018-06-25 13:12 ` [Qemu-devel] [PULL 3/6] audio/hda: tweak timer adjust logic Gerd Hoffmann
2018-06-25 13:12 ` [Qemu-devel] [PULL 4/6] audio/hda: detect output buffer overruns Gerd Hoffmann
2018-06-25 13:12 ` [Qemu-devel] [PULL 5/6] audio/hda: enable new timer code by default Gerd Hoffmann
2018-06-25 13:12 ` [Qemu-devel] [PULL 6/6] audio: Convert use of atoi to qemu_strtoi Gerd Hoffmann
2018-06-25 15:37 ` [Qemu-devel] [PULL 0/6] Audio 20180625 patches Peter Maydell

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=87d0wcwfdv.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=martin@schrodt.org \
    --cc=mreitz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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.