Received: by 10.192.165.156 with SMTP id m28csp2333953imm; Sat, 14 Apr 2018 21:29:11 -0700 (PDT) X-Google-Smtp-Source: AIpwx49x6+2Rxtco9M0gXaSAxVlqpvL9rhJyd8c8qWgOeFoKZrTcr5iUU0Kv4OQIF4Ee1wVk5eyj X-Received: by 10.98.144.85 with SMTP id a82mr11187433pfe.14.1523766551023; Sat, 14 Apr 2018 21:29:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523766550; cv=none; d=google.com; s=arc-20160816; b=zE6EBWfhE2y1sZqjtn4UokworvPBLA884GYb8mKYTof+hFFyyceQ8pcbiAmLGcUQVl RcnL3j87rFKTaSy1GbL9i706sxk/zlMQPkCYMDOahmlu2GpbseCGau9EuICEZDroEN5Z bLuKH9P+0Up2xk4cI0o/N3OZtiiBichFs+1u5ei+DrpjvHxnPB/MfEoIrubEJJ5fccIp QtbtdsfinSlBthH5boRtM25o0LBpqmAYN2qxirL4eh4ipqa1W6zGS5J3B3BQNE9QTUx9 c92LFVncYfrPDLFSdmVSIwohhFBndMjoUs2N0LO3I7KHshXsSTdf1fXO/D99LXWayc2h bAlQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:subject :smtp-origin-cluster:cc:to:smtp-origin-hostname:from :smtp-origin-hostprefix:dkim-signature:arc-authentication-results; bh=h6o4iJp6xm1rhSAdvDxXT8a5yAWS/2ptXoamMkl+jAY=; b=USQOWJWF4ZRMxWEN7CzPs0VubcQehVGa3aAKTsL0Y5OOYGx8ttJXP9F+EIDzyqtdcC ukvcDcIh4OcBP/DXXT7hFeEEszG8JPkILk9Kf7CM1iTEjGE3Q164eeXRQSgyqK1rbcQC BO6ttnwwiP9RjILIesfPxkEkGkPNDpQWUf/Eo6QWae7rwXsOsl+eEr1/XF+Dms5VErAy 8Ya45qzm84nlEoYdVABN+Qfsa5VwhqU4qxsLgX1W/yKN2a/57IWNOOmRiR4Ue0+h+3jf nAXV5qZx253wB3ddObuwLyNtKj/yz5J/lIgPMYtYgiHIhVT3jfdPOdi60VztvBF3u5n7 c6Zg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@fb.com header.s=facebook header.b=AERfmh75; 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=fb.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u6-v6si9555119plz.562.2018.04.14.21.28.55; Sat, 14 Apr 2018 21:29:10 -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; dkim=pass header.i=@fb.com header.s=facebook header.b=AERfmh75; 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=fb.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751065AbeDOE1r (ORCPT + 99 others); Sun, 15 Apr 2018 00:27:47 -0400 Received: from mx0a-00082601.pphosted.com ([67.231.145.42]:51046 "EHLO mx0a-00082601.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750704AbeDOE1q (ORCPT ); Sun, 15 Apr 2018 00:27:46 -0400 Received: from pps.filterd (m0109334.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w3F4OthZ026862 for ; Sat, 14 Apr 2018 21:27:45 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : mime-version : content-type; s=facebook; bh=h6o4iJp6xm1rhSAdvDxXT8a5yAWS/2ptXoamMkl+jAY=; b=AERfmh75gvrXy4ozr8nVkld/FUrjbVQsnSZQr1kjtISKexFD41yTZEc7+rdpCiAGvFfI VYVzxsVr7zGyBc/EXIzoERTwJElMic+Rxf2VRJzmSwqa5owV8gVUaaq0RitETHjO0UKj tFa0TLraP7b1E9eHl9rSrHYrkKB3o3ktm8A= Received: from mail.thefacebook.com ([199.201.64.23]) by mx0a-00082601.pphosted.com with ESMTP id 2hbuqf0870-5 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sat, 14 Apr 2018 21:27:45 -0700 Received: from mx-out.facebook.com (192.168.52.123) by PRN-CHUB05.TheFacebook.com (192.168.16.15) with Microsoft SMTP Server id 14.3.361.1; Sat, 14 Apr 2018 21:27:44 -0700 Received: by devbig474.prn1.facebook.com (Postfix, from userid 128203) id 22F86E4131B; Sat, 14 Apr 2018 21:27:38 -0700 (PDT) Smtp-Origin-Hostprefix: devbig From: Yonghong Song Smtp-Origin-Hostname: devbig474.prn1.facebook.com To: , , , , , CC: Smtp-Origin-Cluster: prn1c29 Subject: [PATCH v2] x86/cpufeature: guard asm_volatile_goto usage with NO_BPF_WORKAROUND Date: Sat, 14 Apr 2018 21:27:38 -0700 Message-ID: <20180415042738.1788215-1-yhs@fb.com> X-Mailer: git-send-email 2.9.5 X-FB-Internal: Safe MIME-Version: 1.0 Content-Type: text/plain X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-04-14_09:,, signatures=0 X-Proofpoint-Spam-Reason: safe X-FB-Internal: Safe Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Commit d0266046ad54 ("x86: Remove FAST_FEATURE_TESTS") removed X86_FAST_FEATURE_TESTS and make macro static_cpu_has() always use __always_inline function _static_cpu_has() funciton. The static_cpu_has() uses gcc feature asm_volatile_goto construct, which is not supported by clang. Currently, for BPF programs written in C, the only widely-supported compiler is clang. Because of clang lacking support of asm_volatile_goto construct, if you try to compile bpf programs under samples/bpf/, $ make -j20 && make headers_install && make samples/bpf/ you will see a lot of failures like below: ========================= clang -nostdinc -isystem /usr/lib/gcc/x86_64-redhat-linux/7/include \ -I/home/yhs/work/bpf-next/arch/x86/include \ -I./arch/x86/include/generated -I/home/yhs/work/bpf-next/include \ -I./include -I/home/yhs/work/bpf-next/arch/x86/include/uapi \ -I./arch/x86/include/generated/uapi \ -I/home/yhs/work/bpf-next/include/uapi -I./include/generated/uapi \ -include /home/yhs/work/bpf-next/include/linux/kconfig.h -Isamples/bpf \ -I/home/yhs/work/bpf-next/tools/testing/selftests/bpf/ \ -D__KERNEL__ -Wno-unused-value -Wno-pointer-sign \ -D__TARGET_ARCH_x86 -Wno-compare-distinct-pointer-types \ -Wno-gnu-variable-sized-type-not-at-end \ -Wno-address-of-packed-member -Wno-tautological-compare \ -Wno-unknown-warning-option \ -O2 -emit-llvm -c /home/yhs/work/bpf-next/samples/bpf/xdp_redirect_cpu_kern.c \ -o -| llc -march=bpf -filetype=obj -o samples/bpf/xdp_redirect_cpu_kern.o In file included from /home/yhs/work/bpf-next/samples/bpf/xdp_redirect_cpu_kern.c:10: In file included from /home/yhs/work/bpf-next/include/uapi/linux/in.h:24: In file included from /home/yhs/work/bpf-next/include/linux/socket.h:8: In file included from /home/yhs/work/bpf-next/include/linux/uio.h:13: In file included from /home/yhs/work/bpf-next/include/linux/thread_info.h:38: In file included from /home/yhs/work/bpf-next/arch/x86/include/asm/thread_info.h:53: /home/yhs/work/bpf-next/arch/x86/include/asm/cpufeature.h:150:2: error: 'asm goto' constructs are not supported yet asm_volatile_goto("1: jmp 6f\n" ^ /home/yhs/work/bpf-next/include/linux/compiler-gcc.h:296:42: note: expanded from macro 'asm_volatile_goto' #define asm_volatile_goto(x...) do { asm goto(x); asm (""); } while (0) ^ 1 error generated. ========================= ... In file included from /home/yhs/work/bpf-next/samples/bpf/tracex4_kern.c:7: In file included from /home/yhs/work/bpf-next/include/linux/ptrace.h:6: In file included from /home/yhs/work/bpf-next/include/linux/sched.h:14: In file included from /home/yhs/work/bpf-next/include/linux/pid.h:5: In file included from /home/yhs/work/bpf-next/include/linux/rculist.h:11: In file included from /home/yhs/work/bpf-next/include/linux/rcupdate.h:40: In file included from /home/yhs/work/bpf-next/include/linux/preempt.h:81: In file included from /home/yhs/work/bpf-next/arch/x86/include/asm/preempt.h:7: In file included from /home/yhs/work/bpf-next/include/linux/thread_info.h:38: In file included from /home/yhs/work/bpf-next/arch/x86/include/asm/thread_info.h:53: /home/yhs/work/bpf-next/arch/x86/include/asm/cpufeature.h:150:2: error: 'asm goto' constructs are not supported yet ... ========================= This patch adds a preprocessor guard NO_BPF_WORKAROUND around the asm_volatile_goto based static_cpu_has(). NO_BPF_WORKAROUND is set at toplevel Makefile when compiler supports asm-goto. That is, if the compiler supports asm-goto, the kernel build will use asm-goto version of static_cpu_has(). For clang compilation for bpf programs where only header files are accessed, NO_BPF_WORKAROUND is not defined and asm-goto version of static_cpu_has() will not be accessed, hence the above compilation error will disappear. If later clang compiler starts to support asm_volatile_goto, the change in this patch can be reverted. Fixes: d0266046ad54 ("x86: Remove FAST_FEATURE_TESTS") Suggested-by: Alexei Starovoitov Signed-off-by: Yonghong Song --- Makefile | 1 + arch/x86/include/asm/cpufeature.h | 5 +++++ 2 files changed, 6 insertions(+) Changelog: v1 -> v2: Use NO_BPF_WORKAROUND macro instead of CC_HAVE_ASM_GOTO to make it explicit that this is a workaround. diff --git a/Makefile b/Makefile index c1a608a..7b81f1f 100644 --- a/Makefile +++ b/Makefile @@ -504,6 +504,7 @@ export RETPOLINE_CFLAGS ifeq ($(call shell-cached,$(CONFIG_SHELL) $(srctree)/scripts/gcc-goto.sh $(CC) $(KBUILD_CFLAGS)), y) CC_HAVE_ASM_GOTO := 1 KBUILD_CFLAGS += -DCC_HAVE_ASM_GOTO + KBUILD_CFLAGS += -DNO_BPF_WORKAROUND KBUILD_AFLAGS += -DCC_HAVE_ASM_GOTO endif diff --git a/arch/x86/include/asm/cpufeature.h b/arch/x86/include/asm/cpufeature.h index b27da96..638417b 100644 --- a/arch/x86/include/asm/cpufeature.h +++ b/arch/x86/include/asm/cpufeature.h @@ -140,6 +140,8 @@ extern void clear_cpu_cap(struct cpuinfo_x86 *c, unsigned int bit); #define setup_force_cpu_bug(bit) setup_force_cpu_cap(bit) +/* this macro is a temporary hack for bpf until clang gains asm-goto support */ +#ifdef NO_BPF_WORKAROUND /* * Static testing of CPU features. Used the same as boot_cpu_has(). * These will statically patch the target code for additional @@ -195,6 +197,9 @@ static __always_inline __pure bool _static_cpu_has(u16 bit) boot_cpu_has(bit) : \ _static_cpu_has(bit) \ ) +#else +#define static_cpu_has(bit) boot_cpu_has(bit) +#endif #define cpu_has_bug(c, bit) cpu_has(c, (bit)) #define set_cpu_bug(c, bit) set_cpu_cap(c, (bit)) -- 2.9.5