-rc5-rt3 - IRQoff tracing numbers still reflect timer? (AMD64?)

[Mark Knecht <markknecht@gmail.com>]

Hi all,
   I want to ensure I understand the status of the kernel right now.
When I enable

[*] Interrupts-off critical section latency timing

I immediately see values as shown below. I think that this is the
timer, which I have set to 1000HZ and not a rela latency. Is that
correct?

   If my understanding is correct then is there someone that can spend
some time and look into this? Is this an x86_64 issue only?

Thanks,
Mark


( softirq-timer/0-3    |#0): new 998 us maximum-latency critical section.
 => started at timestamp 286541291: <acpi_processor_idle+0x20/0x379>
 =>   ended at timestamp 286542289: <thread_return+0xb5/0x11a>

Call Trace:<ffffffff8014e19c>{check_critical_timing+492}
<ffffffff8014e5f5>{sub_preempt_count_ti+133}
       <ffffffff803ff43c>{thread_return+70}
<ffffffff803ff4ab>{thread_return+181}
       <ffffffff803ff615>{schedule+261} <ffffffff801379aa>{ksoftirqd+138}
       <ffffffff80137920>{ksoftirqd+0} <ffffffff80147bfd>{kthread+205}
       <ffffffff8010e70e>{child_rip+8} <ffffffff80147b30>{kthread+0}
       <ffffffff8010e706>{child_rip+0}
---------------------------
| preempt count: 00000001 ]
| 1-level deep critical section nesting:
----------------------------------------
.. [<ffffffff803feef8>] .... __schedule+0xb8/0x5b6
.....[<00000000>] ..   ( <= _stext+0x7feff0e8/0xe8)

 =>   dump-end timestamp 286542378

lightning ~ #
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/