From: Arnd Bergmann <arnd@arndb.de>
To: Mao Han <han_mao@c-sky.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
c-sky_gcc_upstream@c-sky.com, gnu-csky@mentor.com
Subject: Re: [RFC PATCH V2 06/10] C-SKY: Linux Syscall Interface
Date: Sun, 15 Apr 2018 20:29:00 -0000 [thread overview]
Message-ID: <CAK8P3a24o951Vg7zNf4C6OZESwykyOvA+GWR7doJnsLX+2yuPA@mail.gmail.com> (raw)
In-Reply-To: <34f1011affb007e6cc1e4435ca0bd68f4ff4cfd4.1523169833.git.han_mao@c-sky.com>
On Sun, Apr 8, 2018 at 9:02 AM, Mao Han <han_mao@c-sky.com> wrote:
> diff --git a/sysdeps/unix/sysv/linux/csky/syscalls.list b/sysdeps/unix/sysv/linux/csky/syscalls.list
> new file mode 100644
> index 0000000..53cff69
> --- /dev/null
> +++ b/sysdeps/unix/sysv/linux/csky/syscalls.list
> @@ -0,0 +1,7 @@
> +# File name Caller Syscall name Args Strong name Weak names
> +
> +chown - chown32 i:sii __chown chown
> +cacheflush - cacheflush i:pii _flush_cache cacheflush
> +
> +prlimit64 EXTRA prlimit64 i:iipp prlimit64
> +fanotify_mark EXTRA fanotify_mark i:iiiiis fanotify_mark
I can understand the need for the cacheflush syscall here, but why do you need
to override those other three? Shouldn't the defaults be correct for new
architectures?
Arnd
next prev parent reply other threads:[~2018-04-15 20:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 7:03 [RFC PATCH V2 00/10] port C-SKY to glibc Mao Han
2018-04-08 7:03 ` [RFC PATCH V2 02/10] C-SKY: TLS support Mao Han
2018-04-17 20:50 ` Joseph Myers
2018-04-26 7:33 ` Mao Han
2018-04-26 16:00 ` Joseph Myers
2018-04-27 1:55 ` Guo Ren
2018-04-27 12:10 ` Joseph Myers
2018-04-29 8:49 ` Guo Ren
2018-04-08 7:03 ` [RFC PATCH V2 04/10] C-SKY: Hard Float Support Mao Han
2018-04-08 7:03 ` [RFC PATCH V2 06/10] C-SKY: Linux Syscall Interface Mao Han
2018-04-15 20:29 ` Arnd Bergmann [this message]
2018-04-16 5:55 ` Mao Han
2018-04-23 11:32 ` Adhemerval Zanella
2018-04-26 7:39 ` Mao Han
2018-04-08 7:03 ` [RFC PATCH V2 01/10] C-SKY: ABI related code Mao Han
2018-04-17 20:53 ` Joseph Myers
2018-04-26 7:27 ` Mao Han
2018-04-08 7:03 ` [RFC PATCH V2 03/10] C-SKY: Generic math Routines Mao Han
2018-04-08 7:03 ` [RFC PATCH V2 07/10] C-SKY: ABI Lists Mao Han
2018-04-09 22:25 ` Rafal Luzynski
2018-04-10 0:59 ` Mao Han
2018-04-08 7:03 ` [RFC PATCH V2 09/10] C-SKY: Linux Startup and Dynamic Loading Code Mao Han
2018-04-08 7:03 ` [RFC PATCH V2 05/10] C-SKY: Atomic and Locking Routines Mao Han
2018-04-08 7:03 ` [RFC PATCH V2 08/10] C-SKY: Build Infastructure Mao Han
2018-04-08 7:41 ` Andreas Schwab
2018-04-16 5:59 ` Mao Han
2018-04-17 20:54 ` Joseph Myers
2018-04-08 7:04 ` [RFC PATCH V2 10/10] C-SKY: Linux ABI Mao Han
2018-04-17 20:56 ` Joseph Myers
2018-04-08 7:51 ` [RFC PATCH V2 00/10] port C-SKY to glibc Florian Weimer
2018-04-08 8:29 ` Mao Han
2018-04-09 8:43 ` Florian Weimer
2018-04-09 9:05 ` Mao Han
2018-04-17 20:44 ` Joseph Myers
[not found] ` <20180426072022.GA14714@vmh-VirtualBox>
2018-04-26 11:45 ` Joseph Myers
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=CAK8P3a24o951Vg7zNf4C6OZESwykyOvA+GWR7doJnsLX+2yuPA@mail.gmail.com \
--to=arnd@arndb.de \
--cc=c-sky_gcc_upstream@c-sky.com \
--cc=gnu-csky@mentor.com \
--cc=han_mao@c-sky.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).