From: Michael Tokarev <mjt@tls.msk.ru>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-block <qemu-block@nongnu.org>
Cc: QEMU Development <qemu-devel@nongnu.org>,
Richard Henderson <richard.henderson@linaro.org>,
Pierrick Bouvier <pierrick.bouvier@linaro.org>
Subject: Re: QEMU requires a 64-bit CPU host architecture?
Date: Wed, 25 Mar 2026 16:05:22 +0300 [thread overview]
Message-ID: <a547c29b-3ab7-42fe-889a-19668bc9d090@tls.msk.ru> (raw)
In-Reply-To: <f3045c88-c64b-45ea-a372-3627cb3b4b01@linaro.org>
On 25.03.2026 14:55, Philippe Mathieu-Daudé wrote:
...
> ... then the single issue in QOM is the object_class_property_init_all()
> (due to sysemu GlobalProperty) which can be stubbed, ...
qga doesn't actually need GlobalProperty, either.
> ... then the only problem left is what util/qsp.c defines:
>
> - qemu_mutex_lock_func()
> - qemu_cond_wait_func()
> - qemu_cond_timedwait_func()
>
> If we can provide a 32-bit version of these the qga links (not sure
> it makes sense although).
And these aren't needed - it seems - by qga either.
Both come to the qga link line using other, unrelated ways.
Thanks,
/mjt
prev parent reply other threads:[~2026-03-25 13:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 6:45 QEMU requires a 64-bit CPU host architecture? Michael Tokarev
2026-03-20 8:54 ` Daniel P. Berrangé
2026-03-20 9:26 ` Helge Deller
2026-03-25 8:08 ` Michael Tokarev
2026-03-25 9:18 ` Daniel P. Berrangé
2026-03-25 10:24 ` Peter Maydell
2026-03-25 11:21 ` Philippe Mathieu-Daudé
2026-03-25 11:31 ` Daniel P. Berrangé
2026-03-25 11:55 ` Philippe Mathieu-Daudé
2026-03-25 13:05 ` Michael Tokarev [this message]
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=a547c29b-3ab7-42fe-889a-19668bc9d090@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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