From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Yang Shi <yang.shi@linaro.org>
Cc: rostedt@goodmis.org, catalin.marinas@arm.com,
will.deacon@arm.com, linux-kernel@vger.kernel.org,
linux-rt-users@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH] arm64: replace read_lock to rcu lock in call_step_hook
Date: Tue, 9 Feb 2016 10:02:19 +0100 [thread overview]
Message-ID: <20160209090219.GA13035@linutronix.de> (raw)
In-Reply-To: <1454971764-30720-1-git-send-email-yang.shi@linaro.org>
* Yang Shi | 2016-02-08 14:49:24 [-0800]:
>BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:917
…
>This issue is similar with 62c6c61("arm64: replace read_lock to rcu lock in
>call_break_hook"), but comes to single_step_handler.
>
>This also solves kgdbts boot test silent hang issue on 4.4 -rt kernel.
I am going to apply this for -RT.
Sebastian
WARNING: multiple messages have this Message-ID (diff)
From: bigeasy@linutronix.de (Sebastian Andrzej Siewior)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: replace read_lock to rcu lock in call_step_hook
Date: Tue, 9 Feb 2016 10:02:19 +0100 [thread overview]
Message-ID: <20160209090219.GA13035@linutronix.de> (raw)
In-Reply-To: <1454971764-30720-1-git-send-email-yang.shi@linaro.org>
* Yang Shi | 2016-02-08 14:49:24 [-0800]:
>BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:917
?
>This issue is similar with 62c6c61("arm64: replace read_lock to rcu lock in
>call_break_hook"), but comes to single_step_handler.
>
>This also solves kgdbts boot test silent hang issue on 4.4 -rt kernel.
I am going to apply this for -RT.
Sebastian
next prev parent reply other threads:[~2016-02-09 9:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 22:49 [PATCH] arm64: replace read_lock to rcu lock in call_step_hook Yang Shi
2016-02-08 22:49 ` Yang Shi
2016-02-09 9:02 ` Sebastian Andrzej Siewior [this message]
2016-02-09 9:02 ` Sebastian Andrzej Siewior
2016-02-09 14:54 ` Will Deacon
2016-02-09 14:54 ` Will Deacon
2016-02-09 15:07 ` Steven Rostedt
2016-02-09 15:07 ` Steven Rostedt
2016-02-09 16:04 ` Will Deacon
2016-02-09 16:04 ` Will Deacon
2016-02-09 16:08 ` Steven Rostedt
2016-02-09 16:08 ` Steven Rostedt
2016-02-09 16:24 ` Catalin Marinas
2016-02-09 16:24 ` Catalin Marinas
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=20160209090219.GA13035@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=will.deacon@arm.com \
--cc=yang.shi@linaro.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.