qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: qemu-devel@nongnu.org
Cc: arrowd@freebsd.org, def@freebsd.org, jrtc27@FreeBSD.org,
	Warner Losh <imp@bsdimp.com>, Kyle Evans <kevans@freebsd.org>
Subject: [PATCH 0/6] bsd-user upstreaming: read, write and exit
Date: Tue,  7 Jun 2022 14:14:34 -0600	[thread overview]
Message-ID: <20220607201440.41464-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.

These still need review based on comments from  Richard Henderson

       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.

The others were reviewed before, and haven't changed in any real way, but more
eyes likely won't hurt.

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           | 164 ++++++++++++++++++++++++
 bsd-user/bsd-proc.h           |  43 +++++++
 bsd-user/freebsd/os-syscall.c | 231 +++++++++++++++++++++++++++++++++-
 3 files changed, 434 insertions(+), 4 deletions(-)
 create mode 100644 bsd-user/bsd-proc.h

-- 
2.33.1



             reply	other threads:[~2022-06-07 20:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 20:14 Warner Losh [this message]
2022-06-07 20:14 ` [PATCH 1/6] bsd-user/freebsd/os-syscall.c: lock_iovec Warner Losh
2022-06-07 21:01   ` Richard Henderson
2022-06-07 21:31     ` Warner Losh
2022-06-07 20:14 ` [PATCH 2/6] bsd-user/freebsd/os-syscall.c: unlock_iovec Warner Losh
2022-06-07 21:28   ` Richard Henderson
2022-06-07 21:51     ` Warner Losh
2022-06-07 22:23       ` Richard Henderson
2022-06-07 23:35         ` Warner Losh
2022-06-08  2:02           ` Richard Henderson
2022-06-08 16:32             ` Warner Losh
2022-06-07 20:14 ` [PATCH 3/6] bsd-user/freebsd/os-syscall.c: Tracing and error boilerplate Warner Losh
2022-06-07 21:34   ` Richard Henderson
2022-06-07 21:56     ` Warner Losh
2022-06-07 20:14 ` [PATCH 4/6] bsd-user/bsd-file.h: Add implementations for read, pread, readv and preadv Warner Losh
2022-06-07 21:45   ` Richard Henderson
2022-06-08  2:02     ` Warner Losh
2022-06-07 20:14 ` [PATCH 5/6] bsd-user/bsd-file.h: Meat of the write system calls Warner Losh
2022-06-07 21:46   ` Richard Henderson
2022-06-07 20:14 ` [PATCH 6/6] bsd-user/freebsd/os-syscall.c: Implement exit 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=20220607201440.41464-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).