All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [bug report] locking/qrwlock, arm64: Move rwlock implementation over to qrwlocks causes CPU crashes/stalls when killing java processes
Date: Thu, 26 Apr 2018 09:33:14 +0100	[thread overview]
Message-ID: <20180426083313.GF27583@arm.com> (raw)
In-Reply-To: <CACgAJHwemngF4XgfTvWkjANYoWO-=HTKrJmJg8VonJPCR8ZxrQ@mail.gmail.com>

On Fri, Apr 13, 2018 at 08:32:24PM -0700, Tai Tri Nguyen wrote:
> I tried to remove wfe from cmpwait and still could reproduce the issue.

Hmm, then I'm afraid I'm not sure what else to suggest. You've obviously
got a lot of contention on the tasklist_lock on the exit path, but I can't
say why it's acting so slowly. If you get more information, please share
it!

Will

      reply	other threads:[~2018-04-26  8:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-12 17:10 [bug report] locking/qrwlock, arm64: Move rwlock implementation over to qrwlocks causes CPU crashes/stalls when killing java processes Tai Tri Nguyen
2018-04-12 17:24 ` Will Deacon
2018-04-12 17:49   ` Tai Tri Nguyen
2018-04-14  3:32     ` Tai Tri Nguyen
2018-04-26  8:33       ` Will Deacon [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=20180426083313.GF27583@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.