[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a2b0zun=b84d=LhrjrwLDiKh5_KgyZbBAjTz+40NZri=A@mail.gmail.com>
Date: Wed, 22 Dec 2021 15:00:16 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Arnd Bergmann <arnd@...db.de>
Cc: Guo Ren <guoren@...nel.org>, Palmer Dabbelt <palmer@...belt.com>,
Anup Patel <anup.patel@....com>,
gregkh <gregkh@...uxfoundation.org>,
liush <liush@...winnertech.com>, Wei Fu <wefu@...hat.com>,
Drew Fustini <drew@...gleboard.org>,
Wang Junqiang <wangjunqiang@...as.ac.cn>,
Wei Wu (吴伟) <lazyparser@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-riscv <linux-riscv@...ts.infradead.org>,
linux-csky@...r.kernel.org, Guo Ren <guoren@...ux.alibaba.com>
Subject: Re: [PATCH 05/13] riscv: compat: syscall: Add compat_sys_call_table implementation
On Wed, Dec 22, 2021 at 2:21 PM Arnd Bergmann <arnd@...db.de> wrote:
> On Wed, Dec 22, 2021 at 1:43 PM Guo Ren <guoren@...nel.org> wrote:
>
> Right, I think the patch would be a nice cleanup, but it appears that
> riscv is among the few architectures that have defined their own
> nonstandard mmap2() syscall after all, despite using the standard
> name for the entry point. Not sure how this slipped past my original
> review, but it certainly can't be changed now.
No, I misread, the calling conventions are fine after all, it's
just written in a rather odd way.
> Maybe leave it there and change the #ifdef to build mmap2 for both
> native rv32 and compat mode.
This bit still applies though, I don't think you need to add another
helper, just use the one that is already there.
Arnd
Powered by blists - more mailing lists