Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759025Ab3EWN3d (ORCPT ); Thu, 23 May 2013 09:29:33 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.122]:3084 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758581Ab3EWN3c (ORCPT ); Thu, 23 May 2013 09:29:32 -0400 X-Authority-Analysis: v=2.0 cv=DKcNElxb c=1 sm=0 a=rXTBtCOcEpjy1lPqhTCpEQ==:17 a=mNMOxpOpBa8A:10 a=rKI68ldaRsEA:10 a=5SG0PmZfjMsA:10 a=IkcTkHD0fZMA:10 a=meVymXHHAAAA:8 a=54K5z7jWVYMA:10 a=69xIsPUXDEltW-S3PBUA:9 a=QEXdDO2ut3YA:10 a=rXTBtCOcEpjy1lPqhTCpEQ==:117 X-Cloudmark-Score: 0 X-Authenticated-User: X-Originating-IP: 74.67.115.198 Message-ID: <1369315769.6828.198.camel@gandalf.local.home> Subject: Re: [PATCH] mm: fix up a spurious page fault whenever it happens From: Steven Rostedt To: Rik van Riel Cc: Stanislav Meduna , "H. Peter Anvin" , Linus Torvalds , "linux-rt-users@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Thomas Gleixner , Ingo Molnar , the arch/x86 maintainers , Hai Huang Date: Thu, 23 May 2013 09:29:29 -0400 In-Reply-To: <519E095A.4000105@redhat.com> References: <5195ED8B.7060002@meduna.org> <1369183168.6828.168.camel@gandalf.local.home> <519CBB30.3060200@redhat.com> <20130522134111.33a695c5@cuia.bos.redhat.com> <519D08B0.8050707@meduna.org> <1369246316.6828.176.camel@gandalf.local.home> <519D0CAB.7020800@meduna.org> <519D0FF8.5080200@redhat.com> <519D118B.6010306@zytor.com> <519D11BF.5000604@redhat.com> <519DCE2A.4010801@meduna.org> <519E095A.4000105@redhat.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4-3 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 794 Lines: 21 On Thu, 2013-05-23 at 08:19 -0400, Rik van Riel wrote: > We can add a bit in the architecture bits that > we use to check against other CPU and system > errata, and conditionally flush the whole TLB > from __native_flush_tlb_single(). If we find that some CPUs have issues and others do not, and we can determine this by checking the CPU type at run time, I would strongly suggest using the jump_label infrastructure to do the branches. I know this is early to suggest something like this, but I just wanted to put it in your head ;-) -- Steve -- 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/