1. 25 1月, 2010 1 次提交
  2. 20 7月, 2009 16 次提交
  3. 14 7月, 2009 2 次提交
  4. 10 7月, 2009 1 次提交
  5. 13 6月, 2009 1 次提交
  6. 12 6月, 2009 5 次提交
  7. 11 6月, 2009 1 次提交
  8. 08 5月, 2009 4 次提交
  9. 18 2月, 2009 1 次提交
  10. 17 2月, 2009 1 次提交
  11. 05 2月, 2009 1 次提交
  12. 04 12月, 2008 1 次提交
    • W
      x86/oprofile: fix Intel cpu family 6 detection · 3d337c65
      William Cohen 提交于
      Alan Jenkins wrote:
      > This is on an EeePC 701, /proc/cpuinfo as attached.
      >
      > Is this expected?  Will the next release work?
      >
      > Thanks, Alan
      >
      > # opcontrol --setup --no-vmlinux
      > cpu_type 'unset' is not valid
      > you should upgrade oprofile or force the use of timer mode
      >
      > # opcontrol -v
      > opcontrol: oprofile 0.9.4 compiled on Nov 29 2008 22:44:10
      >
      > # cat /dev/oprofile/cpu_type
      > i386/p6
      > # uname -r
      > 2.6.28-rc6eeepc
      
      Hi Alan,
      
      Looking at the kernel driver code for oprofile it can return the "i386/p6" for
      the cpu_type. However, looking at the user-space oprofile code there isn't the
      matching entry in libop/op_cpu_type.c or the events/unit_mask files in
      events/i386 directory.
      
      The Intel AP-485 says this is a "Intel Pentium M processor model D". Seems like
      the oprofile kernel driver should be identifying the processor as "i386/p6_mobile"
      
      The driver identification code doesn't look quite right in nmi_init.c
      
      http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=blob;f=arch/x86/oprofile/nmi_int.c;h=022cd41ea9b4106e5884277096e80e9088a7c7a9;hb=HEAD
      
      has:
      
      409         case 10 ... 13:
      410                 *cpu_type = "i386/p6";
      411                 break;
      
      Referring to the Intel AP-485:
      case 10 and 11 should produce "i386/piii"
      case 13 should produce "i386/p6_mobile"
      
      I didn't see anything for case 12.
      
      Something like the attached patch. I don't have a celeron machine to verify that
      changes in this area of the kernel fix thing.
      
      -Will
      Signed-off-by: NWilliam Cohen <wcohen@redhat.com>
      Tested-by: NAlan Jenkins <alan-jenkins@tuffmail.co.uk>
      Acked-by: NAndi Kleen <ak@linux.intel.com>
      Signed-off-by: NRobert Richter <robert.richter@amd.com>
      3d337c65
  13. 16 10月, 2008 1 次提交
  14. 14 10月, 2008 2 次提交
    • A
      oprofile: Implement Intel architectural perfmon support · b9917028
      Andi Kleen 提交于
      Newer Intel CPUs (Core1+) have support for architectural
      events described in CPUID 0xA. See the IA32 SDM Vol3b.18 for details.
      
      The advantage of this is that it can be done without knowing about
      the specific CPU, because the CPU describes by itself what
      performance events are supported. This is only a fallback
      because only a limited set of 6 events are supported.
      This allows to do profiling on Nehalem and on Atom systems
      (later not tested)
      
      This patch implements support for that in oprofile's Intel
      Family 6 profiling module. It also has the advantage of supporting
      an arbitary number of events now as reported by the CPU.
      Also allow arbitary counter widths >32bit while we're at it.
      
      Requires a patched oprofile userland to support the new
      architecture.
      
      v2: update for latest oprofile tree
          remove force_arch_perfmon
      Signed-off-by: NAndi Kleen <ak@linux.intel.com>
      Signed-off-by: NRobert Richter <robert.richter@amd.com>
      b9917028
    • A
      oprofile: Don't report Nehalem as core_2 · f645f640
      Andi Kleen 提交于
      This essentially reverts Linus' earlier 4b9f12a3
      commit. Nehalem is not core_2, so it shouldn't be reported as such.
      However with the earlier arch perfmon patch it will fall back to
      arch perfmon mode now, so there is no need to fake it as core_2.
      The only drawback is that Linus will need to patch the arch perfmon
      support into his oprofile binary now, but I think he can do that.
      Signed-off-by: NAndi Kleen <ak@linux.intel.com>
      Signed-off-by: NRobert Richter <robert.richter@amd.com>
      f645f640
  15. 24 9月, 2008 1 次提交
  16. 22 9月, 2008 1 次提交
    • A
      x86, oprofile: BUG: using smp_processor_id() in preemptible code · 45f197ad
      Andrea Righi 提交于
      Add __raw access before setting per cpu variable switch_index, to avoid
      the following BUG:
      
      [  449.166827] BUG: using smp_processor_id() in preemptible [00000000] code: modprobe/6998
      [  449.166848] caller is op_nmi_init+0xf0/0x2b0 [oprofile]
      [  449.166855] Pid: 6998, comm: modprobe Not tainted 2.6.27-rc5-mm1 #29
      [  449.166860] Call Trace:
      [  449.166872]  [<ffffffff80362d67>] debug_smp_processor_id+0xd7/0xe0
      [  449.166887]  [<ffffffffa00181c0>] op_nmi_init+0xf0/0x2b0 [oprofile]
      [  449.166902]  [<ffffffffa0018000>] oprofile_init+0x0/0x60 [oprofile]
      [  449.166915]  [<ffffffffa00180a9>] oprofile_arch_init+0x9/0x30 [oprofile]
      [  449.166928]  [<ffffffffa001801e>] oprofile_init+0x1e/0x60 [oprofile]
      [  449.166937]  [<ffffffff8020903b>] _stext+0x3b/0x160
      [  449.166946]  [<ffffffff80477985>] __mutex_unlock_slowpath+0xe5/0x190
      [  449.166955]  [<ffffffff80262c1a>] trace_hardirqs_on_caller+0xca/0x140
      [  449.166965]  [<ffffffff8026f7fc>] sys_init_module+0xdc/0x210
      [  449.166972]  [<ffffffff8020b7cb>] system_call_fastpath+0x16/0x1b
      Signed-off-by: NAndrea Righi <righi.andrea@gmail.com>
      Acked-by: NRobert Richter <robert.richter@amd.com>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      45f197ad