From: Jet Chen <jet.chen@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
"abd38155f8293923de5953cc063f9e2d7ecb3f04.1396679170.git.viresh.kumar@linaro.org"
<abd38155f8293923de5953cc063f9e2d7ecb3f04.1396679170.git.viresh.kumar@linaro.org>
Cc: "Wu, Fengguang" <fengguang.wu@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [clocksource] INFO: possible irq lock inversion dependency detected
Date: Wed, 09 Apr 2014 09:21:39 +0800 [thread overview]
Message-ID: <5344A0A3.9030909@intel.com> (raw)
In-Reply-To: <CAKohpomRb1pix3zQWeY0mKkfuikUtR6w+PUOTzQV_hngPrpHRw@mail.gmail.com>
On 04/08/2014 01:21 PM, Viresh Kumar wrote:
> On 8 April 2014 09:29, Jet Chen <jet.chen@intel.com> wrote:
>> (Sorry for previous bad format email)
>> Your patch on my testing branch in LKP system:
>> git://bee.sh.intel.com/git/tchen37/linux.git timer_debug3 got the below
>> dmesg.
>> FYI, I applied your patch on the top of commit
>> 6378cb51af5f4743db0dcb3cbcf862eac5908754 - timer: don't migrate pinned
>> timers.
>
> Hi Jet,
>
> Thanks for your efforts. It looks like we must use spin_lock_irqsave() here.
> And that's all we need to fix this issue..
>
spin_lock_irqsave() does fix this issue.
Tested-by: Jet Chen <jet.chen@intel.com>
> To get the right order in which patches must be applied (obviously with the
> updates I have), please pick this branch:
>
> git://git.linaro.org/people/viresh.kumar/linux.git isolate-cpusets
>
> I hope this fixes the issues you were getting.
>
next prev parent reply other threads:[~2014-04-09 1:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 3:59 Jet Chen
2014-04-08 5:21 ` Viresh Kumar
2014-04-09 1:21 ` Jet Chen [this message]
2014-04-09 4:25 ` Viresh Kumar
2014-04-09 4:34 ` Jet Chen
2014-04-09 4:40 ` Viresh Kumar
2014-04-09 4:42 ` Jet Chen
-- strict thread matches above, loose matches on Subject: below --
2014-04-07 14:57 Jet Chen
2014-04-08 2:55 ` Fengguang Wu
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=5344A0A3.9030909@intel.com \
--to=jet.chen@intel.com \
--cc=abd38155f8293923de5953cc063f9e2d7ecb3f04.1396679170.git.viresh.kumar@linaro.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viresh.kumar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome