All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Jan Beulich <JBeulich@novell.com>,
	mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
	jeremy.fitzhardinge@citrix.com,
	Ky Srinivasan <KSrinivasan@novell.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4, v2] x86: enlightenment for ticket spin locks - base implementation
Date: Wed, 30 Jun 2010 12:32:51 +0300	[thread overview]
Message-ID: <20100630093251.GW4689@redhat.com> (raw)
In-Reply-To: <1277889996.1868.106.camel@laptop>

On Wed, Jun 30, 2010 at 11:26:36AM +0200, Peter Zijlstra wrote:
> On Wed, 2010-06-30 at 10:05 +0200, Peter Zijlstra wrote:
> > > +config ENLIGHTEN_SPINLOCKS
> > 
> > Why exactly are these enlightened? 
> 
> Or did I just miss a terribly pun:
>   enlightenment -> Buddha -> Zen -> Xen ?
Enlightenment is also a term that MS uses to describe their PV guests
which makes this name very confusing in Xen context. When I saw this
patch series I thought it has something to do with Hyper-V.

--
			Gleb.

  reply	other threads:[~2010-06-30  9:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 14:31 [PATCH 1/4, v2] x86: enlightenment for ticket spin locks - base implementation Jan Beulich
2010-06-30  8:05 ` Peter Zijlstra
2010-06-30  9:00   ` Jan Beulich
2010-06-30  9:11     ` Peter Zijlstra
2010-06-30  9:56       ` Jeremy Fitzhardinge
2010-06-30 11:43         ` Jan Beulich
2010-06-30 11:48           ` Peter Zijlstra
2010-06-30 11:54             ` Jan Beulich
2010-06-30 10:50       ` Jeremy Fitzhardinge
2010-06-30 11:52         ` Jan Beulich
2010-06-30 12:53           ` Jeremy Fitzhardinge
2010-06-30 13:21             ` Jan Beulich
2010-06-30 13:28               ` Jeremy Fitzhardinge
2010-06-30  9:26   ` Peter Zijlstra
2010-06-30  9:32     ` Gleb Natapov [this message]
2010-06-30  8:24 ` Peter Zijlstra

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=20100630093251.GW4689@redhat.com \
    --to=gleb@redhat.com \
    --cc=JBeulich@novell.com \
    --cc=KSrinivasan@novell.com \
    --cc=hpa@zytor.com \
    --cc=jeremy.fitzhardinge@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.