1. 07 Oct, 2007 5 commits
    • Peter Zijlstra's avatar
      lockstat: documentation · a560aa48
      Peter Zijlstra authored
      
      
      Provide some documentation for CONFIG_LOCK_STAT.
      
      Signed-off-by: default avatarPeter Zijlstra <a.p.zijlstra@chello.nl>
      Acked-by: default avatarIngo Molnar <mingo@elte.hu>
      Cc: "Randy.Dunlap" <rdunlap@xenotime.net>
      Cc: Rob Landley <rob@landley.net>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      a560aa48
    • Rafal Bilski's avatar
      Longhaul: add auto enabled "revid_errata" option · 52a2638b
      Rafal Bilski authored
      
      
      VIA C3 Ezra-T has RevisionID equal to 1, but it needs RevisionKey to be 0
      or CPU will ignore new frequency and will continue to work at old
      frequency.  New "revid_errata" option will force RevisionKey to be set to
      0, whatever RevisionID is.
      
      Additionaly "Longhaul" will not silently ignore unsuccessful transition.
      It will try to check if "revid_errata" or "disable_acpi_c3" options need to
      be enabled for this processor/system.
      
      Same for Longhaul ver.  2 support.  It will be disabled if none of above
      options will work.
      
       Best case scenario (with patch apllied and v2 enabled):
       longhaul: VIA C3 'Ezra' [C5C] CPU detected.  Longhaul v2 supported.
       longhaul: Using northbridge support.
       longhaul: VRM 8.5
       longhaul: Max VID=1.350  Min VID=1.050, 13 possible voltage scales
       longhaul: f: 300000 kHz, index: 0, vid: 1050 mV
       [...]
       longhaul: Voltage scaling enabled.
       Worst case scenario:
       longhaul: VIA C3 'Ezra-T' [C5M] CPU detected.  Powersaver supported.
       longhaul: Using northbridge support.
       longhaul: Using ACPI support.
       longhaul: VRM 8.5
       longhaul: Claims to support voltage scaling but min & max are both 1.250. Voltage scaling disabled
       longhaul: Failed to set requested frequency!
       longhaul: Enabling "Ignore Revision ID" option.
       longhaul: Failed to set requested frequency!
       longhaul: Disabling ACPI C3 support.
       longhaul: Disabling "Ignore Revision ID" option.
       longhaul: Failed to set requested frequency!
       longhaul: Enabling "Ignore Revision ID" option.
      
      [akpm@linux-foundation.org: coding-style cleanups]
      Signed-off-by: default avatarRafal Bilski <rafalbilski@interia.pl>
      Signed-off-by: default avatarDave Jones <davej@redhat.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      52a2638b
    • Anton Blanchard's avatar
      Fix timer_stats printout of events/sec · 74922be1
      Anton Blanchard authored
      
      
      When using /proc/timer_stats on ppc64 I noticed the events/sec field wasnt
      accurate.  Sometimes the integer part was incorrect due to rounding (we
      werent taking the fractional seconds into consideration).
      
      The fraction part is also wrong, we need to pad the printf statement and
      take the bottom three digits of 1000 times the value.
      
      Signed-off-by: default avatarAnton Blanchard <anton@samba.org>
      Acked-by: default avatarIngo Molnar <mingo@elte.hu>
      Cc: <stable@kernel.org>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      74922be1
    • Linus Torvalds's avatar
      Don't do load-average calculations at even 5-second intervals · 0c2043ab
      Linus Torvalds authored
      
      
      It turns out that there are a few other five-second timers in the
      kernel, and if the timers get in sync, the load-average can get
      artificially inflated by events that just happen to coincide.
      
      So just offset the load average calculation it by a timer tick.
      
      Noticed by Anders Boström, for whom the coincidence started triggering
      on one of his machines with the JBD jiffies rounding code (JBD is one of
      the subsystems that also end up using a 5-second timer by default).
      
      Tested-by: default avatarAnders Boström <anders@bostrom.dyndns.org>
      Cc: Chuck Ebbert <cebbert@redhat.com>
      Cc: Arjan van de Ven <arjan@linux.intel.com>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      0c2043ab
    • Linus Torvalds's avatar
      VT_WAITACTIVE: Avoid returning EINTR when not necessary · 70cb9793
      Linus Torvalds authored
      
      
      We should generally prefer to return ERESTARTNOHAND rather than EINTR,
      so that processes with unhandled signals that get ignored don't return
      EINTR.
      
      This can help with X startup issues:
      
          Fatal server error:
          xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call
      
      although the real fix is having the X server always retry EINTR
      regardless (since EINTR does happen for signals that have handlers
      installed). Keithp has a patch for that.
      
      Regardless, ERESTARTNOHAND is the correct thing to use.
      
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      70cb9793
  2. 06 Oct, 2007 4 commits
  3. 05 Oct, 2007 7 commits
  4. 04 Oct, 2007 5 commits
  5. 03 Oct, 2007 18 commits
  6. 02 Oct, 2007 1 commit