Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757889AbYKDQ7d (ORCPT ); Tue, 4 Nov 2008 11:59:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755774AbYKDQ7W (ORCPT ); Tue, 4 Nov 2008 11:59:22 -0500 Received: from out5.smtp.messagingengine.com ([66.111.4.29]:49066 "EHLO out5.smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757590AbYKDQ7W (ORCPT ); Tue, 4 Nov 2008 11:59:22 -0500 Message-Id: <1225817939.6422.1282948693@webmail.messagingengine.com> X-Sasl-Enc: tHFxzWVjAPOtRKDe0dU3BBDHT3lLuHwim3RHorXEnl+5 1225817939 From: "Alexander van Heukelum" To: "Ingo Molnar" Cc: "Cyrill Gorcunov" , "Alexander van Heukelum" , "LKML" , "Thomas Gleixner" , "H. Peter Anvin" , lguest@ozlabs.org, jeremy@xensource.com, "Steven Rostedt" , "Mike Travis" Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface Subject: Re: [PATCH RFC/RFB] x86_64, i386: interrupt dispatch changes In-Reply-To: <20081104165409.GA511@elte.hu> Date: Tue, 04 Nov 2008 17:58:59 +0100 References: <20081104122839.GA22864@mailshack.com> <20081104150729.GC21470@localhost> <1225813659.22738.1282932197@webmail.messagingengine.com> <20081104163636.GA20534@elte.hu> <1225817106.2795.1282945873@webmail.messagingengine.com> <20081104165409.GA511@elte.hu> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1397 Lines: 44 On Tue, 4 Nov 2008 17:54:09 +0100, "Ingo Molnar" said: > > * Alexander van Heukelum wrote: > > > > My estimation is that if we do it right, your approach will behave > > > better on modern CPUs (which is what matters most for such > > > things), especially on real workloads where there's a considerable > > > instruction-cache pressure. But it should be measured in any case. > > > > Fully agreed. I will do some measurements in the near future, maybe > > next week. At least noone came up with an absolutely blocking > > problem with this approach ;). > > how about "it does not build with lguest enabled" as a blocking > problem? ;-) Blocking for applying the patch as is, sure... As a proof of concept it is still fine ;). > arch/x86/lguest/built-in.o: In function `lguest_init_IRQ': > boot.c:(.init.text+0x33f): undefined reference to `interrupt' It just needs to be fixed. I guess similar problems are to be expected with xen or um. Thanks, Alexander > config attached. > > Ingo -- Alexander van Heukelum heukelum@fastmail.fm -- http://www.fastmail.fm - mmm... Fastmail... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/