Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753888Ab0HPLbI (ORCPT ); Mon, 16 Aug 2010 07:31:08 -0400 Received: from mx1.redhat.com ([209.132.183.28]:63792 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752408Ab0HPLbG (ORCPT ); Mon, 16 Aug 2010 07:31:06 -0400 Message-ID: <4C692129.4040307@redhat.com> Date: Mon, 16 Aug 2010 14:29:45 +0300 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100720 Fedora/3.1.1-1.fc13 Lightning/1.0b2pre Thunderbird/3.1.1 MIME-Version: 1.0 To: Mathieu Desnoyers CC: Steven Rostedt , Peter Zijlstra , Linus Torvalds , Frederic Weisbecker , Ingo Molnar , LKML , Andrew Morton , Thomas Gleixner , Christoph Hellwig , Li Zefan , Lai Jiangshan , Johannes Berg , Masami Hiramatsu , Arnaldo Carvalho de Melo , Tom Zanussi , KOSAKI Motohiro , Andi Kleen , "H. Peter Anvin" , Jeremy Fitzhardinge , "Frank Ch. Eigler" , Tejun Heo Subject: Re: [patch 1/2] x86_64 page fault NMI-safe References: <20100714231117.GA22341@Krystal> <20100714233843.GD14533@nowhere> <20100715162631.GB30989@Krystal> <1280855904.1923.675.camel@laptop> <1280903273.1923.682.camel@laptop> <1281537273.3058.14.camel@gandalf.stny.rr.com> <4C6816BD.8060101@redhat.com> <20100815164413.GA9990@Krystal> <4C681B03.2050302@redhat.com> <20100815183121.GA6476@Krystal> In-Reply-To: <20100815183121.GA6476@Krystal> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1191 Lines: 26 On 08/15/2010 09:31 PM, Mathieu Desnoyers wrote: > > I tested it in the past, and must admit that I changed from a vmalloc-based > implementation to page-based using software cross-page write primitives based on > feedback from Steven and Ingo. Diminishing TLB trashing seemed like a good > approach, and using vmalloc on 32-bit machines is a pain, because users have to > tweak the vmalloc region size at boot. So all in all, I moved to a vmalloc-less > implementation without much more thought. Forgot to comment about the i386 issue - that really is a blocker if you absolutely need to support large trace buffers on 32-bit machines. I would urge all those people to move to x86_64 and be done with it, but I don't know all the use cases. It's possible to hack this to work by having a private mm_struct and switching to it temporarily, but it will be horribly slow. -- error compiling committee.c: too many arguments to function -- 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/