Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp566908rwb; Tue, 29 Nov 2022 02:25:19 -0800 (PST) X-Google-Smtp-Source: AA0mqf7/jm9lG3i9/ni3cqM8G/ri/OPsmHmcCgHUSXvJ1yiu7MXESgVsP3kN5Y13eB9vWIaBSCwY X-Received: by 2002:a63:d14f:0:b0:476:95a8:de78 with SMTP id c15-20020a63d14f000000b0047695a8de78mr35283538pgj.66.1669717519444; Tue, 29 Nov 2022 02:25:19 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669717519; cv=none; d=google.com; s=arc-20160816; b=V8pv9Cv4DCcZ07TeomZFYzvsdUsgttn/0N+OrjO0Z+t7cmyzuC8QKiuRBgXS7rjH/n 9L40/F2Zlf2Y68gGtafRf/Y7JUjko/zSe6dKBvPBh6CLinQcalnBTBdHvsWP0QLDmFyq 7XVOJ4gAbYAvOT8Nm5VFrm7xFQfumuFZBCv7l51XRHfakpESWw8ulmFvuV5AokhHGJiO mq/CibR7UQ23zPFEgi45HMSLMROx8qLD14MiLWynPPkM0OcymBiInHw8775KXaIQ+wKl a4PG18MKg8H6EnbaKBmaXN5QTz8hY7XfpdVkaFRHXG0sgsRL796hnvZmz+9O+HOBO2TC /3xQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version; bh=poSmrhdJ4U00W1z+gbHBDA9DySuHPZHfxMPRbSyJiW0=; b=sYKGHXMdasNu10RDHfAiugcX0b9Iq5wFAFk2EwoawvGuhKOowaAHpQYlA6SkPZUeP9 1ZtgR2MzKKnAtsgtd4SQNsLG8lLYKiBi6A0Ul0w3F2lnRtX1+9rmgHaV0XD0Gk4fXDf9 AvpmJ/pl6cDevbN0NzGarrPSK30MUMoSLDZJPCSPJuyJ782/uIPrlQdr1iaYjdHNOtJ5 ULeeBH4z+L93SNNvBU2ajCof9SSCA63VjKq7+X8rGK2GfsKvksDsEW0iMGgd9J6bjFrD +24IrpQVi8Ihh3s5V4paksqaPy1YgQ5Hyhu7XMCHR2DMuiAWm4Rfdn/IaxrjKkBBWice 9wRQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k17-20020a63f011000000b004403ddda6e6si14519462pgh.847.2022.11.29.02.25.07; Tue, 29 Nov 2022 02:25:19 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229954AbiK2KPO (ORCPT + 84 others); Tue, 29 Nov 2022 05:15:14 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40762 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232540AbiK2KO4 (ORCPT ); Tue, 29 Nov 2022 05:14:56 -0500 Received: from mail-pj1-f51.google.com (mail-pj1-f51.google.com [209.85.216.51]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2E72D1FFA1 for ; Tue, 29 Nov 2022 02:14:55 -0800 (PST) Received: by mail-pj1-f51.google.com with SMTP id l22-20020a17090a3f1600b00212fbbcfb78so16834373pjc.3 for ; Tue, 29 Nov 2022 02:14:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=poSmrhdJ4U00W1z+gbHBDA9DySuHPZHfxMPRbSyJiW0=; b=GlyUwPws0GVRHJkmCDGEoALIe3k+cKrflmkIjBsgkExmKjPW+R4JzfFmbT2OVBzSdY 9Ca3TSMUVR97rp36JYkYFCAliF7dFss+LGQKGQ0AxcPOZ5/eAErlXwey9mN8JJ+ujRba 6wy7dWjTgQeBEO06CO4o8PWUjqJSQ7Gvu815Jl8ZhYqtWmVdoVveydFIrWhJW88he395 PY8lyzE6o1JTFhhInzahnHCDeDHou2+dLZ4NZBEahOXexBupCjUSkhmSVLpKFaiMKAHk NN1bODZs00FYqzCCpbEKQDeDFrWhcYw8cIXnsuhgncrERmSEwHfBkhuOuU4Do2NvSfbr 8Slg== X-Gm-Message-State: ANoB5pmhfUF2UUUdvzctfWY1jPGn1Hj6zxsKgiH5mN8cdIVA2Bjkbca0 nmFoUGF7X3Aw2QdJS51r6YAhPRpXeS84RnkLY9o= X-Received: by 2002:a17:903:452:b0:189:6574:7ac2 with SMTP id iw18-20020a170903045200b0018965747ac2mr22249796plb.65.1669716894564; Tue, 29 Nov 2022 02:14:54 -0800 (PST) MIME-Version: 1.0 References: <20221128091506.gp4l6klznqhigjxv@box.shutemov.name> <20221128101117.3614401-1-mailhol.vincent@wanadoo.fr> <20221128111112.dzavip4eqqgpyrai@box.shutemov.name> <20221128124513.76392c3d@gandalf.local.home> <20221128141056.29ccafd6@gandalf.local.home> In-Reply-To: <20221128141056.29ccafd6@gandalf.local.home> From: Vincent MAILHOL Date: Tue, 29 Nov 2022 19:14:43 +0900 Message-ID: Subject: Re: [PATCH] x86/asm: Remove unused COMPILE_OFFSETS macro from asm-offsets.c To: Steven Rostedt Cc: Sean Christopherson , Paolo Bonzini , kirill.shutemov@linux.intel.com, bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com, jpoimboe@kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com, sathyanarayanan.kuppuswamy@linux.intel.com, tglx@linutronix.de, viro@zeniv.linux.org.uk, x86@kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue. 29 Nov. 2022 at 04:10, Steven Rostedt wrote: > On Mon, 28 Nov 2022 18:06:18 +0000 > Sean Christopherson wrote: > > > > > IIRC, the reason for adding that was because that logic was screwing up > > > > asm-offsets.c. I'm not sure it screws up kvm-asm-offsets.c though. > > > > > > > > This is one of those cases I wish I commented that code better :-/ > > > > > > I don't think KVM includes linux/ftrace.h or asm/ftrace.h at all. > > > > >From include/linux/kvm_host.h > > > > #include > > > > Even if that didn't exist, saying that XYZ never includes a header is a dangerous > > business, it's all too easy to indirectly include headers in the kernel, now or > > in the future. ACK. This is why I relied on the compiler's -Wunused-macros to assert that COMPILE_OFFSETS can be removed from asm-offsets.c but not from kvm-asm-offsets.c. I also asserted that it is https://git.kernel.org/torvalds/linux/c/debc5a1ec0d1 which removed the dependency. > But going back to the original intent of COMPILE_OFFSETS. I believe it was > because some code that did not work with the auto generation of compiler > offsets and was a way to hide them. > > I do not know if it is still an issue or not today. This I do not know. I only have the confidence to remove COMPILE_OFFSETS from asm-offsets.c. Nothing more.