28 Oct, 2013
1 commit
-
- timers-howto was added by commit 0fcb8081 (Documentation: Add
timers/timers-howto.txt)
- NO_HZ was added by commit 0c87f9b5 (nohz_full: Add documentation.)Cc: Patrick Pannuto
Signed-off-by: Henrik Austad
Reviewed-by: Paul E. McKenney
Signed-off-by: Jiri Kosina
19 Aug, 2013
1 commit
-
This commit adds information about testing nohz_full, and also emphasizes
the fact that you need a multi-CPU system to get any benefit from nohz_full.Signed-off-by: Paul E. McKenney
Acked-by: Frederic Weisbecker
Reviewed-by: Josh Triplett
11 Jun, 2013
2 commits
-
This commit calls out the potential for slowing the tick even when there
are multiple runnable processes per CPU, It also points out that current
mainlined version keeps the tick going on at least one CPU even when all
CPUs are otherwise idle. Finally, it notes the need for a 1-HZ tick in
order to calculate CPU load, maintain sched average, compute CFS entity
vruntime, compute avenrun, and carry out load balancing.Signed-off-by: Paul E. McKenney
Reviewed-by: Josh Triplett -
Make it more clear that there are three options, and give hints as
to which of the three is most likely to be useful in different
situations.Reported-by: Sedat Dilek
Signed-off-by: Paul E. McKenney
Reviewed-by: Josh Triplett
28 Apr, 2013
1 commit
-
Signed-off-by: Paul E. McKenney
Cc: Frederic Weisbecker
Cc: Steven Rostedt
Cc: Borislav Petkov
Cc: Arjan van de Ven
Cc: Kevin Hilman
Cc: Christoph Lameter
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Olivier Baetz
Reviewed-by: Randy Dunlap
Reviewed-by: Borislav Petkov
Reviewed-by: Kevin Hilman
28 Sep, 2011
1 commit
-
There are numerous broken references to Documentation files (in other
Documentation files, in comments, etc.). These broken references are
caused by typo's in the references, and by renames or removals of the
Documentation files. Some broken references are simply odd.Fix these broken references, sometimes by dropping the irrelevant text
they were part of.Signed-off-by: Paul Bolle
Signed-off-by: Jiri Kosina
17 May, 2011
1 commit
-
Signed-off-by: Jonathan Neuschäfer
Signed-off-by: Jiri Kosina
02 Nov, 2010
1 commit
-
"gadget", "through", "command", "maintain", "maintain", "controller", "address",
"between", "initiali[zs]e", "instead", "function", "select", "already",
"equal", "access", "management", "hierarchy", "registration", "interest",
"relative", "memory", "offset", "already",Signed-off-by: Uwe Kleine-König
Signed-off-by: Jiri Kosina
27 Oct, 2010
1 commit
-
$./hpet_example info /dev/hpet
-hpet: executing info
hpet_info: hi_irqfreq 0x0 hi_flags 0x0 hi_hpet 0 hi_timer 2Signed-off-by: Jaswinder Singh Rajput
Cc: Clemens Ladisch
Cc: "Venkatesh Pallipadi (Venki)"
Cc: john stultz
Cc: Thomas Gleixner
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
04 Aug, 2010
1 commit
-
This file seeks to explain the nuances in various delays;
many driver writers are not necessarily familiar with the
various kernel timers, their shortfalls, and quirks. When
faced withndelay, udelay, mdelay, usleep_range, msleep, and msleep_interrubtible
the question "How do I just wait 1 ms for my hardware to
latch?" has the non-intuitive "best" answer:
usleep_range(1000,1500)This patch is followed by a series of checkpatch additions
that seek to help kernel hackers pick the best delay.Signed-off-by: Patrick Pannuto
Cc: apw@canonical.com
Cc: corbet@lwn.net
Cc: arjan@linux.intel.com
Cc: Randy Dunlap
Cc: Andrew Morton
LKML-Reference:
Signed-off-by: Thomas Gleixner
02 Jun, 2010
1 commit
-
We should only build hpet_example on x86[-64], where it is implemented.
It can cause build errors on other architectures.Signed-off-by: Randy Dunlap
Reported-by: Heiko Carstens
Cc: Heiko Carstens
Cc: Arjan van de Ven
Signed-off-by: Linus Torvalds
24 May, 2010
1 commit
-
Documentation/timers/hpet_example.c: fcntl.h is included more than once.
Documentation/timers/hpet_example.c: signal.h is included more than once.Signed-off-by: Andrea Gelmini
Signed-off-by: Randy Dunlap
Signed-off-by: Linus Torvalds
13 Mar, 2010
1 commit
-
Documentation/timers/hpet.txt:
Expose example and tool source files in the Documentation/timers/ directory in
their own files instead of being buried (almost hidden) in readme/txt files.
This should help to prevent bitrot.This will make them more visible/usable to users who may need
to use them, to developers who may need to test with them, and
to anyone who would fix/update them if they were more visible.Also, if any of these possibly should not be in the kernel tree at
all, it will be clearer that they are here and we can discuss if
they should be removed.Signed-off-by: Randy Dunlap
Cc: Thomas Gleixner
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
09 Nov, 2009
1 commit
-
That URL is out of date. Update it.
Cc: Thomas Gleixner
Cc: Randy Dunlap
Cc: Matt LaPlante
Cc: Jiri Kosina
Signed-off-by: WANG Cong
Acked-by: Matt LaPlante
Signed-off-by: Jiri Kosina
13 Jun, 2009
1 commit
-
Fix various typos in documentation txts.
Signed-off-by: Matt LaPlante
Signed-off-by: Jiri Kosina
01 Aug, 2008
2 commits
-
Minor /dev/hpet updates and bugfixes:
* Remove dead code, mostly remnants of an incomplete/unusable
kernel interface ... noted when addressing "sparse" warnings:
+ hpet_unregister() and a routine it calls
+ hpet_task and all references, including hpet_task_lock
+ hpet_data.hd_flags (and HPET_DATA_PLATFORM)* Correct and improve boot message:
+ displays *counter* (shared between comparators) bit width,
not *timer* bit widths (which are often mixed)
+ relabel "timers" as "comparators"; this is less confusing,
they are not independent like normal timers are (sigh)
+ display MHz not Hz; it's never less than 10 MHz.* Tighten and correct the userspace interface code
+ don't accidentally program comparators in 64-bit mode using
32-bit values ... always force comparators into 32-bit mode
+ provide the correct bit definition flagging comparators with
periodic capability ... the ABI is unchanged* Update Documentation/hpet.txt
+ be more correct and current
+ expand description a bit
+ don't mention that now-gone kernel interfacePlus, add a FIXME comment for something that could cause big trouble
on systems with more capable HPETs than at least Intel seems to ship.It seems that few folk use this userspace interface; it's not very
usable given the general lack of HPET IRQ routing. I'm told that
the only real point of it any more is to mmap for fast timestamps;
IMO that's handled better through the gettimeofday() vsyscall.Signed-off-by: David Brownell
Acked-by: Clemens Ladisch
Signed-off-by: Ingo Molnar
27 Jul, 2008
1 commit
-
Cc: Randy Dunlap
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
24 Jul, 2008
1 commit
-
Move hpet.txt to Documentation/timers/ subdirectory.
Add 00-INDEX to Documentation/timers/ subdirectory.Signed-off-by: Randy Dunlap
Cc: tglx
Signed-off-by: Thomas Gleixner
17 Apr, 2008
1 commit
-
We have two directories with timer related information in
Documentation/: hrtimers/ and hrtimer/. timer_stats are not restricted
to hrtimers. Move all those files into Documentation/timers where we
can pile up other timer related docs as well.Pointed-out-by: Randy Dunlap
Signed-off-by: Thomas Gleixner