From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
Jan Beulich <jbeulich@novell.com>
Subject: Re: [PATCH 0 of 4] Xen spinlock updates and performance measurements
Date: Thu, 21 Aug 2008 13:53:04 +0200 [thread overview]
Message-ID: <20080821115304.GF30667@elte.hu> (raw)
In-Reply-To: <patchbomb.1219276937@localhost>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> 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
applied to tip/x86/xen - thanks Jeremy.
Ingo
next prev parent reply other threads:[~2008-08-21 11:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 0:02 Jeremy Fitzhardinge
2008-08-21 0:02 ` [PATCH 1 of 4] xen: save previous spinlock when blocking Jeremy Fitzhardinge
2008-08-21 7:25 ` Jan Beulich
2008-08-21 0:02 ` [PATCH 2 of 4] xen: add debugfs support Jeremy Fitzhardinge
2008-08-21 0:02 ` [PATCH 3 of 4] xen: allow interrupts to be enabled while doing a blocking spin Jeremy Fitzhardinge
2008-08-21 7:29 ` [PATCH 3 of 4] xen: allow interrupts to be enabled while doing ablocking spin Jan Beulich
2008-08-21 0:02 ` [PATCH 4 of 4] xen: measure how long spinlocks spend blocking Jeremy Fitzhardinge
2008-08-21 11:53 ` Ingo Molnar [this message]
2008-08-21 12:13 ` [PATCH 0 of 4] Xen spinlock updates and performance measurements Ingo Molnar
2008-08-21 20:17 ` Jeremy Fitzhardinge
2008-08-22 6:09 ` Ingo Molnar
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=20080821115304.GF30667@elte.hu \
--to=mingo@elte.hu \
--cc=jbeulich@novell.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.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
all inboxes | Powered by JetHome®