linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Jiri Slaby <jslaby@suse.cz>, Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: Kernel 4.15 lost set_robust_list support on POWER 9
Date: Mon, 5 Feb 2018 13:59:19 +0100	[thread overview]
Message-ID: <75d2a8f1-6ca4-e9ca-9900-9fbd48f3c1ae@redhat.com> (raw)
In-Reply-To: <3ef0c599-0285-e77a-c002-e21152823fb8@redhat.com>

On 02/05/2018 01:48 PM, Florian Weimer wrote:
> I get this:
> 
> 7041  set_robust_list(0x7fff93dc3980, 24) = -1 ENOSYS (Function not 
> implemented)
> 
> The system call works on 4.14.  Looks like the probing for 
> futex_cmpxchg_enabled goes wrong.
> 
> Sorry, I have no idea where to start digging.  I don't see anything 
> obvious in dmesg.
> 
> I'm trying to revert
> 
> commit 30d6e0a4190d37740e9447e4e4815f06992dd8c3
> Author: Jiri Slaby <jslaby@suse.cz>
> Date:   Thu Aug 24 09:31:05 2017 +0200
> 
>      futex: Remove duplicated code and fix undefined behaviour
> 
> to see if it makes a difference

Never mind, it must be something else because that commit is in 4.14, 
but set_robust_list is still working there.  (Let's hope that the 
probing doesn't fail randomly …)

Thanks,
Florian

  reply	other threads:[~2018-02-05 12:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 12:48 Kernel 4.15 lost set_robust_list support on POWER 9 Florian Weimer
2018-02-05 12:59 ` Florian Weimer [this message]
2018-02-05 21:14 ` Mauricio Faria de Oliveira
2018-02-05 21:55   ` Benjamin Herrenschmidt
2018-02-06  1:06     ` Nicholas Piggin
2018-02-06  3:17       ` Aneesh Kumar K.V
2018-02-06  4:29         ` Nicholas Piggin
2018-02-06 13:17       ` Mauricio Faria de Oliveira

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=75d2a8f1-6ca4-e9ca-9900-9fbd48f3c1ae@redhat.com \
    --to=fweimer@redhat.com \
    --cc=jslaby@suse.cz \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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;
as well as URLs for NNTP newsgroup(s).