linux-kernel - Re: [Xen-devel] Re: [GIT PULL] Xen for 2.6.30 #2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 03 Apr 2009 11:31:53 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	the arch/x86 maintainers <x86@...nel.org>,
	Xen-devel <xen-devel@...ts.xensource.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [Xen-devel] Re: [GIT PULL] Xen for 2.6.30 #2

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/