From: Sujit K M <sjt.kar@gmail.com>
To: Maksym Parkachov <lazy.gopher@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: beagleboard RT problem
Date: Mon, 14 Jun 2010 16:41:49 +0530 [thread overview]
Message-ID: <AANLkTimtwlNkt3Fc4FP0Da5YYmCNnIDHxSATerps7dRd@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinztcUB6WVJKaZlwPuBrq7nZYN_ROdCC6ZNtRJf@mail.gmail.com>
> But, generally, is there way to trace what happens in kernel,
> something in /proc or /sys ?
> Do I need to switch tracing in configuration ?
I think you should look at kernel module level of Tracing. You could
have tracing with something like cyclic-test.
Also some tracing with options like # CONFIG_PREEMPT_RCU_TRACE is not set.
>
> Thanks,
> Maksym.
>
> On 14 June 2010 11:44, Sujit K M <sjt.kar@gmail.com> wrote:
>>> CONFIG_PREEMPT_RCU=y
>>> # CONFIG_PREEMPT_RCU_TRACE is not set
>>
>> Why is RCU being set to y?
>>
>>> # CONFIG_PREEMPT_NONE is not set
>>> # CONFIG_PREEMPT_VOLUNTARY is not set
>>> # CONFIG_PREEMPT_DESKTOP is not set
>>
>> Fine.
>>
>>> CONFIG_PREEMPT_RT=y
>>
>> This is correct.
>>
>>> CONFIG_PREEMPT=y
>>> CONFIG_PREEMPT_SOFTIRQS=y
>>> CONFIG_PREEMPT_HARDIRQS=y
>>
>> I think this part is susceptible.
>>
>> Thanks,
>> Sujit
>>
>
--
-- Sujit K M
blog(http://kmsujit.blogspot.com/)
next prev parent reply other threads:[~2010-06-14 11:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 8:32 beagleboard RT problem Maksym Parkachov
2010-06-14 9:44 ` Sujit K M
2010-06-14 11:02 ` Maksym Parkachov
2010-06-14 11:11 ` Sujit K M [this message]
2010-06-14 11:05 ` John Kacur
2010-06-14 11:09 ` Sujit K M
2010-06-14 11:23 ` John Kacur
2010-06-14 11:27 ` Sven-Thorsten Dietrich
2010-06-15 7:34 ` Maksym Parkachov
2010-06-20 15:43 ` Maksym Parkachov
2010-06-21 10:34 ` Sujit K M
2010-06-22 7:50 ` Maksym Parkachov
2010-06-22 8:11 ` Sujit K M
2010-06-22 14:46 ` Sven-Thorsten Dietrich
2010-06-23 8:51 ` Chatterjee, Amit
2010-06-23 9:45 ` Maksym Parkachov
2010-08-08 9:41 ` Maksym Parkachov
2010-08-08 12:27 ` Maksym Parkachov
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=AANLkTimtwlNkt3Fc4FP0Da5YYmCNnIDHxSATerps7dRd@mail.gmail.com \
--to=sjt.kar@gmail.com \
--cc=lazy.gopher@gmail.com \
--cc=linux-rt-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).