From: "André Almeida" <andrealmeid@collabora.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Florian Weimer <fweimer@redhat.com>,
malteskarupke@web.de, GNU C Library <libc-alpha@sourceware.org>,
Linux API <linux-api@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
dvhart@infradead.org, kernel@collabora.com,
krisman@collabora.com, pgriffais@valvesoftware.com
Subject: Re: [RFC 0/4] futex2: Add new futex interface
Date: Sat, 13 Jun 2020 16:25:46 -0300 [thread overview]
Message-ID: <c995708f-95e1-119b-c3ce-5fda27f24a4d@collabora.com> (raw)
In-Reply-To: <CAMe9rOqnBRzXv4xnhFvOgdVpDo0oRc1SYq38zcJWo9BPZseagg@mail.gmail.com>
Hello H.J.,
On 6/12/20 4:35 PM, H.J. Lu wrote:
> On Fri, Jun 12, 2020 at 11:53 AM André Almeida via Libc-alpha
> <libc-alpha@sourceware.org> wrote:
>> - Is expected to have a x32 ABI implementation as well? In the case of
>> wait and wake, we could use the same as x86_64 ABI. However, for the
>> waitv (aka wait on multiple futexes) we would need a proper x32 entry
>> since we are dealing with 32bit pointers.
>
> x32 should be able to use the same i386 compat systcall entry. Will it be
> problem?
>
Indeed, you are right. In the last iteration of this work, I had some
problems dealing with x32 ABI, but this new interface doesn't have the
same problem anymore. We can use the same sys_waitv_time64 interface for
both i368 and x32.
>>
>
> H.J.
>
Thanks,
André
next prev parent reply other threads:[~2020-06-13 19:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 18:51 André Almeida
2020-06-12 18:51 ` [RFC 1/4] " André Almeida
2020-06-12 18:51 ` [RFC 2/4] selftests: futex: Add futex2 wake/wait test André Almeida
2020-06-12 18:51 ` [RFC 3/4] selftests: futex: Add futex2 timeout test André Almeida
2020-06-12 18:51 ` [RFC 4/4] selftests: futex: Add futex2 wouldblock test André Almeida
2020-06-12 19:35 ` [RFC 0/4] futex2: Add new futex interface H.J. Lu
2020-06-13 19:25 ` André Almeida [this message]
2020-06-25 6:48 ` Arnd Bergmann
2020-06-25 14:38 ` André Almeida
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=c995708f-95e1-119b-c3ce-5fda27f24a4d@collabora.com \
--to=andrealmeid@collabora.com \
--cc=dvhart@infradead.org \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malteskarupke@web.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pgriffais@valvesoftware.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®