1. 12 10月, 2010 1 次提交
    • R
      oprofile: disable write access to oprofilefs while profiler is running · 7df01d96
      Robert Richter 提交于
      Oprofile counters are setup when profiling is disabled. Thus, writing
      to oprofilefs has no immediate effect. Changes are updated only after
      oprofile is reenabled.
      
      To keep userland and kernel states synchronized, we now allow
      configuration of oprofile only if profiling is disabled.  In this case
      it checks if the profiler is running and then disables write access to
      oprofilefs by returning -EBUSY. The change should be backward
      compatible with current oprofile userland daemon.
      Acked-by: NMaynard Johnson <maynardj@us.ibm.com>
      Cc: William Cohen <wcohen@redhat.com>
      Cc: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
      Signed-off-by: NRobert Richter <robert.richter@amd.com>
      7df01d96
  2. 20 7月, 2009 3 次提交
    • R
      oprofile: Remove oprofile_multiplexing_init() · 16422a6e
      Robert Richter 提交于
      oprofile_multiplexing_init() can be removed when moving the
      initialization of oprofile_time_slice to oprofile_create_files().
      Signed-off-by: NRobert Richter <robert.richter@amd.com>
      16422a6e
    • R
      oprofile: Rename variable timeout_jiffies and move to oprofile_files.c · afe1b50f
      Robert Richter 提交于
      This patch renames timeout_jiffies into an oprofile specific name. The
      macro MULTIPLEXING_TIMER_DEFAULT is changed too.
      
      Also, since this variable is controlled using oprofilefs, its
      definition is moved to oprofile_files.c.
      Signed-off-by: NRobert Richter <robert.richter@amd.com>
      afe1b50f
    • J
      oprofile: Implement performance counter multiplexing · 4d4036e0
      Jason Yeh 提交于
      The number of hardware counters is limited. The multiplexing feature
      enables OProfile to gather more events than counters are provided by
      the hardware. This is realized by switching between events at an user
      specified time interval.
      
      A new file (/dev/oprofile/time_slice) is added for the user to specify
      the timer interval in ms. If the number of events to profile is higher
      than the number of hardware counters available, the patch will
      schedule a work queue that switches the event counter and re-writes
      the different sets of values into it. The switching mechanism needs to
      be implemented for each architecture to support multiplexing. This
      patch only implements AMD CPU support, but multiplexing can be easily
      extended for other models and architectures.
      
      There are follow-on patches that rework parts of this patch.
      Signed-off-by: NJason Yeh <jason.yeh@amd.com>
      Signed-off-by: NRobert Richter <robert.richter@amd.com>
      4d4036e0
  3. 17 12月, 2008 1 次提交
  4. 10 12月, 2008 1 次提交
    • R
      oprofile: set values to default when creating oprofilefs · 37ca5eb3
      Robert Richter 提交于
      This patch restores default values for:
      
      /dev/oprofile/cpu_buffer_size
      /dev/oprofile/buffer_watershed
      /dev/oprofile/buffer_size
      
      when creating the oprofilefs:
      
       # opcontrol --deinit
       # opcontrol --init
       # cat /dev/oprofile/cpu_buffer_size
       8192
       # echo 5123 > /dev/oprofile/cpu_buffer_size
       # cat /dev/oprofile/cpu_buffer_size
       5123
       # opcontrol --deinit
       # opcontrol --init
       # cat /dev/oprofile/cpu_buffer_size
       8192
       # opcontrol --deinit
      
      This sets the values in a defined state. Before, there was no way to
      restore the defaults without rebooting the system or reloading the
      module.
      Signed-off-by: NRobert Richter <robert.richter@amd.com>
      37ca5eb3
  5. 16 10月, 2008 2 次提交
  6. 24 9月, 2008 1 次提交
  7. 26 7月, 2008 1 次提交
    • J
      Oprofile Multiplexing Patch · 1a960b40
      Jason Yeh 提交于
      This patch introduces multiplexing support for the Oprofile kernel
      module. It basically adds a new function pointer in oprofile_operator
      allowing each architecture to supply its callback to switch between
      different sets of event when the timer expires. Userspace tools can
      modify the time slice through /dev/oprofile/time_slice.
      
      It also modifies the number of counters exposed to the userspace through
      /dev/oprofile. For example, the number of counters for AMD CPUs are
      changed to 32 and multiplexed in the sets of 4.
      Signed-off-by: NJason Yeh <jason.yeh@amd.com>
      Signed-off-by: NRobert Richter <robert.richter@amd.com>
      Cc: oprofile-list <oprofile-list@lists.sourceforge.net>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      1a960b40
  8. 13 2月, 2007 1 次提交
  9. 26 4月, 2005 1 次提交
  10. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4