From: Warner Losh <imp@bsdimp.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
arrowd@FreeBSD.org, Kyle Evans <kevans@freebsd.org>,
Richard Henderson <richard.henderson@linaro.org>,
def@FreeBSD.org, jrtc27@FreeBSD.org, Warner Losh <imp@bsdimp.com>,
Brad Smith <brad@comstyle.com>
Subject: [PULL 00/16] Bsd user preen 2022q1 patches
Date: Mon, 28 Feb 2022 11:11:58 -0700 [thread overview]
Message-ID: <20220228181214.2602-1-imp@bsdimp.com> (raw)
The following changes since commit fa435db8ce1dff3b15e3f59a12f55f7b3a347b08:
Merge remote-tracking branch 'remotes/jsnow-gitlab/tags/python-pull-request' into staging (2022-02-24 12:48:14 +0000)
are available in the Git repository at:
git@gitlab.com:bsdimp/qemu.git tags/bsd-user-preen-2022q1-pull-request
for you to fetch changes up to a5b8816636ebd7665d96122c5568192e04c5a888:
bsd-user: Add safe system call macros (2022-02-26 21:05:21 -0700)
----------------------------------------------------------------
bsd-user: Prepare for future upstream of system calls.
This series of patches does three things.
First, it starts to give up on the idea that you can run FooBSD binaries on
BarBSD. They are too different to make that happen any time soon, though I've
kept the support for Net/OpenBSD, even though they haven't built. We'll need a
lot of work to make that happen, though, and I need to simplify to get things
upstream.
Second, it starts to move some of the ifdef trees into target.h.
Third, it starts to upstream bsd-file.h, but the remainder of the file in the
bsd-user fork had some issues that will be resolved before next quarter's
update.
----------------------------------------------------------------
Warner Losh (16):
bsd-user/main.c: Drop syscall flavor arg -bsd
bsd-user/x86_64/target_arch_cpu.h: int $80 never was a BSD system call
on amd64
bsd-user/x86_64/target_arch_cpu.h: Remove openbsd syscall
bsd-user/i386/target_arch_cpu.h: Remove openbsd syscall
bsd-user/arm/target_arch_cpu.h: Only support FreeBSD sys calls
bsd-user/arm/target_arch_thread.h: Assume a FreeBSD target
bsd-user/x86_64/target_arch_thread.h: Assume a FreeBSD target
bsd-user: Remove bsd_type
bsd-user/freebsd/os-syscall.c: Move syscall processing here
bsd-user: Move system call building to os-syscall.c
bsd-user/sycall.c: Now obsolete, remove
bsd-user/freebsd/os-syscall.c: Add get_errno and host_to_target_errno
bsd-user/bsd-file.h: Implementation details for the filesystem calls
bsd-user: introduce target.h
bsd-user: Define target_arg64
bsd-user: Add safe system call macros
bsd-user/arm/target.h | 21 ++
bsd-user/arm/target_arch_cpu.h | 139 ++++----
bsd-user/arm/target_arch_thread.h | 4 +-
bsd-user/bsd-file.h | 30 ++
bsd-user/freebsd/meson.build | 1 +
bsd-user/freebsd/os-syscall.c | 92 +++++
bsd-user/i386/target.h | 21 ++
bsd-user/i386/target_arch_cpu.h | 84 ++---
bsd-user/main.c | 14 -
bsd-user/meson.build | 1 -
bsd-user/qemu.h | 24 +-
bsd-user/syscall.c | 516 ---------------------------
bsd-user/syscall_defs.h | 47 +++
bsd-user/x86_64/target.h | 21 ++
bsd-user/x86_64/target_arch_cpu.h | 85 +----
bsd-user/x86_64/target_arch_thread.h | 4 +-
16 files changed, 362 insertions(+), 742 deletions(-)
create mode 100644 bsd-user/arm/target.h
create mode 100644 bsd-user/bsd-file.h
create mode 100644 bsd-user/freebsd/os-syscall.c
create mode 100644 bsd-user/i386/target.h
delete mode 100644 bsd-user/syscall.c
create mode 100644 bsd-user/x86_64/target.h
--
2.33.1
next reply other threads:[~2022-02-28 18:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 18:11 Warner Losh [this message]
2022-02-28 18:11 ` [PULL 01/16] bsd-user/main.c: Drop syscall flavor arg -bsd Warner Losh
2022-02-28 18:12 ` [PULL 02/16] bsd-user/x86_64/target_arch_cpu.h: int $80 never was a BSD system call on amd64 Warner Losh
2022-02-28 18:12 ` [PULL 03/16] bsd-user/x86_64/target_arch_cpu.h: Remove openbsd syscall Warner Losh
2022-02-28 18:12 ` [PULL 04/16] bsd-user/i386/target_arch_cpu.h: " Warner Losh
2022-02-28 18:12 ` [PULL 05/16] bsd-user/arm/target_arch_cpu.h: Only support FreeBSD sys calls Warner Losh
2022-02-28 18:12 ` [PULL 06/16] bsd-user/arm/target_arch_thread.h: Assume a FreeBSD target Warner Losh
2022-02-28 18:12 ` [PULL 07/16] bsd-user/x86_64/target_arch_thread.h: " Warner Losh
2022-02-28 18:12 ` [PULL 08/16] bsd-user: Remove bsd_type Warner Losh
2022-02-28 18:12 ` [PULL 09/16] bsd-user/freebsd/os-syscall.c: Move syscall processing here Warner Losh
2022-02-28 18:12 ` [PULL 10/16] bsd-user: Move system call building to os-syscall.c Warner Losh
2022-02-28 18:12 ` [PULL 11/16] bsd-user/sycall.c: Now obsolete, remove Warner Losh
2022-02-28 18:12 ` [PULL 12/16] bsd-user/freebsd/os-syscall.c: Add get_errno and host_to_target_errno Warner Losh
2022-02-28 18:12 ` [PULL 13/16] bsd-user/bsd-file.h: Implementation details for the filesystem calls Warner Losh
2022-02-28 18:12 ` [PULL 14/16] bsd-user: introduce target.h Warner Losh
2022-02-28 18:12 ` [PULL 15/16] bsd-user: Define target_arg64 Warner Losh
2022-02-28 18:12 ` [PULL 16/16] bsd-user: Add safe system call macros Warner Losh
2022-03-02 10:45 ` [PULL 00/16] Bsd user preen 2022q1 patches Peter Maydell
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=20220228181214.2602-1-imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=arrowd@FreeBSD.org \
--cc=brad@comstyle.com \
--cc=def@FreeBSD.org \
--cc=jrtc27@FreeBSD.org \
--cc=kevans@freebsd.org \
--cc=peter.maydell@linaro.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).