From: Rich Felker <dalias@libc.org>
To: Alexander Revin <lyssdod@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: Re: musl on a different syscall layer?
Date: Tue, 14 Aug 2018 20:45:26 -0400 [thread overview]
Message-ID: <20180815004526.GE1878@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAM+zL-dNw10LZHrs3LFDpfV3pPHNNXTcgtMfKxi7jSmeeF4i=Q@mail.gmail.com>
On Tue, Aug 14, 2018 at 01:12:56AM +0200, Alexander Revin wrote:
> > On Wed, Sep 17, 2014 at 7:02 PM, <u-wsnj@...ey.se> wrote:
> >> On Wed, Sep 17, 2014 at 01:53:46PM -0400, Rich Felker wrote:
> >>> The main requirement is having equivalent functionality available. On
> >>> the BSD targets I've asked BSD folks about, there's supposedly no
> >>> equivalent of futex except inthe Linux compat layer, which is pretty
> >>> much a show-stopper unless/until it can be remedied. clone is a big
> >>> unknown to me too. The other big potential problem is if the native
> >>> syscall API requires a stack to communicate with the kernel (one or
> >>> more BSDs require this, IIRC), since at least __unmapself needs to be
> >>> able to call SYS_munmap and SYS_exit without a stack.
> >>
> >> Oh I see.
> >>
> >> This means "not much to hope for" (pity but good to know).
>
> > I don't think NetBSD uses the stack for syscalls on any common
> > architecture, maybe on some of the obscure ones, but maybe you don't
> > want to support them.
> >
> > Adding futex support to NetBSD would be an interesting project; it is
> > not in the compat layer at present either, so that is a good reason to
> > add it. NetBSD is pretty friendly...
> >
> > Justin (justin@...bsd.org)
>
> Hi guys, sorry for reviving a dead thread, but do you know if things
> has changed ever since? I'm asking also because it would be nice to
> unify efforts of porting musl to another archs - for example, openrisc
> or m68k - though there're ports for both Linux and NetBSD, libc
> support is kind of scattered over large codebase.
I'm not aware of anything more on the NetBSD side.
Note that "syscalls using stack" is no longer a show-stopper for musl.
There's a portable, albeit less efficient, version of __unmapself that
switches to a shared stack protected by a lock (with the magic exit
futex automatically unlocking it atomically with thread termination).
But this depends on that compat functionality or equivalent.
Rich
prev parent reply other threads:[~2018-08-15 0:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 23:12 Alexander Revin
2018-08-15 0:45 ` Rich Felker [this message]
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=20180815004526.GE1878@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=lyssdod@gmail.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).