public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heinz Graalfs <graalfs@linux.vnet.ibm.com>
To: robert.richter@amd.com
Cc: mingo@elte.hu, oprofile-list@lists.sf.net,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
	borntraeger@de.ibm.com, schwidefsky@de.ibm.com,
	heiko.carstens@de.ibm.com
Subject: [patch v2 0/3] OProfile support for System z's hardware sampling
Date: Fri, 21 Jan 2011 11:06:51 +0100	[thread overview]
Message-ID: <20110121100651.821690659@linux.vnet.ibm.com> (raw)

Hello Robert,

I'm resending yesterday's mail because I missed to specify the correct sender information.

This is a re-posting of the patch series originally posted last month:

http://marc.info/?l=linux-s390&m=129285043619973&w=2

Heinz

Changes in

v2:
   - kernel module hwsampler removed, everything is now in oprofile kernel module
   - functions from hwsampler-main.c and smpctl.c merged into arch/s390/oprofile/hwsampler.c
     - functions made static
   - arch/s390/include/asm/hwsampler.h moved to arch/s390/oprofile/hwsampler.h
     - structs have now hws_ prefix
   - config variables changed, HAVE_HWSAMPLER used only
   - original patch 4 (handle_munmap.patch) removed

Description:

So far, OProfile takes samples by using a software interrupt.
The purpose of this series of patches is to add support for System z hardware sampling to OProfile.

Hardware (HW) sampling is a feature provided by System z processors (z10 and follow ons).
When sampling, the processor takes samples containing the instruction address, PID, and other information.
The samples are taken at a programmable rate and stored into a buffer provided by the operating system.
The sampling process is implemented in hardware and millicode and thus does not affect the operating system
being oberved, apart from requiring buffer memory that the Linux kernel must provide.

Hardware sampling is available in LPAR mode on 64 BIT processors only.

The overall approach is to replace the software-based sample generation by hardware sampling.
All required functionality to control the HW sampling mechanism is added to the oprofile kernel module.
The functions provide support for
 - controlling the sampling hardware,
 - setting up appropriate buffer structures (HW buffers),
 - retrieving sample entries from these buffers.
Multiple CPUs can be handled.

The samples contain the instruction address, a bit distinguishing between kernel and user space,
and for user space samples also the PID.
Instead of taking samples from its own per-CPU buffers, OProfile would rather take samples from the
HW buffers.

When hardware sampling can be enabled on the current System z processor it will be the new default.
Switching back to timer based sampling can be established by using

   echo 0 > /dev/oprofile/hwsampling/hwsampler

The user space drivers of OProfile also need an extension to control hw sampling by appropriate options.


             reply	other threads:[~2011-01-21 10:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 10:06 Heinz Graalfs [this message]
2011-01-21 10:06 ` [patch v2 1/3] This patch adds support for hardware based sampling on System z processors (models z10 and up) Heinz Graalfs
2011-02-14 18:57   ` Robert Richter
2011-03-25 11:00   ` Robert Richter
2011-03-29 12:38     ` Heinz Graalfs
2011-01-21 10:06 ` [patch v2 2/3] This patch enhances OProfile to support System zs hardware sampling feature Heinz Graalfs
2011-02-14 19:01   ` Robert Richter
2011-02-14 19:03     ` Robert Richter
2011-02-14 19:05     ` [PATCH] oprofile, s390: Rework hwsampler implementation Robert Richter
2011-02-14 19:07     ` [PATCH] oprofile, s390: Fix section mismatch of function hws_cpu_callback() Robert Richter
2011-01-21 10:06 ` [patch v2 3/3] This patch introduces a new oprofile sample add function (oprofile_add_ext_hw_sample) Heinz Graalfs
2011-02-14 18:55   ` Robert Richter
2011-02-07  8:23 ` [patch v2 0/3] OProfile support for System z's hardware sampling Heinz Graalfs
2011-02-14 19:42 ` Robert Richter
2011-02-15  7:17   ` Heiko Carstens
2011-02-15 16:59   ` Heinz Graalfs
2011-02-15 17:29     ` Robert Richter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110121100651.821690659@linux.vnet.ibm.com \
    --to=graalfs@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oprofile-list@lists.sf.net \
    --cc=robert.richter@amd.com \
    --cc=schwidefsky@de.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox