From: Stephen Boyd <sboyd@codeaurora.org> To: John Stultz <john.stultz@linaro.org>, LKML <linux-kernel@vger.kernel.org> Cc: "Krzysztof Hałasa" <khalasa@piap.pl>, "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>, "Willy Tarreau" <w@1wt.eu>, "Ingo Molnar" <mingo@kernel.org>, "Peter Zijlstra" <peterz@infradead.org>, "Linus Torvalds" <torvalds@linux-foundation.org>, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 2/2] sched_clock: Disable seqlock lockdep usage in sched_clock Date: Thu, 02 Jan 2014 16:46:20 -0800 [thread overview] Message-ID: <52C6085C.3070206@codeaurora.org> (raw) In-Reply-To: <1388704274-5278-2-git-send-email-john.stultz@linaro.org> On 01/02/14 15:11, John Stultz wrote: > Unforunately the seqlock lockdep enablmenet can't be used s/Unforunately/Unfortunately/ s/enablmenet/enablement/ > in sched_clock, since the lockdep infrastructure eventually > calls into sched_clock, which causes a deadlock. > > Thus, this patch changes all generic sched_clock usage > to use the raw_* methods. > > Cc: Krzysztof Hałasa <khalasa@piap.pl> > Cc: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> > Cc: Willy Tarreau <w@1wt.eu> > Cc: Ingo Molnar <mingo@kernel.org>, > Cc: Peter Zijlstra <peterz@infradead.org> > Cc: Stephen Boyd <sboyd@codeaurora.org> > Cc: Linus Torvalds <torvalds@linux-foundation.org> > Cc: linux-arm-kernel@lists.infradead.org > Reported-by: Krzysztof Hałasa <khalasa@piap.pl> > Signed-off-by: John Stultz <john.stultz@linaro.org> Reviewed-by: Stephen Boyd <sboyd@codeaurora.org> -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 2/2] sched_clock: Disable seqlock lockdep usage in sched_clock Date: Thu, 02 Jan 2014 16:46:20 -0800 [thread overview] Message-ID: <52C6085C.3070206@codeaurora.org> (raw) In-Reply-To: <1388704274-5278-2-git-send-email-john.stultz@linaro.org> On 01/02/14 15:11, John Stultz wrote: > Unforunately the seqlock lockdep enablmenet can't be used s/Unforunately/Unfortunately/ s/enablmenet/enablement/ > in sched_clock, since the lockdep infrastructure eventually > calls into sched_clock, which causes a deadlock. > > Thus, this patch changes all generic sched_clock usage > to use the raw_* methods. > > Cc: Krzysztof Ha?asa <khalasa@piap.pl> > Cc: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de> > Cc: Willy Tarreau <w@1wt.eu> > Cc: Ingo Molnar <mingo@kernel.org>, > Cc: Peter Zijlstra <peterz@infradead.org> > Cc: Stephen Boyd <sboyd@codeaurora.org> > Cc: Linus Torvalds <torvalds@linux-foundation.org> > Cc: linux-arm-kernel at lists.infradead.org > Reported-by: Krzysztof Ha?asa <khalasa@piap.pl> > Signed-off-by: John Stultz <john.stultz@linaro.org> Reviewed-by: Stephen Boyd <sboyd@codeaurora.org> -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2014-01-03 0:46 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-31 10:37 v3.13-rc6+ regression (ARM board) Krzysztof Hałasa 2013-12-31 10:37 ` Krzysztof Hałasa 2013-12-31 10:45 ` Willy Tarreau 2013-12-31 10:45 ` Willy Tarreau 2014-01-02 10:02 ` Krzysztof Hałasa 2014-01-02 10:02 ` Krzysztof Hałasa 2014-01-02 10:14 ` Uwe Kleine-König 2014-01-02 10:14 ` Uwe Kleine-König 2014-01-02 12:07 ` Krzysztof Hałasa 2014-01-02 12:07 ` Krzysztof Hałasa 2014-01-02 19:38 ` Linus Torvalds 2014-01-02 19:38 ` Linus Torvalds 2014-01-02 20:03 ` John Stultz 2014-01-02 20:03 ` John Stultz 2014-01-02 20:30 ` John Stultz 2014-01-02 20:30 ` John Stultz 2014-01-02 20:42 ` Stephen Boyd 2014-01-02 20:42 ` Stephen Boyd 2014-01-02 20:52 ` John Stultz 2014-01-02 20:52 ` John Stultz 2014-01-02 20:43 ` Linus Torvalds 2014-01-02 20:43 ` Linus Torvalds 2014-01-02 21:34 ` John Stultz 2014-01-02 21:34 ` John Stultz 2014-01-02 21:54 ` [PATCH] sched_clock: Disable seqlock lockdep usage in sched_clock John Stultz 2014-01-02 21:54 ` John Stultz 2014-01-02 22:15 ` Linus Torvalds 2014-01-02 22:15 ` Linus Torvalds 2014-01-02 22:21 ` John Stultz 2014-01-02 22:21 ` John Stultz 2014-01-02 23:11 ` [PATCH 1/2] seqlock: Use raw_ prefix instead of _no_lockdep John Stultz 2014-01-02 23:11 ` John Stultz 2014-01-02 23:11 ` [PATCH 2/2] sched_clock: Disable seqlock lockdep usage in sched_clock John Stultz 2014-01-02 23:11 ` John Stultz 2014-01-03 0:46 ` Stephen Boyd [this message] 2014-01-03 0:46 ` Stephen Boyd 2014-01-03 6:05 ` Krzysztof Hałasa 2014-01-03 6:05 ` Krzysztof Hałasa 2014-01-12 18:42 ` [tip:core/urgent] sched_clock: Disable seqlock lockdep usage in sched_clock() tip-bot for John Stultz 2014-01-14 19:18 ` John Stultz 2014-01-15 6:38 ` Ingo Molnar 2014-01-03 0:46 ` [PATCH 1/2] seqlock: Use raw_ prefix instead of _no_lockdep Stephen Boyd 2014-01-03 0:46 ` Stephen Boyd 2014-01-03 0:50 ` Linus Torvalds 2014-01-03 0:50 ` Linus Torvalds 2014-01-04 0:28 ` John Stultz 2014-01-04 0:28 ` John Stultz 2014-01-06 10:10 ` Peter Zijlstra 2014-01-06 10:10 ` Peter Zijlstra 2014-01-12 18:42 ` [tip:core/urgent] " tip-bot for John Stultz 2014-01-03 6:01 ` v3.13-rc6+ regression (ARM board) Krzysztof Hałasa 2014-01-03 6:01 ` Krzysztof Hałasa
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=52C6085C.3070206@codeaurora.org \ --to=sboyd@codeaurora.org \ --cc=john.stultz@linaro.org \ --cc=khalasa@piap.pl \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=peterz@infradead.org \ --cc=torvalds@linux-foundation.org \ --cc=u.kleine-koenig@pengutronix.de \ --cc=w@1wt.eu \ /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: linkBe 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.