mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	ksrinivasan <ksrinivasan@novell.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"hpa@zytor.com" <hpa@zytor.com>
Subject: Re: [PATCH 2/4, v2] x86: enlightenment for ticket spin locks -  Xen implementation
Date: Thu, 1 Jul 2010 12:39:25 +0100	[thread overview]
Message-ID: <alpine.DEB.2.00.1007011105430.30135@kaball-desktop> (raw)
In-Reply-To: <4C2C6680020000780000901E@vpn.id2.novell.com>

On Thu, 1 Jul 2010, Jan Beulich wrote:
> >>> On 30.06.10 at 17:57, Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> wrote:
> > On Wed, 30 Jun 2010, Jeremy Fitzhardinge wrote:
> >> On 06/29/2010 04:32 PM, Jan Beulich wrote:
> >> > Use the (alternative instructions based) callout hooks to the ticket
> >> > spinlock code to enlighten ticket locks when running fully virtualized
> >> > on Xen. Ultimately, this code might also be a candidate to be used
> >> > when running para-virtualized.
> >> >
> >> 
> >> I'm not sure what the gain is by making this independent of all the rest
> >> of the Xen support in the kernel.  Stefano is working on a series
> >> (posted a few times now) to add more paravirtual features for Xen HVM
> >> guests, and this work is conceptually very similar.
> > 
> > My series has been stable since a while now and contains all the basic
> > PV on HVM mechanisms you need, including parsing the cpuid and mapping
> > the shared info page.
> > 
> > Could you please rebase on my series (or at least the first two
> > patches), so that we don't conflict with each other?
> 
> I really don't want to make those patches depend on no upstream
> stuff (as I want it accepted upstream), and I'm not sure when your
> patch series is expected to be upstream. If that's going to be soon,
> I'd just re-base after it happened.
 
Given that the patch series has been tested and reviewed several times
by now, I don't expect big changes any more.
Therefore I hope it will be accepted as soon as possible (keeping in
mind that we are in RC3 right now).

      reply	other threads:[~2010-07-01 11:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 14:32 Jan Beulich
2010-06-30  8:05 ` Peter Zijlstra
2010-06-30  8:52   ` Jan Beulich
2010-06-30  8:56     ` Peter Zijlstra
2010-06-30  9:04       ` Jan Beulich
2010-06-30 10:07 ` Jeremy Fitzhardinge
2010-06-30 11:31   ` Jan Beulich
2010-06-30 13:23     ` Jeremy Fitzhardinge
2010-06-30 14:03       ` Jan Beulich
2010-06-30 14:25         ` Jeremy Fitzhardinge
2010-06-30 14:36           ` Jan Beulich
2010-06-30 14:42             ` Jeremy Fitzhardinge
2010-06-30 22:14       ` H. Peter Anvin
2010-07-05 23:12         ` Jeremy Fitzhardinge
2010-06-30 15:57   ` Stefano Stabellini
2010-07-01  7:57     ` Jan Beulich
2010-07-01 11:39       ` Stefano Stabellini [this message]

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=alpine.DEB.2.00.1007011105430.30135@kaball-desktop \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=JBeulich@novell.com \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=ksrinivasan@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 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®