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] [day] [month] [year] [list]

Message-ID: <20090408143837.GG12931@elte.hu>
Date:	Wed, 8 Apr 2009 16:38:37 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	William Pitcock <nenolod@...eferenced.org>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	the arch/x86 maintainers <x86@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Xen-devel <xen-devel@...ts.xensource.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] Re: [GIT PULL] Xen for 2.6.30 #2


* William Pitcock <nenolod@...eferenced.org> wrote:

> Hi,
> 
> On Fri, 2009-04-03 at 19:36 +0200, Ingo Molnar wrote:
> > * Jeremy Fitzhardinge <jeremy@...p.org> wrote:
> > 
> > >> You know our stance which is very simple: dont put in Xen-only 
> > >> hooks that slow down native, and get rid of the existing Xen-only 
> > >> hooks.
> > >
> > > Yes, I understand that.  Unlike the pvops stuff, the dom0 changes 
> > > are largely all init-time and setup, and so have no performance 
> > > impact.
> > 
> > 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? :)
> 
> There's plenty of incentive for everyone who has a stake in this 
> thing to ensure that paravirt performs equally to native. I do not 
> see how you could be legitimately concerned about that.

Well, instead of supposedly plenty of speculative incentives in the 
future i'd like to see the existing performance impact of paravirt 
features to be fixed here and now, before piling up new features. 
Which did not get fixed in the past two years, despite those plenty 
of incentives you claim.

This is a basic engineering principle: fix up existing performance 
impact before piling up more overhead.

	Ingo
--
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/