Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933635AbbGUSyx (ORCPT ); Tue, 21 Jul 2015 14:54:53 -0400 Received: from mail-lb0-f176.google.com ([209.85.217.176]:35662 "EHLO mail-lb0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933338AbbGUSyw (ORCPT ); Tue, 21 Jul 2015 14:54:52 -0400 MIME-Version: 1.0 In-Reply-To: <55AE9471.1000601@gmail.com> References: <20150708160750.GQ19282@twins.programming.kicks-ass.net> <559D8250.8000707@gmail.com> <20150710141359.GJ19282@twins.programming.kicks-ass.net> <20150721082107.GE18673@twins.programming.kicks-ass.net> <20150721154959.GS19282@twins.programming.kicks-ass.net> <20150721161215.GU19282@twins.programming.kicks-ass.net> <20150721181553.GA3378@nazgul.tnic> <55AE9471.1000601@gmail.com> From: Andy Lutomirski Date: Tue, 21 Jul 2015 11:54:30 -0700 Message-ID: Subject: Re: Kernel broken on processors without performance counters To: Jason Baron Cc: Borislav Petkov , Peter Zijlstra , Thomas Gleixner , Mikulas Patocka , Paul Mackerras , Arnaldo Carvalho de Melo , Kees Cook , Andrea Arcangeli , Vince Weaver , "hillf.zj" , Valdis Kletnieks , "linux-kernel@vger.kernel.org" , Steven Rostedt Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1696 Lines: 50 On Tue, Jul 21, 2015 at 11:50 AM, Jason Baron wrote: > > > On 07/21/2015 02:15 PM, Borislav Petkov wrote: >> On Tue, Jul 21, 2015 at 06:12:15PM +0200, Peter Zijlstra wrote: >>> Yes, if you start out false, you must be unlikely. If you start out >>> true, you must be likely. >>> >>> We could maybe try and untangle that if there really is a good use case, >>> but this is the current state. >>> >>> The whole reason this happened is because 'false' is like: >>> >>> >>> ... >>> >>> 1: >>> ... >>> >>> >>> >>> label: >>> >>> jmp 1b >>> >>> >>> Where the code if out-of-line by default. The enable will rewrite the >>> with a jmp label. >> Btw, native_sched_clock() is kinda botched because of that, see below. >> >> I'd want that RDTSC to come first with a NOP preceding it which can >> become a JMP in case some idiotic CPU can't do RDTSC and needs to use >> jiffies. Instead, we *unconditionally* jump to RDTSC which is WTF?! We >> can just as well do a normal unlikely() without the static_key: > > hmmm...so this is a case where need to the default the branch > to the out-of-line branch at boot. That is, we can't just enable > the out-of-line branch at boot time, b/c it might be too late at > that point? IE native_sched_clock() gets called very early? > Could this be done at link time, or perhaps when compressing the kernel image, instead of at boot time? --Andy -- 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/