From: Karim Taha <kariem.taha2.7@gmail.com>
To: qemu-devel@nongnu.org
Cc: Warner Losh <imp@bsdimp.com>,
Richard Henderson <richard.henderson@linaro.org>,
Stacey Son <sson@FreeBSD.org>,
Karim Taha <kariem.taha2.7@gmail.com>
Subject: [PATCH v5 02/28] bsd-user: Define procctl(2) related structs
Date: Mon, 25 Sep 2023 21:23:59 +0300 [thread overview]
Message-ID: <20230925182425.3163-3-kariem.taha2.7@gmail.com> (raw)
In-Reply-To: <20230925182425.3163-1-kariem.taha2.7@gmail.com>
From: Stacey Son <sson@FreeBSD.org>
Implement procctl flags and related structs:
struct target_procctl_reaper_status
struct target_procctl_reaper_pidinfo
struct target_procctl_reaper_pids
struct target_procctl_reaper_kill
Signed-off-by: Stacey Son <sson@FreeBSD.org>
Signed-off-by: Karim Taha <kariem.taha2.7@gmail.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Warner Losh <imp@bsdimp.com>
---
bsd-user/syscall_defs.h | 42 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 42 insertions(+)
diff --git a/bsd-user/syscall_defs.h b/bsd-user/syscall_defs.h
index ddd38c13e0..a3bc738ff8 100644
--- a/bsd-user/syscall_defs.h
+++ b/bsd-user/syscall_defs.h
@@ -390,6 +390,48 @@ struct target_freebsd_flock {
/* user: vfork(2) semantics, clear signals */
#define TARGET_RFSPAWN (1U << 31)
+/*
+ * from sys/procctl.h
+ */
+#define TARGET_PROC_SPROTECT 1
+#define TARGET_PROC_REAP_ACQUIRE 2
+#define TARGET_PROC_REAP_RELEASE 3
+#define TARGET_PROC_REAP_STATUS 4
+#define TARGET_PROC_REAP_GETPIDS 5
+#define TARGET_PROC_REAP_KILL 6
+
+struct target_procctl_reaper_status {
+ uint32_t rs_flags;
+ uint32_t rs_children;
+ uint32_t rs_descendants;
+ uint32_t rs_reaper;
+ uint32_t rs_pid;
+ uint32_t rs_pad0[15];
+};
+
+struct target_procctl_reaper_pidinfo {
+ uint32_t pi_pid;
+ uint32_t pi_subtree;
+ uint32_t pi_flags;
+ uint32_t pi_pad0[15];
+};
+
+struct target_procctl_reaper_pids {
+ uint32_t rp_count;
+ uint32_t rp_pad0[15];
+ abi_ulong rp_pids;
+};
+
+struct target_procctl_reaper_kill {
+ int32_t rk_sig;
+ uint32_t rk_flags;
+ uint32_t rk_subtree;
+ uint32_t rk_killed;
+ uint32_t rk_fpid;
+ uint32_t rk_pad0[15];
+};
+
+
#define safe_syscall0(type, name) \
type safe_##name(void) \
{ \
--
2.42.0
next prev parent reply other threads:[~2023-09-25 18:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 18:23 [PATCH v5 00/28] bsd-user: Implement freebsd process related system calls Karim Taha
2023-09-25 18:23 ` [PATCH v5 01/28] bsd-user: define TARGET_RFSPAWN for rfork to use vfork(2) semantics, and fix RLIM_INFINITY Karim Taha
2023-09-25 18:23 ` Karim Taha [this message]
2023-09-25 18:24 ` [PATCH v5 03/28] bsd-user: Implement host_to_target_siginfo Karim Taha
2023-09-25 18:24 ` [PATCH v5 04/28] bsd-user: Add freebsd_exec_common and do_freebsd_procctl to qemu.h Karim Taha
2023-09-25 18:24 ` [PATCH v5 05/28] bsd-user: add extern declarations for bsd-proc.c conversion functions Karim Taha
2023-09-25 18:24 ` [PATCH v5 06/28] bsd-user: Implement target_to_host_resource conversion function Karim Taha
2023-09-25 18:24 ` [PATCH v5 07/28] bsd-user: Implement target_to_host_rlim and host_to_target_rlim conversion Karim Taha
2023-09-25 18:24 ` [PATCH v5 08/28] bsd-user: Implement host_to_target_rusage and host_to_target_wrusage Karim Taha
2023-09-25 18:24 ` [PATCH v5 09/28] bsd-user: Implement host_to_target_waitstatus conversion Karim Taha
2023-09-25 18:24 ` [PATCH v5 10/28] bsd-user: Get number of cpus Karim Taha
2023-09-25 18:24 ` [PATCH v5 11/28] bsd-user: Implement getgroups(2) and setgroups(2) system calls Karim Taha
2023-09-25 18:24 ` [PATCH v5 12/28] bsd-user: Implement umask(2), setlogin(2) and getlogin(2) Karim Taha
2023-09-25 18:24 ` [PATCH v5 13/28] bsd-user: Implement getrusage(2) Karim Taha
2023-09-25 18:24 ` [PATCH v5 14/28] bsd-user: Implement getrlimit(2) and setrlimit(2) Karim Taha
2023-09-25 18:24 ` [PATCH v5 15/28] bsd-user: Implement several get/set system calls: Karim Taha
2023-09-25 18:24 ` [PATCH v5 16/28] bsd-user: Implement get/set[resuid/resgid/sid] and issetugid Karim Taha
2023-09-25 18:24 ` [PATCH v5 17/28] bsd-user: Add stubs for profil(2), ktrace(2), utrace(2) and ptrace(2) Karim Taha
2023-09-25 18:24 ` [PATCH v5 18/28] bsd-user: Implement getpriority(2) and setpriority(2) Karim Taha
2023-09-25 18:24 ` [PATCH v5 19/28] bsd-user: Implement get_filename_from_fd Karim Taha
2023-09-25 18:24 ` [PATCH v5 20/28] bsd-user: Implement freebsd_exec_common, used in implementing execve/fexecve Karim Taha
2023-09-25 18:24 ` [PATCH v5 21/28] bsd-user: Implement procctl(2) along with necessary conversion functions Karim Taha
2023-09-25 18:24 ` [PATCH v5 22/28] bsd-user: Implement execve(2) and fexecve(2) system calls Karim Taha
2023-09-25 18:24 ` [PATCH v5 23/28] bsd-user: Implement wait4(2) and wait6(2) " Karim Taha
2023-09-25 18:24 ` [PATCH v5 24/28] bsd-user: Implement setloginclass(2) and getloginclass(2) " Karim Taha
2023-09-25 18:24 ` [PATCH v5 25/28] bsd-user: Implement pdgetpid(2) and the undocumented setugid Karim Taha
2023-09-25 18:24 ` [PATCH v5 26/28] bsd-user: Implement fork(2) and vfork(2) system calls Karim Taha
2023-09-25 18:24 ` [PATCH v5 27/28] bsd-user: Implement rfork(2) system call Karim Taha
2023-09-25 18:24 ` [PATCH v5 28/28] bsd-user: Implement pdfork(2) " Karim Taha
2023-09-27 4:25 ` [PATCH v5 00/28] bsd-user: Implement freebsd process related system calls 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=20230925182425.3163-3-kariem.taha2.7@gmail.com \
--to=kariem.taha2.7@gmail.com \
--cc=imp@bsdimp.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sson@FreeBSD.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).