Date: Wed, 11 Jan 2023 01:29:35 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Jake Freeland <jake@technologyfriends.net> Cc: freebsd-hackers@freebsd.org Subject: Re: Syscalls: eventfd and timerfd Message-ID: <Y73039Y2vMB7eN0v@kib.kiev.ua> In-Reply-To: <CAOgZAGbK5H=JtxY7MZKyyXa=i=CXbYtV4tCOvg6N-CRYjqJ4fQ@mail.gmail.com> References: <CAOgZAGbK5H=JtxY7MZKyyXa=i=CXbYtV4tCOvg6N-CRYjqJ4fQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 10, 2023 at 05:21:42PM -0600, Jake Freeland wrote: > Hi there, > > I am currently working on moving the linux_compat implementation of > timerfd (in sys/compat/linux/linux_event.c) into its own FreeBSD syscall > similar to what was done for eventfd. This is my first time implementing > a syscall, so I have been following the eventfd implementation as a > reference. I noticed that the eventfd syscall entries are absent from > sys/kern/syscalls.master and I am not sure why. Was eventfd never > formally added as a syscall entry or am I missing something? I was > planning on adding timerfd entries to syscalls.master, but now I am > unsure how to proceed. There is no eventfd(2) in FreeBSD. There is __specialfd(2) syscall #577, which dispatches based on type. The libc wrapper provides eventfd(3) API.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Y73039Y2vMB7eN0v>