From: naresh kamboju <naresh.kernel@gmail.com> To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com> Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>, ltt-dev@lists.casi.polymtl.ca, Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu> Subject: Re: LTTng 0.193 fixes RT kernel support Date: Tue, 23 Feb 2010 21:05:08 +0530 [thread overview] Message-ID: <f5a7b3811002230735p2eb90904l33e8090ade66fc14@mail.gmail.com> (raw) In-Reply-To: <20100223123016.GA12857@Krystal> On Tue, Feb 23, 2010 at 6:00 PM, Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote: > * naresh kamboju (naresh.kernel@gmail.com) wrote: >> On Mon, Feb 22, 2010 at 9:07 PM, naresh kamboju <naresh.kernel@gmail.com> wrote: >> > On Thu, Feb 18, 2010 at 4:38 AM, Mathieu Desnoyers >> > <mathieu.desnoyers@efficios.com> wrote: >> >> * naresh kamboju (naresh.kernel@gmail.com) wrote: >> >>> On Tue, Feb 16, 2010 at 10:35 PM, Mathieu Desnoyers <compudj@krystal.dyndns.org> wrote: >> >>> > Oh, right. Thanks for the explanation. I'll look into moving LTTng to a >> >>> > saner del_timer_sync() scheme to delete the timers. >> >> patch trace-clock-32-to-64-use-del-timer-sync.patch is causing above >> problem on SMP. >> >> with out this patch on SMP reported the previous bug as BUG: sleeping >> function called from invalid context at kernel/rtmutex.c:685 >> >> However, i'll investigate. > > Hrm, we should turn the arch/{arm/mach-omap2,x86/kernel}/trace-clock.c: > trace_clock_lock into a mutex, and kernel/trace/trace-clock-32-to-64.c: > synthetic_tsc_lock into a mutex too. I have modified kernel/trace/trace-clock-32-to-64.c spin_lock to mutex_lock to all the calls -static DEFINE_SPINLOCK(synthetic_tsc_lock); +static DEFINE_MUTEX(synthetic_tsc_lock); - spin_lock(&synthetic_tsc_lock); + mutex_lock(&synthetic_tsc_lock); for arch/{arm/mach-omap2/kernel}/trace-clock.c is already modified as above from the patch omap-trace-clock-fix-mutex.patch from LTTng patches 02-Feb-2009. this patch was prepared by you to fix BUG: sleeping function called from invalid context at kernel/mutex.c:207. Still reporting same bug at my end :-( let me try in all possible ways. Best regards Naresh Kamboju > > I used a spinlock previously on ARM because it was called from power > management resume, but now that the data structures touched by this code > path are per-cpu, this lock is not taken there, so it should be OK to > turn it into a mutex. > > Can you try that and tell me if that fixes your issues ? > > Thanks, > > Mathieu > >> >> Best regards, >> Naresh Kamboju >> >> Thanks, >> >> >> >> Mathieu >> >> >> >> -- >> >> Mathieu Desnoyers >> >> OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68 >> >> >> > >> >> _______________________________________________ >> ltt-dev mailing list >> ltt-dev@lists.casi.polymtl.ca >> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev >> > > -- > Mathieu Desnoyers > OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68 >
WARNING: multiple messages have this Message-ID (diff)
From: naresh kamboju <naresh.kernel@gmail.com> To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com> Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>, ltt-dev@lists.casi.polymtl.ca, Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu> Subject: Re: LTTng 0.193 fixes RT kernel support Date: Tue, 23 Feb 2010 21:05:08 +0530 [thread overview] Message-ID: <f5a7b3811002230735p2eb90904l33e8090ade66fc14@mail.gmail.com> (raw) In-Reply-To: <20100223123016.GA12857@Krystal> On Tue, Feb 23, 2010 at 6:00 PM, Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote: > * naresh kamboju (naresh.kernel@gmail.com) wrote: >> On Mon, Feb 22, 2010 at 9:07 PM, naresh kamboju <naresh.kernel@gmail.com> wrote: >> > On Thu, Feb 18, 2010 at 4:38 AM, Mathieu Desnoyers >> > <mathieu.desnoyers@efficios.com> wrote: >> >> * naresh kamboju (naresh.kernel@gmail.com) wrote: >> >>> On Tue, Feb 16, 2010 at 10:35 PM, Mathieu Desnoyers <compudj@krystal.dyndns.org> wrote: >> >>> > Oh, right. Thanks for the explanation. I'll look into moving LTTng to a >> >>> > saner del_timer_sync() scheme to delete the timers. >> >> patch trace-clock-32-to-64-use-del-timer-sync.patch is causing above >> problem on SMP. >> >> with out this patch on SMP reported the previous bug as BUG: sleeping >> function called from invalid context at kernel/rtmutex.c:685 >> >> However, i'll investigate. > > Hrm, we should turn the arch/{arm/mach-omap2,x86/kernel}/trace-clock.c: > trace_clock_lock into a mutex, and kernel/trace/trace-clock-32-to-64.c: > synthetic_tsc_lock into a mutex too. I have modified kernel/trace/trace-clock-32-to-64.c spin_lock to mutex_lock to all the calls -static DEFINE_SPINLOCK(synthetic_tsc_lock); +static DEFINE_MUTEX(synthetic_tsc_lock); - spin_lock(&synthetic_tsc_lock); + mutex_lock(&synthetic_tsc_lock); for arch/{arm/mach-omap2/kernel}/trace-clock.c is already modified as above from the patch omap-trace-clock-fix-mutex.patch from LTTng patches 02-Feb-2009. this patch was prepared by you to fix BUG: sleeping function called from invalid context at kernel/mutex.c:207. Still reporting same bug at my end :-( let me try in all possible ways. Best regards Naresh Kamboju > > I used a spinlock previously on ARM because it was called from power > management resume, but now that the data structures touched by this code > path are per-cpu, this lock is not taken there, so it should be OK to > turn it into a mutex. > > Can you try that and tell me if that fixes your issues ? > > Thanks, > > Mathieu > >> >> Best regards, >> Naresh Kamboju >> >> Thanks, >> >> >> >> Mathieu >> >> >> >> -- >> >> Mathieu Desnoyers >> >> OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68 >> >> >> > >> >> _______________________________________________ >> ltt-dev mailing list >> ltt-dev@lists.casi.polymtl.ca >> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev >> > > -- > Mathieu Desnoyers > OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68 > -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-02-23 15:35 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-02-16 15:17 LTTng0.158 Linux-2629-RT kernel BUG: sleeping function called from invalid context at kernel/rtmutex.c:685 naresh kamboju 2010-02-16 16:24 ` Steven Rostedt 2010-02-16 16:30 ` Thomas Gleixner 2010-02-16 16:47 ` [ltt-dev] " Mathieu Desnoyers 2010-02-16 17:01 ` Thomas Gleixner 2010-02-16 17:05 ` Mathieu Desnoyers 2010-02-17 10:36 ` naresh kamboju 2010-02-17 10:36 ` naresh kamboju 2010-02-17 23:08 ` [ltt-dev] LTTng 0.193 fixes RT kernel support Mathieu Desnoyers 2010-02-17 23:08 ` Mathieu Desnoyers 2010-02-22 15:37 ` [ltt-dev] " naresh kamboju 2010-02-22 15:37 ` naresh kamboju 2010-02-23 11:29 ` naresh kamboju 2010-02-23 11:29 ` naresh kamboju 2010-02-23 12:30 ` Mathieu Desnoyers 2010-02-23 15:35 ` naresh kamboju [this message] 2010-02-23 15:35 ` naresh kamboju 2010-02-23 15:52 ` Mathieu Desnoyers 2010-02-24 16:01 ` naresh kamboju
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=f5a7b3811002230735p2eb90904l33e8090ade66fc14@mail.gmail.com \ --to=naresh.kernel@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rt-users@vger.kernel.org \ --cc=ltt-dev@lists.casi.polymtl.ca \ --cc=mathieu.desnoyers@efficios.com \ --cc=mingo@elte.hu \ --cc=rostedt@goodmis.org \ --cc=tglx@linutronix.de \ /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.