All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerrit Binnenmars <gerritbinnenmars@wanadoo.nl>
To: linux-rt-users@vger.kernel.org
Subject: Re: CONFIG_CRITICAL_IRQSOFF_TIMING
Date: Tue, 30 Oct 2007 21:52:01 +0100 (CET)	[thread overview]
Message-ID: <11542808.1611171193777521160.JavaMail.www@wwinf6102> (raw)

> Datum: 29/10/07 02:09 PM
> Van: "Steven Rostedt" 
> Aan: "Gerrit Binnenmars" 
> CC: linux-rt-users@vger.kernel.org
> Onderwerp : Re: CONFIG_CRITICAL_IRQSOFF_TIMING
> 
> 
> --
> On Sun, 28 Oct 2007, Gerrit Binnenmars wrote:
> 
> > Hello,
> >
> > Can someone send me a .config file that shows the options needed to get the interrupt off
> > timing values in preempt_max_latency, please. I only see a value of 0 in this file
> > I am using kernel 2.6.22.1 with the corresponding rt patch.
> >
> > Thanks in advance,
> 
> Make sure you have event trace and latency tracing as well as
> "Interrupts-off critical section latency timing".
> 
> Then you need to echo 0 > /proc/sys/kernel/preempt_max_latency.
> 
Hello Steve,

Thanks for your quick response, but the preempt_max_latency remains 0. Also the latency_hist shows no samples taken.
Can you or someone else have a look at the corresponding CONFIG options?

CONFIG_LTT_PROBE_LOCKING=m
# CONFIG_LTT_PROBE_STACK is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
CONFIG_ENABLE_MUST_CHECK=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_UNUSED_SYMBOLS=y
CONFIG_DEBUG_FS=y
# CONFIG_HEADERS_CHECK is not set
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_SHIRQ is not set
CONFIG_DETECT_SOFTLOCKUP=y
CONFIG_SCHED_DEBUG=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_TIMER_STATS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_PREEMPT=y
# CONFIG_DEBUG_RT_MUTEXES is not set
# CONFIG_RT_MUTEX_TESTER is not set
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_DEBUG_LOCK_ALLOC=y
# CONFIG_PROVE_LOCKING is not set
CONFIG_LOCKDEP=y
# CONFIG_LOCK_STAT is not set
# CONFIG_DEBUG_LOCKDEP is not set
CONFIG_TRACE_IRQFLAGS=y
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_LOCKING_API_SELFTESTS is not set
CONFIG_STACKTRACE=y
CONFIG_PREEMPT_TRACE=y
CONFIG_EVENT_TRACE=y
CONFIG_FUNCTION_TRACE=y
# CONFIG_WAKEUP_TIMING is not set
CONFIG_LATENCY_TRACE=y
# CONFIG_CRITICAL_PREEMPT_TIMING is not set
CONFIG_CRITICAL_IRQSOFF_TIMING=y
CONFIG_INTERRUPT_OFF_HIST=y
CONFIG_CRITICAL_TIMING=y
CONFIG_DEBUG_TRACE_IRQFLAGS=y
CONFIG_LATENCY_TIMING=y
CONFIG_CRITICAL_LATENCY_HIST=y
CONFIG_LATENCY_HIST=y
CONFIG_MCOUNT=y
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_VM is not set
# CONFIG_DEBUG_LIST is not set
CONFIG_FRAME_POINTER=y
CONFIG_FORCED_INLINING=y
# CONFIG_RCU_TORTURE_TEST is not set
# CONFIG_LKDTM is not set
# CONFIG_FAULT_INJECTION is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
CONFIG_DEBUG_RODATA=y
CONFIG_4KSTACKS=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_DOUBLEFAULT=y

Greetings Gerrit

> -- Steve
> 
> -
> 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
> 
> 

             reply	other threads:[~2007-10-30 20:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-30 20:52 Gerrit Binnenmars [this message]
2007-10-30 20:56 ` CONFIG_CRITICAL_IRQSOFF_TIMING Daniel Walker
2007-10-31  0:17 ` CONFIG_CRITICAL_IRQSOFF_TIMING Steven Rostedt
  -- strict thread matches above, loose matches on Subject: below --
2007-10-31 19:53 CONFIG_CRITICAL_IRQSOFF_TIMING Gerrit Binnenmars
2007-10-31 20:03 ` CONFIG_CRITICAL_IRQSOFF_TIMING Steven Rostedt
2007-10-30 21:46 CONFIG_CRITICAL_IRQSOFF_TIMING Gerrit Binnenmars
2007-10-30 21:26 CONFIG_CRITICAL_IRQSOFF_TIMING Gerrit Binnenmars
2007-10-30 21:32 ` CONFIG_CRITICAL_IRQSOFF_TIMING Daniel Walker
2007-10-30 21:09 CONFIG_CRITICAL_IRQSOFF_TIMING Gerrit Binnenmars
2007-10-30 21:05 ` CONFIG_CRITICAL_IRQSOFF_TIMING Daniel Walker
2007-10-28 13:00 CONFIG_CRITICAL_IRQSOFF_TIMING Gerrit Binnenmars
2007-10-29 13:08 ` CONFIG_CRITICAL_IRQSOFF_TIMING Steven Rostedt

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=11542808.1611171193777521160.JavaMail.www@wwinf6102 \
    --to=gerritbinnenmars@wanadoo.nl \
    --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 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.