Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp4992342ybb; Tue, 24 Mar 2020 09:00:31 -0700 (PDT) X-Google-Smtp-Source: ADFU+vu2Hte3a6b4e7LDHf3D8eYyyhiJut8M6Y6Dk2psfUsyS/Nnf9UACwnplSaOTZ6hvoMs209D X-Received: by 2002:a05:6830:1581:: with SMTP id i1mr21458752otr.349.1585065631164; Tue, 24 Mar 2020 09:00:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585065631; cv=none; d=google.com; s=arc-20160816; b=CyVnaB4qQAJZ1M5+OKJjwVb1bAmixi/cPKtYHkzKsMnlVCHgYdJ0RMkzWsTRbnzmL6 kcN78u8TzD/+kU8S5C2+NsppTyJeHvMqeSeNXGL9sDWEf7DOsFdarkK0nWZOH+RbVsWd KF9cL+IAi4Q5gg7n5VWVFMkk+60CNsKdp9w+ZE2pau/fCB/kDbpOtw5ZYCqIziBLyn4+ 4gHW8czlkQoGsndWBypF4PHfoMV6gJ5vw9A2zFUTzgsxIFuPcwCc2FaJZc2BYj27bU+s JFfpAOoWq4Qk6LEmzOom6XEwY5kt+zJb66KF/iWrT5iiKDAy+t9Lp6mxgZjJXMHeNkP1 a6yQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:cc:from:subject:references :mime-version:message-id:in-reply-to:date:dkim-signature; bh=6vaPWbP6ANUHUHOz8sns0zk878oxF/Up8fDXRsjlrW0=; b=TWd/FJ33WMo1P3Vr3OfiCyFhh70jXURYL8U8Tkll02gtrt4uHvJ+MqLvvQzsHcdEs+ QcrF9d4J4h8wgOdANBGNI2m6wY9qzrIwRtxahj/TnzLYoWV5ngi25fO2zjkc5a9zl3Ec WiTjHfX0DAmTUFHCI3vqhM+1PCSrOF+MY1bUEHq+GyUTzHcqs65uYxx5hRMKT6BfvErN cTMSZiu/lhS2Rsg1nIMZrmBePpI8ixv2R7Qtn2MxFu1epGOXaRCF3T4gl6vxqbqtSfoq iDn8C42fc7NTmPQSO9mHsA22fTO8h2hJsBHHHT8VHAiTBLKlYNzWLZNVv4Utbp44Tk0f rMmw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=PhzSoHHg; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d20si9335964oti.311.2020.03.24.09.00.17; Tue, 24 Mar 2020 09:00:31 -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=@google.com header.s=20161025 header.b=PhzSoHHg; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728339AbgCXP72 (ORCPT + 99 others); Tue, 24 Mar 2020 11:59:28 -0400 Received: from mail-wr1-f73.google.com ([209.85.221.73]:42129 "EHLO mail-wr1-f73.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727665AbgCXP72 (ORCPT ); Tue, 24 Mar 2020 11:59:28 -0400 Received: by mail-wr1-f73.google.com with SMTP id o18so6027748wrx.9 for ; Tue, 24 Mar 2020 08:59:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:in-reply-to:message-id:mime-version:references:subject:from:cc; bh=6vaPWbP6ANUHUHOz8sns0zk878oxF/Up8fDXRsjlrW0=; b=PhzSoHHgm6kzqXckUj1hMJQQ00oWqkLQlPCoaVh2BlJzOv7otdTlVHco/J8wUFyoyU sRv2K12f0v7HbtkZXjfqo14K+kBYEg4LIDXNNy7rcLtJqtN9kl0lOAUuaFiYVB1wt7F1 LdfNOyWEu1SSkJ4wpcuhs+fE990IJV/sELuU0t7W/miqEVL0y/OjIZLDbwJq8ERXC/lJ /xDui9edLVHi+oUutjdZCSf02cK8rFjNrS6Puql6opfvPr954sxDjsDzjIO4CgR3tAqr m9x7M30492yYD+ZzIfzSCvTVWvNR0tSoSOXTrWN9caBXY34h9BOLbXI4arRUz0YpywxJ y6aw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:in-reply-to:message-id:mime-version :references:subject:from:cc; bh=6vaPWbP6ANUHUHOz8sns0zk878oxF/Up8fDXRsjlrW0=; b=QxgGt5xy4kvg3TzJRrPEcPG8NDhK0cNSk8uzIOdHLEJ07ya+qbeyAh2myiFIXecRmG 3zVS+djRh6qZj0hUZ2gGGZIp2g6yAmttJJLhZswurpqL2I02qT6n/SXeQkrY+39llGea JLm5BsZshQFUoUKILDKwS/ait8zwLY8GJvGk48EehZrg9XK4Kf9jcTyilaKmAzzcWPaC TQ8GMnV0z2b00FMF4+MbeCRvpJ6otFSO51I0DV8C5lBBjdFDkULoCky/sN4W1tyYBzqA WsLjdBKo9mPRHiuG26/q0793q2WjSm5rJG36y4YxUNzOFH1U6qNDWR9sEKBjf63/Fu9b 5pCw== X-Gm-Message-State: ANhLgQ3582C1hxfsLFIYF5PnkfW9CtWg9vE8siE+60BuOWWGpQbcfQ5G B3/r2tCPCXFKunqoqp3H8IiUuXGtImBz X-Received: by 2002:a5d:69c7:: with SMTP id s7mr36849068wrw.165.1585065564454; Tue, 24 Mar 2020 08:59:24 -0700 (PDT) Date: Tue, 24 Mar 2020 16:59:06 +0100 In-Reply-To: <20200323114207.222412-1-courbet@google.com> Message-Id: <20200324155907.97184-1-courbet@google.com> Mime-Version: 1.0 References: <20200323114207.222412-1-courbet@google.com> X-Mailer: git-send-email 2.25.1.696.g5e7596f4ac-goog Subject: [PATCH v3] x86: Alias memset to __builtin_memset. From: Clement Courbet Cc: Nathan Chancellor , Kees Cook , Nick Desaulniers , Joe Perches , Clement Courbet , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , x86@kernel.org, linux-kernel@vger.kernel.org, clang-built-linux@googlegroups.com Content-Type: text/plain; charset="UTF-8" To: unlisted-recipients:; (no To-header on input) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Recent compilers know the meaning of builtins (`memset`, `memcpy`, ...) and can replace calls by inline code when deemed better. For example, `memset(p, 0, 4)` will be lowered to a four-byte zero store. When using -ffreestanding (this is the case e.g. building on clang), these optimizations are disabled. This means that **all** memsets, including those with small, constant sizes, will result in an actual call to memset. We have identified several spots where we have high CPU usage because of this. For example, a single one of these memsets is responsible for about 0.3% of our total CPU usage in the kernel. Aliasing `memset` to `__builtin_memset` allows the compiler to perform this optimization even when -ffreestanding is used. There is no change when -ffreestanding is not used. Below is a diff (clang) for `update_sg_lb_stats()`, which includes the aforementionned hot memset: memset(sgs, 0, sizeof(*sgs)); Diff: movq %rsi, %rbx ~~~> movq $0x0, 0x40(%r8) movq %rdi, %r15 ~~~> movq $0x0, 0x38(%r8) movl $0x48, %edx ~~~> movq $0x0, 0x30(%r8) movq %r8, %rdi ~~~> movq $0x0, 0x28(%r8) xorl %esi, %esi ~~~> movq $0x0, 0x20(%r8) callq ~~~> movq $0x0, 0x18(%r8) ~~~> movq $0x0, 0x10(%r8) ~~~> movq $0x0, 0x8(%r8) ~~~> movq $0x0, (%r8) In terms of code size, this shrins the clang-built kernel a bit (-0.022%): 440383608 vmlinux.clang.before 440285512 vmlinux.clang.after Signed-off-by: Clement Courbet --- changes in v2: - Removed ifdef(GNUC >= 4). - Disabled change when CONFIG_FORTIFY_SOURCE is set. changes in v3: - Fixed commit message: the kernel shrinks in size. --- arch/x86/include/asm/string_64.h | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/arch/x86/include/asm/string_64.h b/arch/x86/include/asm/string_64.h index 75314c3dbe47..9cfce0a840a4 100644 --- a/arch/x86/include/asm/string_64.h +++ b/arch/x86/include/asm/string_64.h @@ -18,6 +18,15 @@ extern void *__memcpy(void *to, const void *from, size_t len); void *memset(void *s, int c, size_t n); void *__memset(void *s, int c, size_t n); +/* Recent compilers can generate much better code for known size and/or + * fill values, and will fallback on `memset` if they fail. + * We alias `memset` to `__builtin_memset` explicitly to inform the compiler to + * perform this optimization even when -ffreestanding is used. + */ +#if !defined(CONFIG_FORTIFY_SOURCE) +#define memset(s, c, count) __builtin_memset(s, c, count) +#endif + #define __HAVE_ARCH_MEMSET16 static inline void *memset16(uint16_t *s, uint16_t v, size_t n) { @@ -74,6 +83,7 @@ int strcmp(const char *cs, const char *ct); #undef memcpy #define memcpy(dst, src, len) __memcpy(dst, src, len) #define memmove(dst, src, len) __memmove(dst, src, len) +#undef memset #define memset(s, c, n) __memset(s, c, n) #ifndef __NO_FORTIFY -- 2.25.1.696.g5e7596f4ac-goog