Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp1228179ybp; Fri, 4 Oct 2019 11:21:39 -0700 (PDT) X-Google-Smtp-Source: APXvYqwdWVrua9uMKG4f9Iq4t8FtOp+huKrJGkTORsa5aDgvrvDQQ3pUp+WUp5XOzMm0rG/bYf2M X-Received: by 2002:a17:906:2f03:: with SMTP id v3mr6202512eji.333.1570213299832; Fri, 04 Oct 2019 11:21:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570213299; cv=none; d=google.com; s=arc-20160816; b=F+t7QlYidpVzGOB3G1lyC8ydwLPKFUJA+cIV84iZL8tVpt+JaYgL4s82CRB9tBdSo8 zTYYFD9wmqJAa/7Cg79dqOC+AoqwU1grHGvEpvF6w3qucbdObd/OCr9qAAGjttkD5P1Q iNLRKC830YcTkm9ydUVf3khqPcS1JXkC59BRNm8Gk1QZ7Gd+htMmNY0l8FNzdyhxX2Tn 2IjRSQF8qRwE0Hxi4u8dT05VKWTIHQOq3s+BXUR4mekmrjXRgVyBe6e7Qo2DwbmUvrEm ivnXyxHYG7matlKhbMoSC4FDpHNaoITQIe4XZ0eLCN/zjZE85JbSlgToUz7T9r7DA75U 6mXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from; bh=v0w8+ysyGHn8nsOtgGl+3s2als6vX85MsJ7+eg3B9jA=; b=HlqmGIo//CAdAsNkYzSwO+ZS+Ym9M8IgO/PZni7fn6bPd8OEdLGteadHRjxEnIk1cn 2xc6Cdf2DfwRQWXBKijBj+ei9HNt+Xa+cybhWTxJwrr9typ1kf7GXYSH29Z2f6fSU6g/ 4qSGyax2NLJFMCnaqoPA/BKtXzEk8tkGNj3zVNAAa7ZesIWbFiVQml9ldfCY8x4raBD8 3mX59fCIqPJ8JfWYvW/htXPRrb6gjp7lSmtOWgopAsNsRZqFU7txdlkYK/+hcmbgKuvT gp++6GetiFSisByNaph22UOb1km6SLtv2X2x+CVsedWoreD6xMk/XMWQFkOg8k0Ly4CD DxbQ== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b13si4042542edy.320.2019.10.04.11.21.15; Fri, 04 Oct 2019 11:21:39 -0700 (PDT) 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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388890AbfJDSRP (ORCPT + 99 others); Fri, 4 Oct 2019 14:17:15 -0400 Received: from mga07.intel.com ([134.134.136.100]:15536 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388618AbfJDSRH (ORCPT ); Fri, 4 Oct 2019 14:17:07 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Oct 2019 11:17:07 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.67,257,1566889200"; d="scan'208";a="204394825" Received: from chang-linux-3.sc.intel.com ([172.25.66.185]) by orsmga002.jf.intel.com with ESMTP; 04 Oct 2019 11:17:07 -0700 From: "Chang S. Bae" To: linux-kernel@vger.kernel.org, tglx@linutronix.de, bp@alien8.de, luto@kernel.org Cc: hpa@zytor.com, dave.hansen@intel.com, tony.luck@intel.com, ak@linux.intel.com, ravi.v.shankar@intel.com, chang.seok.bae@intel.com Subject: [PATCH v9 16/17] x86/elf: Enumerate kernel FSGSBASE capability in AT_HWCAP2 Date: Fri, 4 Oct 2019 11:16:08 -0700 Message-Id: <1570212969-21888-17-git-send-email-chang.seok.bae@intel.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1570212969-21888-1-git-send-email-chang.seok.bae@intel.com> References: <1570212969-21888-1-git-send-email-chang.seok.bae@intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Andi Kleen The kernel needs to explicitly enable FSGSBASE. So, the application needs to know if it can safely use these instructions. Just looking at the CPUID bit is not enough because it may be running in a kernel that does not enable the instructions. One way for the application would be to just try and catch the SIGILL. But that is difficult to do in libraries which may not want to overwrite the signal handlers of the main application. Enumerate the enabled FSGSBASE capability in bit 1 of AT_HWCAP2 in the ELF aux vector. AT_HWCAP2 is already used by PPC for similar purposes. The application can access it open coded or by using the getauxval() function in newer versions of glibc. Signed-off-by: Andi Kleen Signed-off-by: Chang S. Bae Reviewed-by: Tony Luck Cc: Thomas Gleixner Cc: Borislav Petkov Cc: Andy Lutomirski Cc: H. Peter Anvin Cc: Dave Hansen Cc: Tony Luck Cc: Andi Kleen --- Changes from v8: none Changes from v7: * No code change * Massaged changelog by Thomas --- arch/x86/include/uapi/asm/hwcap2.h | 3 +++ arch/x86/kernel/cpu/common.c | 4 +++- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/arch/x86/include/uapi/asm/hwcap2.h b/arch/x86/include/uapi/asm/hwcap2.h index 8b2effe..5fdfcb4 100644 --- a/arch/x86/include/uapi/asm/hwcap2.h +++ b/arch/x86/include/uapi/asm/hwcap2.h @@ -5,4 +5,7 @@ /* MONITOR/MWAIT enabled in Ring 3 */ #define HWCAP2_RING3MWAIT (1 << 0) +/* Kernel allows FSGSBASE instructions available in Ring 3 */ +#define HWCAP2_FSGSBASE BIT(1) + #endif diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c index 9b59377bb..90d7e95 100644 --- a/arch/x86/kernel/cpu/common.c +++ b/arch/x86/kernel/cpu/common.c @@ -1472,8 +1472,10 @@ static void identify_cpu(struct cpuinfo_x86 *c) setup_umip(c); /* Enable FSGSBASE instructions if available. */ - if (cpu_has(c, X86_FEATURE_FSGSBASE)) + if (cpu_has(c, X86_FEATURE_FSGSBASE)) { cr4_set_bits(X86_CR4_FSGSBASE); + elf_hwcap2 |= HWCAP2_FSGSBASE; + } /* * The vendor-specific functions might have changed features. -- 2.7.4