From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: qemu-devel@nongnu.org
Cc: sw@weilnetz.de, kkostiuk@redhat.com, clg@kaod.org,
richard.henderson@linaro.org, alex.bennee@linaro.org,
Pierrick Bouvier <pierrick.bouvier@linaro.org>
Subject: [PATCH 0/4] Adds support for running QEMU natively on windows-arm64
Date: Mon, 13 Feb 2023 17:13:48 +0100 [thread overview]
Message-ID: <20230213161352.17199-1-pierrick.bouvier@linaro.org> (raw)
Note: As it's my first submission using git send-email and on QEMU, don't
hesitate to report if anything is wrong/missing.
To compile this, the fastest route is to use msys2, setup with clangarm64
repository. This way, all dependencies can be installed easily, and clang is
available directly. Please note that GCC currently is not able to generate code
for this platform, so only clang can be used for now.
---
After having being able to compile, I had to fix two blocking issues:
- illegal instruction
- setjmp/longjmp segfaulting
Then, two warnings were reported, and their fix is included in this series as
well, so we can have clean support out of the box on this platform.
---
This series was tested with:
- make check (find a full log here [1], compiled using this script [2])
- installing and booting a debian bullseye x64
- installing and booting an ubuntu 22.10 arm64
Despite the slowness of an emulated system, it works well!
[1] https://gitlab.com/Linaro/windowsonarm/packages/qemu/-/jobs/3761641695
[2] https://gitlab.com/Linaro/windowsonarm/packages/qemu/-/blob/master/recipe.sh
---
As it has been discussed privately inside Linaro, we can allocate one Windows on
Arm machine (running in our lab), to add a runner for gitlab CI. But this is
probably a discussion for another thread.
---
Pierrick Bouvier (4):
util/cacheflush: fix illegal instruction on windows-arm64
sysemu/os-win32: fix setjmp/longjmp on windows-arm64
qga/vss-win32: fix warning for clang++-15
target/ppc: fix warning with clang-15
include/sysemu/os-win32.h | 18 ++++++++++++++++--
qga/vss-win32/install.cpp | 2 +-
target/ppc/dfp_helper.c | 4 ++--
util/cacheflush.c | 5 +++--
4 files changed, 22 insertions(+), 7 deletions(-)
--
2.30.2
next reply other threads:[~2023-02-13 20:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 16:13 Pierrick Bouvier [this message]
2023-02-13 16:13 ` [PATCH 1/4] util/cacheflush: fix illegal instruction on windows-arm64 Pierrick Bouvier
2023-02-14 16:44 ` Peter Maydell
2023-02-14 17:02 ` Richard Henderson
2023-02-15 12:49 ` Pierrick Bouvier
2023-02-15 18:22 ` Richard Henderson
2023-02-16 12:53 ` Pierrick Bouvier
2023-02-13 16:13 ` [PATCH 2/4] sysemu/os-win32: fix setjmp/longjmp " Pierrick Bouvier
2023-02-14 7:11 ` Philippe Mathieu-Daudé
2023-02-14 8:16 ` Pierrick Bouvier
2023-02-13 16:13 ` [PATCH 3/4] qga/vss-win32: fix warning for clang++-15 Pierrick Bouvier
2023-02-13 16:20 ` Konstantin Kostiuk
2023-02-13 18:08 ` Cédric Le Goater
2023-02-13 16:13 ` [PATCH 4/4] target/ppc: fix warning with clang-15 Pierrick Bouvier
2023-02-13 18:08 ` Cédric Le Goater
2023-02-14 7:14 ` Philippe Mathieu-Daudé
2023-02-14 7:57 ` Pierrick Bouvier
2023-02-14 18:10 ` Richard Henderson
2023-02-15 10:58 ` Pierrick Bouvier
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=20230213161352.17199-1-pierrick.bouvier@linaro.org \
--to=pierrick.bouvier@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=clg@kaod.org \
--cc=kkostiuk@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sw@weilnetz.de \
/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).