[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <519E3089.8040701@zytor.com>
Date: Thu, 23 May 2013 08:06:49 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Steven Rostedt <rostedt@...dmis.org>
CC: Rik van Riel <riel@...hat.com>,
Stanislav Meduna <stano@...una.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"linux-rt-users@...r.kernel.org" <linux-rt-users@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
the arch/x86 maintainers <x86@...nel.org>,
Hai Huang <hhuang@...hat.com>
Subject: Re: [PATCH] mm: fix up a spurious page fault whenever it happens
On 05/23/2013 06:29 AM, Steven Rostedt wrote:
> 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 ;-)
>
We don't even need the jump_label infrastructure -- we have
static_cpu_has*() which actually predates jump_label although it uses
the same underlying ideas.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists