1. 09 1月, 2006 1 次提交
  2. 06 1月, 2006 1 次提交
    • C
      [PATCH] i386: PTRACE_POKEUSR: allow changing RF bit in EFLAGS register. · 9f155b98
      Chuck Ebbert 提交于
      Setting RF (resume flag) allows a debugger to resume execution after a
      code breakpoint without tripping the breakpoint again.  It is reset by
      the CPU after execution of one instruction.
      
      Requested by Stephane Eranian:
        "I am trying to the user HW debug registers on i386 and I am running
         into a problem with ptrace() not allowing access to EFLAGS_RF for
         POKEUSER (see FLAG_MASK).  [ ...  ] It avoids the need to remove the
         breakpoint, single step, and reinstall.  The equivalent functionality
         exists on IA-64 and is allowed by ptrace()"
      
      Cc: Stephane Eranian <eranian@hpl.hp.com>
      Signed-off-by: NChuck Ebbert <76306.1226@compuserve.com>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9f155b98
  3. 05 1月, 2006 1 次提交
  4. 01 1月, 2006 1 次提交
  5. 21 12月, 2005 1 次提交
  6. 17 12月, 2005 1 次提交
  7. 16 12月, 2005 2 次提交
  8. 13 12月, 2005 6 次提交
  9. 07 12月, 2005 4 次提交
    • V
      [CPUFREQ] CPU frequency display in /proc/cpuinfo · 95235ca2
      Venkatesh Pallipadi 提交于
      What is the value shown in "cpu MHz" of /proc/cpuinfo when CPUs are capable of
      changing frequency?
      
      Today the answer is: It depends.
      On i386:
      SMP kernel - It is always the boot frequency
      UP kernel - Scales with the frequency change and shows that was last set.
      
      On x86_64:
      There is one single variable cpu_khz that gets written by all the CPUs. So,
      the frequency set by last CPU will be seen on /proc/cpuinfo of all the
      CPUs in the system. What you see also depends on whether you have constant_tsc
      capable CPU or not.
      
      On ia64:
      It is always boot time frequency of a particular CPU that gets displayed.
      
      The patch below changes this to:
      Show the last known frequency of the particular CPU, when cpufreq is present. If
      cpu doesnot support changing of frequency through cpufreq, then boot frequency
      will be shown. The patch affects i386, x86_64 and ia64 architectures.
      
      Signed-off-by: Venkatesh Pallipadi<venkatesh.pallipadi@intel.com>
      Signed-off-by: NDave Jones <davej@redhat.com>
      95235ca2
    • M
      [CPUFREQ] Move PMBASE reading away and do it only once at initialization time · 9a7d82a8
      Mattia Dongili 提交于
      This patch moves away PMBASE reading and only performs it at
      cpufreq_register_driver time by exiting with -ENODEV if unable to read
      the value.
      Signed-off-by: NMattia Dongili <malattia@linux.it>
      Acked-by: NDominik Brodowski <linux@dominikbrodowski.net>
      Signed-off-by: NDave Jones <davej@redhat.com>
      9a7d82a8
    • M
      [CPUFREQ] Measure transition latency at driver initialization · 1a10760c
      Mattia Dongili 提交于
      The attached patch introduces runtime latency measurement for ICH[234]
      based chipsets instead of using CPUFREQ_ETERNAL. It includes
      some sanity checks in case the measured value is out of range and
      assigns a safe value of 500uSec that should still be enough on
      problematics chipsets (current testing report values ~200uSec). The
      measurement is currently done in speedstep_get_freqs in order to avoid
      further unnecessary transitions and in the hope it'll come handy for SMI
      also.
      Signed-off-by: NMattia Dongili <malattia@linux.it>
      Acked-by: NDominik Brodowski <linux@dominikbrodowski.net>
      Signed-off-by: NDave Jones <davej@redhat.com>
      
       speedstep-ich.c |    4 ++--
       speedstep-lib.c |   32 +++++++++++++++++++++++++++++++-
       speedstep-lib.h |    1 +
       speedstep-smi.c |    1 +
       4 files changed, 35 insertions(+), 3 deletions(-)
      1a10760c
    • D
      [CPUFREQ] Change loglevels on powernow-k8 bios error printk's. · cc6e8de8
      Dave Jones 提交于
      If a user has booted with 'quiet', some important messages don't
      get displayed which really should. We've seen at least one case
      where powernow-k8 stopped working, and the user needed a BIOS update
      that they didn't know about.
      Signed-off-by: NDave Jones <davej@redhat.com>
      cc6e8de8
  10. 01 12月, 2005 3 次提交
  11. 30 11月, 2005 3 次提交
  12. 24 11月, 2005 4 次提交
  13. 21 11月, 2005 3 次提交
  14. 16 11月, 2005 1 次提交
  15. 15 11月, 2005 7 次提交
  16. 14 11月, 2005 1 次提交