On Thursday 04 August 2005 15:19, Steven Rostedt wrote:
> On Thu, 2005-08-04 at 14:59 +0200, Borislav Petkov wrote:
> > where you see the deltas between the printk's printed once the tsc timer
> > is initialized as opposed to the first bootlog where you see all times
> > relative to a single point in time. The python script
> > <scripts/show_delta> in the kernel source converts between these two
> > representations but there's a pretty simple solution IMHO to make
> > PRINTK_TIME uniform and independent from the used timer. The one liner is
> > against 2.6.12.3.
> >
> > After applying it, printk timing looks like this:
> >
> > <snip>
> > [ 0.000000] Detected 1500.132 MHz processor.
> > [ 0.000000] Using pmtmr for high-res timesource
> > [ 0.000000] Console: colour VGA+ 80x25
> > [ 1.890000] Dentry cache hash table entries: 131072 (order: 7, 524288
> > bytes)
> > [ 1.891000] Inode-cache hash table entries: 65536 (order: 6, 262144
> > bytes) [ 1.906000] Memory: 513756k/523520k available (2839k kernel
> > code, 9276k reserved, 1148k data, 152k init, 0k highmem)
> > [ 1.906000] Checking if this processor honours the WP bit even in
> > supervisor mode... Ok.
> > [ 1.906000] Calibrating delay loop... 2973.69 BogoMIPS (lpj=1486848)
> > [ 1.928000] Security Framework v1.0.0 initialized
> > </snip>
>
> But if you are debugging problems with jiffies wrapping, wouldn't you
> want to see the jiffies unmodified? I understand your point, but the
> tsc output (which I do prefer) seems to only be for the tsc (on x86),
> and all else use jiffies (haven't looked at other archs). So debugging a
> problem with jiffy wrap*, one would need to use something other than the
> tsc, and then they would see the time the wrap occurred.
>
> Also, the big number stands out more than the 3 zeros, so when I see
> that, I know right away to go and change it back to use the tsc (since
> my debugging usually needs higher resolutions).
>
> * new product from Renolds ;-)
>
> -- Steve
I get it. Actually, I wasn't very sure whether this is the right solution
since my desktop machine uses tsc timer as default while the laptop the
pmtmr. I also remember that there was a patch a while ago on lkml which
enabled a modifiable behavior for PRINTK_TIME through a /proc interface and
kernel boot option but it somehow didn't get accepted. Ok, then, since we
keep the jiffies solution across arch's, how can I force the kernel to use
tsc for printk timings so that i can see the deltas between the different
printk's instead of the jiffies_64 ns value? The Pentium-M Centrino on the
laptop evidently supports rdtsc as a msr instruction after testing with this
small inline assembly snippet:
#include <stdio.h>
int main()
{
unsigned long long val;
__asm__ __volatile__("rdtsc" : "=A" (val));
printf("%llu\n", val);
return 0;
}
--
Regards,
Borislav Petkov.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |