[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110121100651.821690659@linux.vnet.ibm.com>
Date: Fri, 21 Jan 2011 11:06:51 +0100
From: Heinz Graalfs <graalfs@...ux.vnet.ibm.com>
To: robert.richter@....com
Cc: mingo@...e.hu, oprofile-list@...ts.sf.net,
linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org,
borntraeger@...ibm.com, schwidefsky@...ibm.com,
heiko.carstens@...ibm.com
Subject: [patch v2 0/3] OProfile support for System z's hardware sampling
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists