All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: the arch/x86 maintainers <x86@kernel.org>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [Xen-devel] Re: [GIT PULL] Xen for 2.6.30 #2
Date: Fri, 03 Apr 2009 11:31:53 -0700	[thread overview]
Message-ID: <49D65619.8000708@goop.org> (raw)
In-Reply-To: <20090403173623.GB6295@elte.hu>

Ingo Molnar wrote:
> Yes, but once dom0 goes in your incentive to fix the native kernel 
> performance drain we accumulated along the years of paravirt layers 
> will be strongly weakened, right? :)

Not at all.  There's a pile of performance work that needs to be done, 
both native and Xen.  I've been addressing it in an ad-hoc, time-sliced 
way so far, but I haven't had the chance to concentrate on it as I'd 
like to.  Once I get all the basic stuff off my plate I'll be able to 
actually focus.

Besides, its not really the sort of "incentive" that I respond to; I 
find it demotivating because it carries the presumption that I won't do 
"the right thing" without some element of coercion.  It's not like I 
don't already do a fair amount of generally beneficial kernel work.  If 
you think I should direct my attention in one direction over another, 
I'm happy to take suggestions.

    J

WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: the arch/x86 maintainers <x86@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Xen-devel <xen-devel@lists.xensource.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Re: [GIT PULL] Xen for 2.6.30 #2
Date: Fri, 03 Apr 2009 11:31:53 -0700	[thread overview]
Message-ID: <49D65619.8000708@goop.org> (raw)
In-Reply-To: <20090403173623.GB6295@elte.hu>

Ingo Molnar wrote:
> Yes, but once dom0 goes in your incentive to fix the native kernel 
> performance drain we accumulated along the years of paravirt layers 
> will be strongly weakened, right? :)

Not at all.  There's a pile of performance work that needs to be done, 
both native and Xen.  I've been addressing it in an ad-hoc, time-sliced 
way so far, but I haven't had the chance to concentrate on it as I'd 
like to.  Once I get all the basic stuff off my plate I'll be able to 
actually focus.

Besides, its not really the sort of "incentive" that I respond to; I 
find it demotivating because it carries the presumption that I won't do 
"the right thing" without some element of coercion.  It's not like I 
don't already do a fair amount of generally beneficial kernel work.  If 
you think I should direct my attention in one direction over another, 
I'm happy to take suggestions.

    J

  reply	other threads:[~2009-04-03 18:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30 19:42 [GIT PULL] Xen for 2.6.30 #1 Jeremy Fitzhardinge
2009-03-31 18:00 ` [GIT PULL] Xen for 2.6.30 #2 Jeremy Fitzhardinge
2009-03-31 18:00   ` Jeremy Fitzhardinge
2009-03-31 18:55   ` Ingo Molnar
2009-03-31 18:55     ` Ingo Molnar
2009-03-31 19:38     ` [Xen-devel] " Jeremy Fitzhardinge
2009-03-31 19:38       ` Jeremy Fitzhardinge
2009-04-03 17:36       ` [Xen-devel] " Ingo Molnar
2009-04-03 17:36         ` Ingo Molnar
2009-04-03 18:31         ` Jeremy Fitzhardinge [this message]
2009-04-03 18:31           ` Jeremy Fitzhardinge
2009-04-05  2:38         ` [Xen-devel] " William Pitcock
2009-04-05  2:38           ` William Pitcock
2009-04-08 14:38           ` [Xen-devel] " 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=49D65619.8000708@goop.org \
    --to=jeremy@goop.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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 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.