Received: by 2002:ac0:8c9a:0:0:0:0:0 with SMTP id r26csp1207807ima; Fri, 1 Feb 2019 18:53:34 -0800 (PST) X-Google-Smtp-Source: ALg8bN4d048pBfodJaEHan1tPLGJYN32jZfXF10GbSADS3S+a3aMQVSbKexTYb6Eh8Y37jqWE4H0 X-Received: by 2002:a17:902:1745:: with SMTP id i63mr41335845pli.145.1549076014717; Fri, 01 Feb 2019 18:53:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549076014; cv=none; d=google.com; s=arc-20160816; b=ZJXHW7xzBjiqkj2xx3dlVFXd7AGMUzFtRGEKTB5vKJDfSNvNVfvDLHl/gAEECgrkkg ZZxxg1dvmGlczaol2dvk80TnyN2Mf1nXmAntFII1Mr51O3GiDhPC+mBmc5qdroUJPqPr 89dsyJkR1Tmy7orwQwisEgBANCSfImiXVuGAwdQTUxlglDME5QcenoqS/gTk9SKjzPHV zpoylizObcINqkI/eVEtjN7CFZxq7pKKag6JseWdfWjyHQvH4qQ/xzQ9ZwqTK7W+cBhP V6kQRbEQVGhsUC2wLx5VzAVTyNX1hTEZkJzOoprhGASiCDyecGgy9VCdkuW+huUtXa/2 L56A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=OaXTWh0WxXqZCOdBjbYVZZf6E1Hak+s+/dQNUWyqxDI=; b=rMCAWb5/R0+zLW9ZQVcd1X2ZEepeKACUenh1cztG090xAQ2eRp6CKSAvHPZJjRMR30 AzTFV/4JSa7Zn6mBGUXSI+t5QwZ4RJGzGftZEzIPWKUMnzSavvDKKLrQzr47LUECjKmK SRnXtZSOWL85ZRObP2m3LN97lG+fKJSlZ1PqtyVExQlAQ2CSPV4jlQwmurSGjxJTXzVO R2qVrNGYIEYGITOJaOhXg2TedWvYHYYiIFs7MbnLl+Cg0+kkBQ0Q/HCYjUM5jk8vVvUX JX+lyHDLWgfA9UbtI2X8ubQEFCNl1SYJrd258cLCTGkc+WLJ87xfM0d0tJhRTOOQqHS6 HdZQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=zuCZY4m4; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a1si9809938pld.249.2019.02.01.18.53.19; Fri, 01 Feb 2019 18:53:34 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=zuCZY4m4; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727454AbfBBCwt (ORCPT + 99 others); Fri, 1 Feb 2019 21:52:49 -0500 Received: from mail.kernel.org ([198.145.29.99]:57204 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726506AbfBBCws (ORCPT ); Fri, 1 Feb 2019 21:52:48 -0500 Received: from mail-wr1-f54.google.com (mail-wr1-f54.google.com [209.85.221.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B4021218FF for ; Sat, 2 Feb 2019 02:52:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1549075968; bh=kIGqXvcpyLnfAD3MHpZJsKj71GoTka2Lw9lznxRezNo=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=zuCZY4m4IyGnYksmS2iYk/Rlw61CbnTHHWXzuwpKAcnAiFrPnLAyWGSeX/2vCVtI5 L0vVk8AYYqx7AnkHkD/ppeOybItm0b92GSAyGdf46v9RQLJbEW1ulY0krmrxh/uIXJ 1BsMvDypJW8Eh1b00fKbfp8SR3+jKTbGAIQnd9Yc= Received: by mail-wr1-f54.google.com with SMTP id p4so9052666wrt.7 for ; Fri, 01 Feb 2019 18:52:47 -0800 (PST) X-Gm-Message-State: AJcUukfJhAB7OMigCDvbcVd34IyaOu0l8jA9Q5Y5Smyat7jm5xxVE/3q 5IJhlTove3pcrUMWnpEMxtrLMxglNWcJRNct2tK/OA== X-Received: by 2002:adf:8323:: with SMTP id 32mr39541754wrd.176.1549075966133; Fri, 01 Feb 2019 18:52:46 -0800 (PST) MIME-Version: 1.0 References: <20190201205319.15995-1-chang.seok.bae@intel.com> <20190201205319.15995-5-chang.seok.bae@intel.com> In-Reply-To: <20190201205319.15995-5-chang.seok.bae@intel.com> From: Andy Lutomirski Date: Fri, 1 Feb 2019 18:52:35 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v5 04/13] x86/fsgsbase/64: Add intrinsics for FSGSBASE instructions To: "Chang S. Bae" Cc: Andy Lutomirski , Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , Andi Kleen , Markus T Metzger , Ravi Shankar , LKML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 1, 2019 at 12:54 PM Chang S. Bae wrote: > > From: Andi Kleen > > Add C intrinsics and assembler macros for the new FSBASE and GSBASE > instructions. > > Very straight forward. Used in followon patches. > > [ luto: Rename the variables from FS and GS to FSBASE and GSBASE and > make safe to include on 32-bit kernels. ] > > v2: Use __always_inline > > [ chang: Revise the changelog. Place them in . Replace > the macros with GAS-compatible ones. ] > > If GCC supports it, we can add -mfsgsbase to CFLAGS and use the builtins > here for extra performance Does it really get better performance? If so, let's do it. If not, let's remove the comment. And, whatever you do, please put this above the [luto] and [chang] parts. . > > [ chang: Use FSGSBASE instructions directly. Removed GAS-compatible > macros as the minimum required binutils (v2.21) supports the FSGSBASE > instructions. ] Can you stick the "v2" revision notes below the --- or even just remove them? It makes the changelog a lot harder to review and it's not really useful in the git tree.