Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp1408451ybp; Wed, 9 Oct 2019 13:42:23 -0700 (PDT) X-Google-Smtp-Source: APXvYqwGDe6w0yRrz9Dm10d7tW99l7Svdq+Eq+uf2BSOlMFNuklAczOamwT6QHkexONxlENq6SOR X-Received: by 2002:a05:6402:6c9:: with SMTP id n9mr4670203edy.190.1570653743503; Wed, 09 Oct 2019 13:42:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570653743; cv=none; d=google.com; s=arc-20160816; b=g0a99unian12Icw8yX2U7NvnEDwa73WmWV6nhETTW26HCCLKZbuuERGasrkx6LkQP6 so9g4bJ00461aXTAZ/lI9/D+GO1fVuEmUUVRdjtJNUxYXd3T6+cetodF7VnqhB8ypUKH BIF/ynsb8vnLbzD3fHiF6YL4ip8+Sovw0ESdRIqcWpdgchGHMky1br8qxgbGjF1vC709 piQ3OyQLNAENP299IHyvpOHTKIX376OxgT0zeE2uLtR3HNrJCOJBwRqrPrKoHlppnusk lsN1uF2UjHsciB5MaGlKEBaFQ14fPZ/mLiDGevdYaFEWMYnYIuLKaOAiOkOkapOlmE1s S0Mg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :dkim-signature; bh=tKxIqZaGiIZbrcpQmZNhRc78ngIxmKtJ7WH1CMEhs2I=; b=PAm4kRchhNTZm5ExgzUkxroqgj8mNUnQ0xOOBfnPcITui0YygLwstqrvMtoY39Q92P pZfz7P6jqFObLYWzKNbW5+l+4T1yyxvWhoXPMmuYRExbOO6Hllj+Eb1O2GRt2zPvLrFU RCJDOcHrP5LEzw4eFcMpSc9RxvVuY27/yjOkupavezlwevlGRN/n4Lf92xoRIhz0T+9T RIyURZJoldiBz7Fje0NqTbe/wio9wJQ+7h9WJGLEP3mgNHpsnV92lGCQlC+KmYn2BOW3 B6uY/Ph07Y4jpr9uEQgq6m9ralhkPBhZnIMqkw/9YpZTZv+iRLcqHN0UzzKPw0qheN7c fI+g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=WxNv25vr; 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=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q13si1847077eju.46.2019.10.09.13.41.59; Wed, 09 Oct 2019 13:42:23 -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=@linaro.org header.s=google header.b=WxNv25vr; 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=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731878AbfJIUlo (ORCPT + 99 others); Wed, 9 Oct 2019 16:41:44 -0400 Received: from mail-lj1-f195.google.com ([209.85.208.195]:44714 "EHLO mail-lj1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731792AbfJIUlo (ORCPT ); Wed, 9 Oct 2019 16:41:44 -0400 Received: by mail-lj1-f195.google.com with SMTP id m13so3837698ljj.11 for ; Wed, 09 Oct 2019 13:41:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id; bh=tKxIqZaGiIZbrcpQmZNhRc78ngIxmKtJ7WH1CMEhs2I=; b=WxNv25vrnjt4D1lt3yzvx28MGV/CRGv+OcBswnLQs52baGdH9kyk2XmTWFLi1vx56m xr8BZGbgRMQQFBMot/4hsnIbNTYSzHcvjwKrdgTZgWMzVFGlC7n6/drmeqzDn/vthXAa MMVr6AV36/+f2Didl3WLclx2fFoUjZ78jWmxtwHLoc50XAtgFk0EbbNqgid+CwLfF0FG PNeQNIqvgYpYnAJOptZoj1sq3t6ohc2a8BWj5AnyfDwF6fn6fnzLNftzfyLZGUmQ3UFx dF/CLm6BJ2+0r6kWiNTm1Nm4MvqEOSf2hvODXCCdcBK81RNPnKosS0/qws79Ujtohfrp ZTyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=tKxIqZaGiIZbrcpQmZNhRc78ngIxmKtJ7WH1CMEhs2I=; b=H9YQtmx7hG+KorR1PC5B7dVXI+SLDWwoZwj+yqRlqt1+S/gsNTgHH6aCvHdhs3qssp sT/JrVtU7GjKevofXxmUzhoMUrc5R86ikgCZEi5mTNSgBmWl5VLlD/zkM4ucYcCCyVSy IKdIR9up8fyDkOUTAm3zLfTmiQCtDBY4bK9uWdYUB6WJE5jh7/Nw1Z3NFiycMG+w1uuc oYAUiFqmjrgjrkQRIaKzjsNTpegvLTs+gFKIDdzuOeC9fT1DdHadbiCJxUwk7xJdtClg IcnXZFh8mtYddbUfXA6Mm9QqhLkwP7gS7xXryzcW0CXQncy4Zv8ufaiTqLh9uZHhJ0/V xH/Q== X-Gm-Message-State: APjAAAVgh+uM32Qi7wwCp5yoh7kbEP08/xRsNwyjOdTp1+p8o3kLTHKB Wdgk0Ty4B3ywL68op9VRkmmI1A== X-Received: by 2002:a2e:8310:: with SMTP id a16mr3673167ljh.48.1570653699554; Wed, 09 Oct 2019 13:41:39 -0700 (PDT) Received: from localhost.localdomain (168-200-94-178.pool.ukrtel.net. [178.94.200.168]) by smtp.gmail.com with ESMTPSA id h3sm730871ljf.12.2019.10.09.13.41.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 09 Oct 2019 13:41:38 -0700 (PDT) From: Ivan Khoronzhuk To: ast@kernel.org, daniel@iogearbox.net, yhs@fb.com, davem@davemloft.net, jakub.kicinski@netronome.com, hawk@kernel.org, john.fastabend@gmail.com Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org, clang-built-linux@googlegroups.com, ilias.apalodimas@linaro.org, sergei.shtylyov@cogentembedded.com, Ivan Khoronzhuk Subject: [PATCH v4 bpf-next 00/15] samples: bpf: improve/fix cross-compilation Date: Wed, 9 Oct 2019 23:41:19 +0300 Message-Id: <20191009204134.26960-1-ivan.khoronzhuk@linaro.org> X-Mailer: git-send-email 2.17.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This series contains mainly fixes/improvements for cross-compilation but not only, tested for arm, arm64, and intended for any arch. Also verified on native build (not cross compilation) for x86_64 and arm, arm64. Initial RFC link: https://lkml.org/lkml/2019/8/29/1665 Prev. version: https://lkml.org/lkml/2019/9/16/231 Besides the patches given here, the RFC also contains couple patches related to llvm clang arm: include: asm: swab: mask rev16 instruction for clang arm: include: asm: unified: mask .syntax unified for clang They are necessarily to verify arm 32 build. Also, couple more fixes were added but are not merged in bpf-next yet, they can be needed for verification/configuration steps, if not in your tree the fixes can be taken here: https://www.spinics.net/lists/netdev/msg601716.html https://www.spinics.net/lists/netdev/msg601714.html https://www.spinics.net/lists/linux-kbuild/msg23468.html Now, to build samples, SAMPLE_BPF should be enabled in config. The change touches not only cross-compilation and can have impact on other archs and build environments, so might be good idea to verify it in order to add appropriate changes, some warn options could be tuned also. All is tested on x86-64 with clang installed (has to be built containing targets for arm, arm64..., see llc --version, usually it's present already) Instructions to test native on x86_64 ================================================= Native build on x86_64 is done in usual way and shouldn't have difference except HOSTCC is now printed as CC wile building the samples. Instructions to test cross compilation on arm64 ================================================= #Toolchain used for test: gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) # Get some arm64 FS, containing at least libelf I've used sdk for TI am65x got here: http://downloads.ti.com/processor-sdk-linux/esd/AM65X/latest/exports/\ ti-processor-sdk-linux-am65xx-evm-06.00.00.07-Linux-x86-Install.bin # Install this binary to some dir, say "sdk". # Configure kernel (use defconfig as no matter), but clean everything # before. make ARCH=arm64 -C tools/ clean make ARCH=arm64 -C samples/bpf clean make ARCH=arm64 clean make ARCH=arm64 defconfig # Enable SAMPLE_BPF and it's dependencies in config # The kernel version used in sdk doesn't correspond to checked one, # but for this verification only headers need to be syched, # so install them (can be enabled in config): make ARCH=arm64 headers_install # or on SDK if need keep them in sync (not necessarily to verify): make ARCH=arm64 INSTALL_HDR_PATH=/../sdk/\ ti-processor-sdk-linux-am65xx-evm-06.00.00.07/linux-devkit/sysroots/\ aarch64-linux/usr headers_install # Build samples make samples/bpf/ ARCH=arm64 CROSS_COMPILE="aarch64-linux-gnu-"\ SYSROOT="/../sdk/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/\ linux-devkit/sysroots/aarch64-linux" Instructions to test cross compilation on arm ================================================= #Toolchains used for test: arm-linux-gnueabihf-gcc (Linaro GCC 7.2-2017.11) 7.2.1 20171011 or arm-linux-gnueabihf-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 \ (arm-rel-8.36)) 8.3.0 # Get some FS, I've used sdk for TI am52xx got here: http://downloads.ti.com/processor-sdk-linux/esd/AM57X/05_03_00_07/exports/\ ti-processor-sdk-linux-am57xx-evm-05.03.00.07-Linux-x86-Install.bin # Install this binary to some dir, say "sdk". # Configure kernel, but clean everything before. make ARCH=arm -C tools/ clean make ARCH=arm -C samples/bpf clean make ARCH=arm clean make ARCH=arm omap2plus_defconfig # The kernel version used in sdk doesn't correspond to checked one, but # headers only should be synched, # so install them (can be enabled in config): make ARCH=arm headers_install # or on SDK if need keep them in sync (not necessarily): make ARCH=arm INSTALL_HDR_PATH=/../sdk/\ ti-processor-sdk-linux-am57xx-evm-05.03.00.07/linux-devkit/sysroots/\ armv7ahf-neon-linux-gnueabi/usr headers_install # Build samples make samples/bpf/ ARCH=arm CROSS_COMPILE="arm-linux-gnueabihf-"\ SYSROOT="/../sdk/ti-processor-sdk-linux-am57xx-evm-05.03\ .00.07/linux-devkit/sysroots/armv7ahf-neon-linux-gnueabi" Based on bpf-next/master v4..v3: - renamed CLANG_EXTRA_CFLAGS on BPF_EXTRA_CFLAGS - used filter for ARCH_ARM_SELECTOR - omit "-fomit-frame-pointer" and use same flags for native and "cross" - used sample/bpf prefixes - use C instead of C++ compiler for test_libbpf target v3..v2: - renamed makefile.progs to makeifle.target, as more appropriate - left only __LINUX_ARM_ARCH__ for D options for arm - for host build - left options from KBUILD_HOST for compatibility reasons - split patch adding c/cxx/ld flags to libbpf by modules - moved readme change to separate patch - added patch setting options for cross-compile - fixed issue with option error for syscall_nrs.S, avoiding overlap for ccflags-y. v2..v1: - restructured patches order - split "samples: bpf: Makefile: base progs build on Makefile.progs" to make change more readable. It added couple nice extra patches. - removed redundant patch: "samples: bpf: Makefile: remove target for native build" - added fix: "samples: bpf: makefile: fix cookie_uid_helper_example obj build" - limited -D option filter only for arm - improved comments - added couple instructions to verify cross compilation for arm and arm64 arches based on TI am57xx and am65xx sdks. - corrected include a little order Ivan Khoronzhuk (15): samples/bpf: fix HDR_PROBE "echo" samples/bpf: fix cookie_uid_helper_example obj build samples/bpf: use --target from cross-compile samples/bpf: use own EXTRA_CFLAGS for clang commands samples/bpf: use __LINUX_ARM_ARCH__ selector for arm samples/bpf: drop unnecessarily inclusion for bpf_load samples/bpf add makefile.target for separate CC target build samples/bpf: base target programs rules on Makefile.target samples/bpf: use own flags but not HOSTCFLAGS samples/bpf: use target CC environment for HDR_PROBE libbpf: don't use cxx to test_libpf target libbpf: add C/LDFLAGS to libbpf.so and test_libpf targets samples/bpf: provide C/LDFLAGS to libbpf samples/bpf: add sysroot support samples/bpf: add preparation steps and sysroot info to readme samples/bpf/Makefile | 164 ++++++++++-------- samples/bpf/Makefile.target | 75 ++++++++ samples/bpf/README.rst | 41 ++++- tools/lib/bpf/Makefile | 23 +-- .../bpf/{test_libbpf.cpp => test_libbpf.c} | 14 +- 5 files changed, 218 insertions(+), 99 deletions(-) create mode 100644 samples/bpf/Makefile.target rename tools/lib/bpf/{test_libbpf.cpp => test_libbpf.c} (61%) -- 2.17.1