From: Warner Losh <imp@bsdimp.com>
To: qemu-devel@nongnu.org
Cc: Warner Losh <imp@bsdimp.com>,
Richard Henderson <richard.henderson@linaro.org>,
Kyle Evans <kevans@freebsd.org>,
jrtc27@FreeBSD.org, arrowd@freebsd.org, def@FreeBSD.org
Subject: [PULL 00/11] Bsd user syscall 2022q2 patches
Date: Sun, 19 Jun 2022 12:05:20 -0600 [thread overview]
Message-ID: <20220619180531.9161-1-imp@bsdimp.com> (raw)
The following changes since commit dcb40541ebca7ec98a14d461593b3cd7282b4fac:
Merge tag 'mips-20220611' of https://github.com/philmd/qemu into staging (2022-06-11 21:13:27 -0700)
are available in the Git repository at:
ssh://git@github.com/qemu-bsd-user/qemu-bsd-user.git tags/bsd-user-syscall-2022q2-pull-request
for you to fetch changes up to d35020ed00b1cb649ccd73ba4f5e918a5cc5363a:
bsd-user: Implement acct and sync (2022-06-14 08:17:44 -0600)
----------------------------------------------------------------
bsd-user: Next round of syscalls
Implement the next round of system calls. These are open, openat, close,
fdatasync, fsync, close_from, revoke, access, eacccess, facccessat, chdir,
fchdir, rename, renameat, mkdir, mkdirat, rmdir, _getcwd, dup, dup2, truncate,
ftruncate, acct and sync. In addition, the helper functions needed for these to
work are included. With the helper functions, all of these system calls are the
'obvious' wrapper...
----------------------------------------------------------------
Warner Losh (11):
bsd-user: Implement open, openat and close
bsd-user: Implement fdatasync, fsync and close_from
bsd-user: Implement revoke, access, eaccess and faccessat
bsd-user: Implement chdir and fchdir
bsd-user: Implement rename and renameat
bsd-user: Implement link, linkat, unlink and unlinkat
bsd-user: Implement mkdir and mkdirat
bsd-user: Implement rmdir and undocumented __getcwd
bsd-user: Implement dup and dup2
bsd-user: Implement trunctate and ftruncate
bsd-user: Implement acct and sync
bsd-user/bsd-file.h | 359 ++++++++++++++++++++++++++++++++++
bsd-user/freebsd/os-syscall.c | 116 +++++++++++
bsd-user/syscall_defs.h | 4 +
3 files changed, 479 insertions(+)
--
2.33.1
next reply other threads:[~2022-06-19 18:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 18:05 Warner Losh [this message]
2022-06-19 18:05 ` [PULL 01/11] bsd-user: Implement open, openat and close Warner Losh
2022-06-19 18:05 ` [PULL 02/11] bsd-user: Implement fdatasync, fsync and close_from Warner Losh
2022-06-19 18:05 ` [PULL 03/11] bsd-user: Implement revoke, access, eaccess and faccessat Warner Losh
2022-06-19 18:05 ` [PULL 04/11] bsd-user: Implement chdir and fchdir Warner Losh
2022-06-19 18:05 ` [PULL 05/11] bsd-user: Implement rename and renameat Warner Losh
2022-06-19 18:05 ` [PULL 06/11] bsd-user: Implement link, linkat, unlink and unlinkat Warner Losh
2022-06-19 18:05 ` [PULL 07/11] bsd-user: Implement mkdir and mkdirat Warner Losh
2022-06-19 18:05 ` [PULL 08/11] bsd-user: Implement rmdir and undocumented __getcwd Warner Losh
2022-06-19 18:05 ` [PULL 09/11] bsd-user: Implement dup and dup2 Warner Losh
2022-06-19 18:05 ` [PULL 10/11] bsd-user: Implement trunctate and ftruncate Warner Losh
2022-06-19 18:05 ` [PULL 11/11] bsd-user: Implement acct and sync Warner Losh
2022-06-20 0:20 ` [PULL 00/11] Bsd user syscall 2022q2 patches 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=20220619180531.9161-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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.