From a4851206bef5ceecef18b3fde5be6918a67cca21 Mon Sep 17 00:00:00 2001 From: Kimplul Date: Sat, 21 May 2022 21:23:12 +0300 Subject: add create syscall for threads --- common/uapi/dispatch.c | 1 + common/uapi/proc.c | 6 +++++- 2 files changed, 6 insertions(+), 1 deletion(-) (limited to 'common/uapi') diff --git a/common/uapi/dispatch.c b/common/uapi/dispatch.c index 8ffaffb..97fc0d8 100644 --- a/common/uapi/dispatch.c +++ b/common/uapi/dispatch.c @@ -21,6 +21,7 @@ static const sys_t syscall_table[] = { [SYS_IPC_RESP] = sys_ipc_resp, /* proc */ + [SYS_CREATE] = sys_create, [SYS_FORK] = sys_fork, [SYS_EXEC] = sys_exec, [SYS_SIGNAL] = sys_signal, diff --git a/common/uapi/proc.c b/common/uapi/proc.c index bd5874d..3ce3bcb 100644 --- a/common/uapi/proc.c +++ b/common/uapi/proc.c @@ -1,5 +1,10 @@ #include +SYSCALL_DEFINE0(create)() +{ + return (struct sys_ret){ OK, 0 }; +} + /* Not entirely sure how I should handle forks/execs etc, mostly whether I * should allow forks/execs to be called directly or only though the process * manager. Probably though the process manager, although that will add in a @@ -12,7 +17,6 @@ */ SYSCALL_DEFINE0(fork)() { - /* TODO: create new thread in the same process family */ return (struct sys_ret){ OK, 0 }; } -- cgit v1.3