Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757464Ab0GNT4W (ORCPT ); Wed, 14 Jul 2010 15:56:22 -0400 Received: from one.firstfloor.org ([213.235.205.2]:37093 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754050Ab0GNT4V (ORCPT ); Wed, 14 Jul 2010 15:56:21 -0400 Date: Wed, 14 Jul 2010 21:56:17 +0200 From: Andi Kleen To: Linus Torvalds Cc: Ingo Molnar , Mathieu Desnoyers , LKML , Andrew Morton , Peter Zijlstra , Steven Rostedt , Steven Rostedt , Frederic Weisbecker , 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 Message-ID: <20100714195617.GC22373@basil.fritz.box> References: <20100714154923.947138065@efficios.com> <20100714155804.049012415@efficios.com> <20100714170617.GB4955@Krystal> <20100714184642.GA9728@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 781 Lines: 21 > or similar. Wouldn't that be nice to have as a capability? It means the NMI watchdog would get useless if these areas become common. Again I suspect all of this is not really needed anyways if vmalloc_sync_all() works properly. That would solve the original problem Mathieu was trying to solve for per_cpu data. The rule would be just to call vmalloc_sync_all() properly when changing per CPU data too. In fact I'm pretty sure it worked originally. Perhaps it regressed? -Andi -- ak@linux.intel.com -- Speaking for myself only. -- 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/