From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: next-20081030: voyager compile busted Date: Thu, 30 Oct 2008 14:50:53 -0700 Message-ID: <490A2C3D.4020202@zytor.com> References: <20081030173030.d8847df6.sfr@canb.auug.org.au> <20081030180323.GA13399@x200.localdomain> <1225398287.19324.1.camel@localhost.localdomain> <20081030205230.GO27407@elte.hu> <1225400283.19324.6.camel@localhost.localdomain> <20081030210704.GA25665@elte.hu> <1225401708.19324.35.camel@localhost.localdomain> <490A2A30.5040905@zytor.com> <1225403266.19324.42.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: Received: from terminus.zytor.com ([198.137.202.10]:39852 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756240AbYJ3VvV (ORCPT ); Thu, 30 Oct 2008 17:51:21 -0400 In-Reply-To: <1225403266.19324.42.camel@localhost.localdomain> Sender: linux-next-owner@vger.kernel.org List-ID: To: James Bottomley Cc: Ingo Molnar , Alexey Dobriyan , Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Thomas Gleixner , Yinghai Lu James Bottomley wrote: > > Yes ... been having IRC conversations about that. We'd need to use > runtime patching to fix the performance regressions virtualisation has > been causing us first ... but then we could use it for voyager. > I thought we already were, at least to some degree (the call sites are way too big and way bigger than they need to be, so we end up with a lot of NOPs. I proposed a solution to Jeremy at Kernel Summit, but he basically said "I don't want to maintain that, I don't care about hardware performance", which is understandable but highly unfortunate.) -hpa