From: Warner Losh <imp@bsdimp.com>
To: qemu-devel@nongnu.org
Cc: arrowd@freebsd.org, kevans@freebsd.org,
richard.henderson@linaro.org, f4bug@amsat.org, def@freebsd.org,
Warner Losh <imp@bsdimp.com>
Subject: [PATCH for 7.0 0/5] bsd-user-smoke: A simple smoke test for bsd-user
Date: Sat, 27 Nov 2021 13:18:41 -0700 [thread overview]
Message-ID: <20211127201846.64187-1-imp@bsdimp.com> (raw)
This series adds a number of simple binaries that FreeBSD's clang can build on
any system. I've kept it simple so that there's no extra binaries that need to
be installed. Given the current state of bsd-user in the project's repo, this
likely is as extensive a set of tests that should be done right now. We can load
static binaries only (so these are static binaries) and hello world is the
canonical test. I have binaries for all the supported FreeBSD targets, but have
included only the ones that are in upstream (or in review) at this time.
In the future, I'll integreate with the tcg tests when there's more in upstream
they can test. Since that requires putting together FreeBSD sysroots for all
the supported architectures for multiple versions, I'm going to delay that for a
while. I'll also integrate FreeBSD's 5k system tests when we're much further
along with the upstreaming.
The purpose of this is to give others doing changes in this area a standardized
way to ensure their changes don't fundamentally break bsd-user. This approach
will work for all setups that do a 'make check' to do their testing.
Based-on: 20211108035136.43687-1-imp@bsdimp.com
Warner Losh (5):
h.armv7: Simple hello-world test for armv7
h.i386: Simple hello-world test for i386
h.amd64: Simple hello-world test for x86_64
smoke-bsd-user: A test script to run all the FreeBSD binaries
bsd-user-smoke: Add to build
tests/bsd-user-smoke/h.amd64.S | 28 +++++++++++++++++++++
tests/bsd-user-smoke/h.armv7.S | 37 +++++++++++++++++++++++++++
tests/bsd-user-smoke/h.i386.S | 39 +++++++++++++++++++++++++++++
tests/bsd-user-smoke/meson.build | 31 +++++++++++++++++++++++
tests/bsd-user-smoke/smoke-bsd-user | 22 ++++++++++++++++
tests/meson.build | 1 +
6 files changed, 158 insertions(+)
create mode 100644 tests/bsd-user-smoke/h.amd64.S
create mode 100644 tests/bsd-user-smoke/h.armv7.S
create mode 100644 tests/bsd-user-smoke/h.i386.S
create mode 100644 tests/bsd-user-smoke/meson.build
create mode 100644 tests/bsd-user-smoke/smoke-bsd-user
--
2.33.0
next reply other threads:[~2021-11-27 20:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 20:18 Warner Losh [this message]
2021-11-27 20:18 ` [PATCH for 7.0 1/5] h.armv7: Simple hello-world test for armv7 Warner Losh
2021-11-27 20:18 ` [PATCH for 7.0 2/5] h.i386: Simple hello-world test for i386 Warner Losh
2021-11-27 20:18 ` [PATCH for 7.0 3/5] h.amd64: Simple hello-world test for x86_64 Warner Losh
2021-11-27 20:18 ` [PATCH for 7.0 4/5] smoke-bsd-user: A test script to run all the FreeBSD binaries Warner Losh
2021-11-27 20:18 ` [PATCH for 7.0 5/5] bsd-user-smoke: Add to build Warner Losh
2022-01-04 23:25 ` Philippe Mathieu-Daudé
2022-01-04 23:28 ` Warner Losh
2021-12-03 23:46 ` [PATCH for 7.0 0/5] bsd-user-smoke: A simple smoke test for bsd-user Warner Losh
2022-01-04 17:20 ` Alex Bennée
2022-01-04 17:39 ` Warner Losh
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=20211127201846.64187-1-imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=arrowd@freebsd.org \
--cc=def@freebsd.org \
--cc=f4bug@amsat.org \
--cc=kevans@freebsd.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;
as well as URLs for NNTP newsgroup(s).