From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3A633C56201 for ; Fri, 20 Nov 2020 04:05:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CFFA722365 for ; Fri, 20 Nov 2020 04:04:59 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="QAJ7dC+j" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726485AbgKTEEi (ORCPT ); Thu, 19 Nov 2020 23:04:38 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:58925 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726105AbgKTEEi (ORCPT ); Thu, 19 Nov 2020 23:04:38 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1605845077; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=o2KUuc5wwsBwxaFKsqE+AT6g8ZgQDPHa1BC4D1RcHko=; b=QAJ7dC+jIYsdyzBghu3FHiqv+OL8V9WfweQXvabDm0BuyD2fUVodeXv9ZSzivR3XgbNV/9 zHJUJxTdFwFOenytSIrWixG0LeCLX+vakVbyd9H9RKRHaz7jpzN0vIdQ84bnrJGoWlABzE 7UQhpSn87Kq+F1ruZxfdoTXRYHzCfsc= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-230-yDf3VGw1POqCQOhtPJpkwQ-1; Thu, 19 Nov 2020 23:04:33 -0500 X-MC-Unique: yDf3VGw1POqCQOhtPJpkwQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 126894236B; Fri, 20 Nov 2020 04:04:31 +0000 (UTC) Received: from treble (ovpn-119-150.rdu2.redhat.com [10.10.119.150]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 90D3019C47; Fri, 20 Nov 2020 04:04:27 +0000 (UTC) Date: Thu, 19 Nov 2020 22:04:24 -0600 From: Josh Poimboeuf To: Sami Tolvanen Cc: Masahiro Yamada , Steven Rostedt , Will Deacon , Peter Zijlstra , Greg Kroah-Hartman , "Paul E. McKenney" , Kees Cook , Nick Desaulniers , clang-built-linux@googlegroups.com, kernel-hardening@lists.openwall.com, linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org Subject: Re: [PATCH v7 00/17] Add support for Clang LTO Message-ID: <20201120040424.a3wctajzft4ufoiw@treble> References: <20201118220731.925424-1-samitolvanen@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20201118220731.925424-1-samitolvanen@google.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 18, 2020 at 02:07:14PM -0800, Sami Tolvanen wrote: > This patch series adds support for building the kernel with Clang's > Link Time Optimization (LTO). In addition to performance, the primary > motivation for LTO is to allow Clang's Control-Flow Integrity (CFI) to > be used in the kernel. Google has shipped millions of Pixel devices > running three major kernel versions with LTO+CFI since 2018. > > Most of the patches are build system changes for handling LLVM bitcode, > which Clang produces with LTO instead of ELF object files, postponing > ELF processing until a later stage, and ensuring initcall ordering. > > Note that v7 brings back arm64 support as Will has now staged the > prerequisite memory ordering patches [1], and drops x86_64 while we work > on fixing the remaining objtool warnings [2]. Sami, Here are some patches to fix the objtool issues (other than crypto which I'll work on next). https://git.kernel.org/pub/scm/linux/kernel/git/jpoimboe/linux.git objtool-vmlinux -- Josh From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B69F9C5519F for ; Fri, 20 Nov 2020 04:05:55 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3734B21D40 for ; Fri, 20 Nov 2020 04:05:55 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="L79b0lyS"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="QAJ7dC+j" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3734B21D40 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=9C9SIGm1KW2UHmclpkWB1AuLJE+DeUhDgvmvpR1PV70=; b=L79b0lySRLKImfNdCm+20I+u/ CsILciyyg/6axt4YEbI0fk8riqdMEvNE+h/FqLg8v9PsMzomTrkTKCSfs3V5oCUZXDuYElckKCNac FWRvfLtbrt7GbZoNUUJDjefFVud8TuU2CIjy5AkPwyQigzg0u8ToTdhW340JsEUzWTo2kc6c6/lyn zJfoiuhGl3FKqH9qmqnX+53++tM94Ra36fgktkUfyA0LZ0Bn6PIO05TzBvm1tIF1f52VfcDt/Zc/c gPY84Bfme23myd/61kdp0hDlIoht2JJ9cC/FBF67wKds/a3GRBwt88fVFjhrLiLQf+SF/n4pYa2Uh EPIqKDwsA==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kfxf8-0005Ur-Mh; Fri, 20 Nov 2020 04:04:42 +0000 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kfxf5-0005UE-5W for linux-arm-kernel@lists.infradead.org; Fri, 20 Nov 2020 04:04:40 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1605845077; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=o2KUuc5wwsBwxaFKsqE+AT6g8ZgQDPHa1BC4D1RcHko=; b=QAJ7dC+jIYsdyzBghu3FHiqv+OL8V9WfweQXvabDm0BuyD2fUVodeXv9ZSzivR3XgbNV/9 zHJUJxTdFwFOenytSIrWixG0LeCLX+vakVbyd9H9RKRHaz7jpzN0vIdQ84bnrJGoWlABzE 7UQhpSn87Kq+F1ruZxfdoTXRYHzCfsc= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-230-yDf3VGw1POqCQOhtPJpkwQ-1; Thu, 19 Nov 2020 23:04:33 -0500 X-MC-Unique: yDf3VGw1POqCQOhtPJpkwQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 126894236B; Fri, 20 Nov 2020 04:04:31 +0000 (UTC) Received: from treble (ovpn-119-150.rdu2.redhat.com [10.10.119.150]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 90D3019C47; Fri, 20 Nov 2020 04:04:27 +0000 (UTC) Date: Thu, 19 Nov 2020 22:04:24 -0600 From: Josh Poimboeuf To: Sami Tolvanen Subject: Re: [PATCH v7 00/17] Add support for Clang LTO Message-ID: <20201120040424.a3wctajzft4ufoiw@treble> References: <20201118220731.925424-1-samitolvanen@google.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20201118220731.925424-1-samitolvanen@google.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20201119_230439_401144_F1A7E27F X-CRM114-Status: GOOD ( 19.59 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-arch@vger.kernel.org, Kees Cook , "Paul E. McKenney" , kernel-hardening@lists.openwall.com, Peter Zijlstra , Greg Kroah-Hartman , Masahiro Yamada , linux-kbuild@vger.kernel.org, Nick Desaulniers , linux-kernel@vger.kernel.org, Steven Rostedt , clang-built-linux@googlegroups.com, linux-pci@vger.kernel.org, Will Deacon , linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Nov 18, 2020 at 02:07:14PM -0800, Sami Tolvanen wrote: > This patch series adds support for building the kernel with Clang's > Link Time Optimization (LTO). In addition to performance, the primary > motivation for LTO is to allow Clang's Control-Flow Integrity (CFI) to > be used in the kernel. Google has shipped millions of Pixel devices > running three major kernel versions with LTO+CFI since 2018. > > Most of the patches are build system changes for handling LLVM bitcode, > which Clang produces with LTO instead of ELF object files, postponing > ELF processing until a later stage, and ensuring initcall ordering. > > Note that v7 brings back arm64 support as Will has now staged the > prerequisite memory ordering patches [1], and drops x86_64 while we work > on fixing the remaining objtool warnings [2]. Sami, Here are some patches to fix the objtool issues (other than crypto which I'll work on next). https://git.kernel.org/pub/scm/linux/kernel/git/jpoimboe/linux.git objtool-vmlinux -- Josh _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel