From: guoren@kernel.org
To: guoren@kernel.org, arnd@arndb.de, alx@kernel.org,
mtk.manpages@gmail.com, alx.manpages@gmail.com
Cc: linux-man@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-csky@vger.kernel.org, Guo Ren <guoren@linux.alibaba.com>
Subject: [PATCH] set_thread_area.2: Add C-SKY document
Date: Sun, 15 Oct 2023 11:07:32 -0400 [thread overview]
Message-ID: <20231015150732.1991997-1-guoren@kernel.org> (raw)
From: Guo Ren <guoren@linux.alibaba.com>
C-SKY only needs set_thread_area, no need for get_thread_area, the
same as MIPS.
Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
Signed-off-by: Guo Ren <guoren@kernel.org>
---
man2/set_thread_area.2 | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/man2/set_thread_area.2 b/man2/set_thread_area.2
index 02f65e0418f2..c43a92eb447a 100644
--- a/man2/set_thread_area.2
+++ b/man2/set_thread_area.2
@@ -26,7 +26,7 @@ Standard C library
.B "int syscall(SYS_get_thread_area);"
.BI "int syscall(SYS_set_thread_area, unsigned long " tp );
.PP
-.B #elif defined __mips__
+.B #elif defined(__mips__ || defined __csky__)
.PP
.BI "int syscall(SYS_set_thread_area, unsigned long " addr );
.PP
@@ -42,17 +42,17 @@ These calls provide architecture-specific support for a thread-local storage
implementation.
At the moment,
.BR set_thread_area ()
-is available on m68k, MIPS, and x86 (both 32-bit and 64-bit variants);
+is available on m68k, MIPS, C-SKY, and x86 (both 32-bit and 64-bit variants);
.BR get_thread_area ()
is available on m68k and x86.
.PP
-On m68k and MIPS,
+On m68k, MIPS and C-SKY,
.BR set_thread_area ()
allows storing an arbitrary pointer (provided in the
.B tp
argument on m68k and in the
.B addr
-argument on MIPS)
+argument on MIPS and C-SKY)
in the kernel data structure associated with the calling thread;
this pointer can later be retrieved using
.BR get_thread_area ()
@@ -139,7 +139,7 @@ return 0 on success, and \-1 on failure, with
.I errno
set to indicate the error.
.PP
-On MIPS and m68k,
+On C-SKY, MIPS and m68k,
.BR set_thread_area ()
always returns 0.
On m68k,
--
2.36.1
next reply other threads:[~2023-10-15 15:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 15:07 guoren [this message]
2023-10-15 18:00 ` [PATCH] set_thread_area.2: Add C-SKY document Alejandro Colomar
2023-10-16 0:53 ` Guo Ren
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=20231015150732.1991997-1-guoren@kernel.org \
--to=guoren@kernel.org \
--cc=alx.manpages@gmail.com \
--cc=alx@kernel.org \
--cc=arnd@arndb.de \
--cc=guoren@linux.alibaba.com \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).