From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: David Abdurachmanov <david.abdurachmanov@gmail.com>,
palmer@sifive.com, aou@eecs.berkeley.edu,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Guenter Roeck <linux@roeck-us.net>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] riscv: add asm/unistd.h UAPI header
Date: Mon, 5 Nov 2018 17:02:59 +0100 [thread overview]
Message-ID: <10c6f266-12ce-9f1a-5859-52873ff329f1@linaro.org> (raw)
Message-ID: <20181105160259.wAjrv-NdKJY3aJ4DBvMMtzlueIcmQY_hwJnZM9xK8oo@z> (raw)
In-Reply-To: <20181105142602.25750-1-david.abdurachmanov@gmail.com>
W dniu 05.11.2018 o 15:26, David Abdurachmanov pisze:
> Marcin Juszkiewicz reported issues while generating syscall table for riscv
> using 4.20-rc1. The patch refactors our unistd.h files to match some other
> architectures.
>
> - Add asm/unistd.h UAPI header, which has __ARCH_WANT_NEW_STAT
> - Remove asm/syscalls.h UAPI header and merge to asm/unistd.h
> - Adjust kernel asm/unistd.h
>
> So now asm/unistd.h UAPI header should show all syscalls for riscv.
>
> Before this, Makefile simply put `#include <asm-generic/unistd.h>` into
> generated asm/unistd.h UAPI header thus user didn't see:
>
> - __NR_riscv_flush_icache
> - __NR_newfstatat
> - __NR_fstat
>
> which are supported by riscv kernel.
Tested-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
With patch applied I got proper syscall data:
fstat 80
newfstatat 79
riscv_flush_icache 259
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2018-11-05 16:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 14:26 [PATCH] riscv: add asm/unistd.h UAPI header David Abdurachmanov
2018-11-05 14:26 ` David Abdurachmanov
2018-11-05 14:43 ` David Abdurachmanov
2018-11-05 14:43 ` David Abdurachmanov
2018-11-05 16:02 ` Marcin Juszkiewicz [this message]
2018-11-05 16:02 ` Marcin Juszkiewicz
2018-11-05 20:56 ` Arnd Bergmann
2018-11-05 20:56 ` Arnd Bergmann
2018-11-07 0:08 ` Palmer Dabbelt
2018-11-07 0:08 ` Palmer Dabbelt
2018-11-07 18:30 ` David Abdurachmanov
2018-11-07 18:30 ` David Abdurachmanov
2018-11-07 21:09 ` Arnd Bergmann
2018-11-07 21:09 ` Arnd Bergmann
2018-11-08 2:10 ` Palmer Dabbelt
2018-11-08 2:10 ` Palmer Dabbelt
2018-11-08 10:30 ` Arnd Bergmann
2018-11-08 10:30 ` Arnd Bergmann
2018-11-08 16:57 ` Palmer Dabbelt
2018-11-08 16:57 ` Palmer Dabbelt
2018-11-08 10:38 ` David Abdurachmanov
2018-11-08 10:38 ` David Abdurachmanov
2018-11-08 16:57 ` Palmer Dabbelt
2018-11-08 16:57 ` Palmer Dabbelt
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=10c6f266-12ce-9f1a-5859-52873ff329f1@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=david.abdurachmanov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=palmer@sifive.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 NNTP newsgroup(s).