From: Warner Losh <imp@bsdimp.com>
To: qemu-devel@nongnu.org
Cc: jrtc27@FreeBSD.org, def@freebsd.org, Warner Losh <imp@bsdimp.com>,
arrowd@freebsd.org, Kyle Evans <kevans@freebsd.org>
Subject: [PATCH v2 0/6] bsd-user upstreaming: read, write and exit
Date: Wed, 8 Jun 2022 15:17:05 -0600 [thread overview]
Message-ID: <20220608211711.56158-1-imp@bsdimp.com> (raw)
This series of patches continues the effort to get system calls working
upstream. This series was cleaved off a prior series to give me time to rework
based on the feedback from the first time I posted these.
o bsd-user/freebsd/os-syscall.c: lock_iovec
I rewored to use g_try_new, as well as fixing bugs in the 'after a FAULT
handling code' Created a common routine to cleanup after errors that can
be used for the unlock_iovec.
o bsd-user/freebsd/os-syscall.c: unlock_iovec
Fixed the error handling to be consistent with a normal unlock_iovec.
o bsd-user/freebsd/os-syscall.c: Tracing and error boilerplate
Created the wrapper function as suggested in prior reviews.
V2: Use g_try_new0 and simplify based on not needing to initialize things
to zero that are already zero. Only affects the 'lock_iovec' hunk.
V2: Remove inline tags from do_bsd_* routines.
V2: Clean up logging a little
Now all the patches, except the last one, need to be reviewed.
Warner Losh (6):
bsd-user/freebsd/os-syscall.c: lock_iovec
bsd-user/freebsd/os-syscall.c: unlock_iovec
bsd-user/freebsd/os-syscall.c: Tracing and error boilerplate
bsd-user/bsd-file.h: Add implementations for read, pread, readv and
preadv
bsd-user/bsd-file.h: Meat of the write system calls
bsd-user/freebsd/os-syscall.c: Implement exit
bsd-user/bsd-file.h | 163 +++++++++++++++++++++++++
bsd-user/bsd-proc.h | 43 +++++++
bsd-user/freebsd/os-syscall.c | 217 +++++++++++++++++++++++++++++++++-
3 files changed, 419 insertions(+), 4 deletions(-)
create mode 100644 bsd-user/bsd-proc.h
--
2.33.1
next reply other threads:[~2022-06-08 21:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 21:17 Warner Losh [this message]
2022-06-08 21:17 ` [PATCH v2 1/6] bsd-user/freebsd/os-syscall.c: lock_iovec Warner Losh
2022-06-08 21:17 ` [PATCH v2 2/6] bsd-user/freebsd/os-syscall.c: unlock_iovec Warner Losh
2022-06-08 21:17 ` [PATCH v2 3/6] bsd-user/freebsd/os-syscall.c: Tracing and error boilerplate Warner Losh
2022-06-08 21:17 ` [PATCH v2 4/6] bsd-user/bsd-file.h: Add implementations for read, pread, readv and preadv Warner Losh
2022-06-08 21:17 ` [PATCH v2 5/6] bsd-user/bsd-file.h: Meat of the write system calls Warner Losh
2022-06-08 21:17 ` [PATCH v2 6/6] bsd-user/freebsd/os-syscall.c: Implement exit Warner Losh
2022-06-09 14:15 ` Richard Henderson
2022-06-09 14:16 ` [PATCH v2 0/6] bsd-user upstreaming: read, write and exit Richard Henderson
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=20220608211711.56158-1-imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=arrowd@freebsd.org \
--cc=def@freebsd.org \
--cc=jrtc27@FreeBSD.org \
--cc=kevans@freebsd.org \
--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).