From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: [PATCH 0 of 4] Xen spinlock updates and performance
	measurements
Date: Wed, 20 Aug 2008 17:02:17 -0700
Message-ID: <patchbomb.1219276937@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Ingo Molnar <mingo@elte.hu>
Cc: xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
List-Id: xen-devel@lists.xenproject.org

Hi Ingo,

This series has some updates to Xen's spinlock implementation,
including adding a set of performance measurements in debugfs.

The series consists of:
 - correctly deal with a spinlock in an interrupt handler interrupting
   another spinlock spinning on a lock. [2.6.27 bugfix]
 - Add Xen debugfs support, including performance metrics for
   spinlocks, multicalls and mmu operations.
 - Allow interrupts to be enabled while spinning (blocking) for a lock
 - Measure time spinlocks spend blocked

Thanks,
	J