On Wed, 29 Nov 2006, Ingo Molnar wrote:
please talk to John and Thomas about GTOD interfaces. Right now the
solution used by the latency tracer is working out pretty OK - but if
something better comes along i can use that too. It's not a burning
issue though, unless you know of some bug. (i'm not sure what you mean
by it becoming constrictive)
It doesn't appear to handle clock switching, so for instance, if generic
time switches from the tsc, to the acpi_pm would the latency tracer
tolerate it ? Also a combination of HRT enabled, and a faulty acpi_pm
would cause the tracer to use the PIT .. The PIT takes spinlocks during
it's read so I'd imgaine the system would crash, or something else not so
good.
Also with HRT enabled, you would end up using the acpi_pm even if the TSC
is stable which is slower ..
That's what I mean when I say constrictive .
I've been working with John and Thomas to make the clocksource more
usable (and lots of cleanups),
ftp://source.mvista.com/pub/dwalker/clocksource/clocksource-v8/
Daniel
-
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]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
