[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 10/16] lib: General Linux RV64 syscall support.
From: |
Danny Milosavljevic |
Subject: |
Re: [PATCH 10/16] lib: General Linux RV64 syscall support. |
Date: |
Tue, 4 May 2021 13:31:56 +0200 |
Hi,
On Tue, 04 May 2021 11:05:13 +0000
"W. J. van der Laan" <laanwj@protonmail.com> wrote:
> On Sunday, May 2nd, 2021 at 5:48 PM, Jan Nieuwenhuizen <janneke@gnu.org>
> wrote:
>
> > Why use openAT here instead of open?
>
> On modern kernels, open() is a wrapper for openat(). It is provided for
> backwards compatibility with older binaries only.
>Newer architectures do not have these backwards compatibility constraints, so
>don't have that syscall at all. The only way to open is thus to use openat().
I see.
> Same for the other syscalls I've replaced in this patch. Doing it in some way
> is a necessity, unfortunately.
Which kernel version introduced openat() on architectures we want to use? (x86,
x86_64, arm, risc-v)
Is it old enough that it makes sense for us to have it as a minimum version
requirement?
I'm thinking of maybe just always using openat in mes on all architectures--if
that's possible without downsides.