From: Peter Maydell <peter.maydell@linaro.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Joao Martins <joao.m.martins@oracle.com>,
QEMU Developers <qemu-devel@nongnu.org>,
David Woodhouse <dwmw@amazon.co.uk>
Subject: Re: xen bits broke x32 build
Date: Tue, 11 Apr 2023 13:09:03 +0100 [thread overview]
Message-ID: <CAFEAcA8DyTixWoeRpt3R7MHmLEwnvX5Y6ciCDaVj1n7K6GnOeQ@mail.gmail.com> (raw)
In-Reply-To: <7739b40d-d8ba-ccde-cc6c-5d9f2c93a663@msgid.tls.msk.ru>
On Tue, 11 Apr 2023 at 12:57, Michael Tokarev <mjt@tls.msk.ru> wrote:
>
> 01.04.2023 11:40, Michael Tokarev wrote:
> > After bringing in xen guest support, qemu fails to build on x32:
> >
> > target/i386/kvm/xen-emu.c:876:5: note: in expansion of macro ‘qemu_build_assert’
> > 876 | qemu_build_assert(sizeof(struct vcpu_info) == 64);
> > | ^~~~~~~~~~~~~~~~~
> >
> > This one should be easy to fix, but I wonder if there are other issues
> > with x32 exists..
>
> Ok, I took a look at how to disable this new XEN stuff on x32.
>
> It is the commit 820c1aba519bd072ac71c754733f6c86d8b4309 "xen: add
> CONFIG_XEN_BUS and CONFIG_XEN_EMU options for Xen emulation" adding
> this construct to hw/i386/Kconfig:
>
> config XEN_EMU
> bool
> default y
> depends on KVM && (I386 || X86_64)
>
> Since meson does not know about x32, and while ./conifgure does, it
> is not propagated to meson, and sure not propagated to Kconfig too,
> there's some more work needed to disable XEN_EMU on x32.
Frankly I would prefer to just say "we don't support x32".
It's a weird non-standard configuration that as far as I'm
aware is very little used. Its stats in the debian
popularity-contest graphs peaked at 18 users in 2017, and
have mostly been fluctuating between 1 and 3 for the last
couple of years:
https://popcon.debian.org/stat/sub-x32.png
We're currently planning to deprecate-and-drop 32-bit x86
hosts, which are much more widely used than this. I see
no reason why we should care about this oddball failed
experiment of an ABI...
thanks
-- PMM
next prev parent reply other threads:[~2023-04-11 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 8:40 xen bits broke x32 build Michael Tokarev
2023-04-01 11:45 ` Joao Martins
2023-04-01 11:57 ` Michael Tokarev
2023-04-01 12:10 ` David Woodhouse
2023-04-03 6:46 ` Philippe Mathieu-Daudé
2023-04-03 8:46 ` David Woodhouse
2023-04-01 12:07 ` Michael Tokarev
2023-04-11 11:56 ` Michael Tokarev
2023-04-11 12:09 ` Peter Maydell [this message]
2023-04-11 17:30 ` Michael Tokarev
2023-04-12 10:19 ` Philippe Mathieu-Daudé
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=CAFEAcA8DyTixWoeRpt3R7MHmLEwnvX5Y6ciCDaVj1n7K6GnOeQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=dwmw@amazon.co.uk \
--cc=joao.m.martins@oracle.com \
--cc=mjt@tls.msk.ru \
--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).