Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933768AbeAJISR (ORCPT + 1 other); Wed, 10 Jan 2018 03:18:17 -0500 Received: from mail-wr0-f179.google.com ([209.85.128.179]:36045 "EHLO mail-wr0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965226AbeAJIBG (ORCPT ); Wed, 10 Jan 2018 03:01:06 -0500 X-Google-Smtp-Source: ACJfBou7mVZC7YqpKcv3M9B6bXBQqXL2qER8Mb7w9/SATeGAL9nfpTz5jqOvr0GK3mLWI+U62jwUKA== Date: Wed, 10 Jan 2018 09:01:02 +0100 From: Ingo Molnar To: Willy Tarreau Cc: linux-kernel@vger.kernel.org, x86@kernel.org, Andy Lutomirski , Borislav Petkov , Brian Gerst , Dave Hansen , Linus Torvalds , Peter Zijlstra , Thomas Gleixner , Josh Poimboeuf , "H. Peter Anvin" , Kees Cook Subject: Re: [RFC PATCH v2 3/6] x86/pti: add a per-cpu variable pti_disable Message-ID: <20180110080102.7ggggtruidb53yfu@gmail.com> References: <1515502580-12261-1-git-send-email-w@1wt.eu> <1515502580-12261-4-git-send-email-w@1wt.eu> <20180110071951.t4vbwlnlw2qycnpm@gmail.com> <20180110072900.GC14066@1wt.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180110072900.GC14066@1wt.eu> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: * Willy Tarreau wrote: > [...] If we had "pit_enabled", something like this could be confusing because > it's not obvious whether this pti_enabled *enforces* PTI or if its absence > disables it : > > cmpb $0, PER_CPU_VAR(pti_enabled) > jz .Lend\@ The natural sequence would be: cmpb $1, PER_CPU_VAR(pti_enabled) jne .Lend\@ which is not confusing to me at all. Thanks, Ingo