From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, rth@twiddle.net,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [Qemu-devel] [RFC for 2.8 0/3] Drop support for 64 bit guests on 32 bit hosts
Date: Tue, 9 Aug 2016 16:55:24 +0100 [thread overview]
Message-ID: <1470758127-17769-1-git-send-email-alex.bennee@linaro.org> (raw)
Hi,
I'm proposing for the 2.8 cycle we officially drop supporting 64 bit
guests on 32 bit hosts. For most of the KVM targets it doesn't make
any sense anyway and for TCG it makes things harder (e.g. supporting
64 bit atomics on a 32 bit platform). I'm not actually convinced
things actually work if built or that anyone relies on these
combinations. Consider these patches a way of flushing any such users
out ;-)
Alex Bennée (3):
configure: check CPU width and disable larger guests
configure: filter 64 bit machines on 32 bit builds
cpu-defs.h: add compile check for HOST vs TARGET LONG_BITS
configure | 50 +++++++++++++++++++++++++++++++++++++++++++++++--
include/exec/cpu-defs.h | 9 +++++++++
2 files changed, 57 insertions(+), 2 deletions(-)
--
2.7.4
next reply other threads:[~2016-08-09 15:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 15:55 Alex Bennée [this message]
2016-08-09 15:55 ` [Qemu-devel] [RFC for 2.8 1/3] configure: check CPU width and disable larger guests Alex Bennée
2016-08-09 16:13 ` Peter Maydell
2016-08-09 18:06 ` Richard Henderson
2016-08-09 15:55 ` [Qemu-devel] [RFC for 2.8 2/3] configure: filter 64 bit machines on 32 bit builds Alex Bennée
2016-08-09 16:15 ` Peter Maydell
2016-08-09 19:08 ` Alex Bennée
2016-08-09 19:11 ` Peter Maydell
2016-08-09 15:55 ` [Qemu-devel] [RFC for 2.8 3/3] cpu-defs.h: add compile check for HOST vs TARGET LONG_BITS Alex Bennée
2016-08-10 9:25 ` [Qemu-devel] [RFC for 2.8 0/3] Drop support for 64 bit guests on 32 bit hosts Gerd Hoffmann
2016-08-15 17:46 ` [Qemu-devel] [Xen-devel] " Stefano Stabellini
2016-08-24 12:23 ` [Qemu-devel] " Alex Bennée
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=1470758127-17769-1-git-send-email-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).