From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Guo Ren <guoren@kernel.org>,
linux-csky@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: set_thread_area.2: csky architecture undocumented
Date: Mon, 23 Nov 2020 22:31:05 +0100 [thread overview]
Message-ID: <014e670b-2a11-3deb-4e7e-bfe9defd8597@gmail.com> (raw)
Hi Michael,
SYNOPSIS
#include <linux/unistd.h>
#if defined __i386__ || defined __x86_64__
# include <asm/ldt.h>
int get_thread_area(struct user_desc *u_info);
int set_thread_area(struct user_desc *u_info);
#elif defined __m68k__
int get_thread_area(void);
int set_thread_area(unsigned long tp);
#elif defined __mips__
int set_thread_area(unsigned long addr);
#endif
Note: There are no glibc wrappers for these system calls; see
NOTES.
$ grep -rn 'SYSCALL_DEFINE.*et_thread_area'
arch/csky/kernel/syscall.c:6:
SYSCALL_DEFINE1(set_thread_area, unsigned long, addr)
arch/mips/kernel/syscall.c:86:
SYSCALL_DEFINE1(set_thread_area, unsigned long, addr)
arch/x86/kernel/tls.c:191:
SYSCALL_DEFINE1(set_thread_area, struct user_desc __user *, u_info)
arch/x86/kernel/tls.c:243:
SYSCALL_DEFINE1(get_thread_area, struct user_desc __user *, u_info)
arch/x86/um/tls_32.c:277:
SYSCALL_DEFINE1(set_thread_area, struct user_desc __user *, user_desc)
arch/x86/um/tls_32.c:325:
SYSCALL_DEFINE1(get_thread_area, struct user_desc __user *, user_desc)
See kernel commit 4859bfca11c7d63d55175bcd85a75d6cee4b7184
I'd change
- #elif defined __mips__
+ #elif defined(__mips__ || __csky__)
and then change the rest of the text to add csky when appropriate.
Am I correct?
Thanks,
Alex
next reply other threads:[~2020-11-23 21:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 21:31 Alejandro Colomar (man-pages) [this message]
2020-11-23 21:48 ` set_thread_area.2: csky architecture undocumented Michael Kerrisk (man-pages)
2020-11-24 9:51 ` Michael Kerrisk (man-pages)
2020-11-24 12:07 ` Guo Ren
2020-11-26 12:16 ` Alejandro Colomar (mailing lists; readonly)
2023-10-14 23:20 ` Alejandro Colomar
2023-10-15 15:09 ` Guo Ren
2020-11-26 12:14 ` Alejandro Colomar (mailing lists; readonly)
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=014e670b-2a11-3deb-4e7e-bfe9defd8597@gmail.com \
--to=alx.manpages@gmail.com \
--cc=arnd@arndb.de \
--cc=guoren@kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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.