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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no 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 9BC75C4743D for ; Tue, 8 Jun 2021 18:53:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7E28B6147F for ; Tue, 8 Jun 2021 18:53:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236095AbhFHSyI (ORCPT ); Tue, 8 Jun 2021 14:54:08 -0400 Received: from smtp-out1.suse.de ([195.135.220.28]:42228 "EHLO smtp-out1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235377AbhFHSsC (ORCPT ); Tue, 8 Jun 2021 14:48:02 -0400 Received: from imap.suse.de (imap-alt.suse-dmz.suse.de [192.168.254.47]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 32944219D8; Tue, 8 Jun 2021 18:46:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1623177968; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=sY1lNhT8zE/AvIyHCiemembHK2uoefGtSYoQxLprpo0=; b=WJpCMzacaMbZSPcKkJSmKUQOuYFB+R+axjR2eu77aFtqDXuSl8mh8X7NV8ge4zny3v+84b X7BumQxfoeAOW4G5rptqvX5dWb0V2hEn7+P9DzJ+MOKvGqCc3D8u6SQuM/1hM4TiVG4Hny ENHusJJquABxOwqMlfLmQFonkEo5+Oo= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1623177968; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=sY1lNhT8zE/AvIyHCiemembHK2uoefGtSYoQxLprpo0=; b=qVoIvDLtc64ta6H3xXZa20TwkiE/+ffu+bvvIygUKdhUnAMNUa/QIDrGJD5FZFlY9XpIS7 jlYkyemgMEHsO+Dg== Received: from imap3-int (imap-alt.suse-dmz.suse.de [192.168.254.47]) by imap.suse.de (Postfix) with ESMTP id 1E78C118DD; Tue, 8 Jun 2021 18:46:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1623177968; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=sY1lNhT8zE/AvIyHCiemembHK2uoefGtSYoQxLprpo0=; b=WJpCMzacaMbZSPcKkJSmKUQOuYFB+R+axjR2eu77aFtqDXuSl8mh8X7NV8ge4zny3v+84b X7BumQxfoeAOW4G5rptqvX5dWb0V2hEn7+P9DzJ+MOKvGqCc3D8u6SQuM/1hM4TiVG4Hny ENHusJJquABxOwqMlfLmQFonkEo5+Oo= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1623177968; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=sY1lNhT8zE/AvIyHCiemembHK2uoefGtSYoQxLprpo0=; b=qVoIvDLtc64ta6H3xXZa20TwkiE/+ffu+bvvIygUKdhUnAMNUa/QIDrGJD5FZFlY9XpIS7 jlYkyemgMEHsO+Dg== Received: from director2.suse.de ([192.168.254.72]) by imap3-int with ESMTPSA id 2ViiB/C6v2BJGAAALh3uQQ (envelope-from ); Tue, 08 Jun 2021 18:46:08 +0000 Date: Tue, 8 Jun 2021 20:46:02 +0200 From: Borislav Petkov To: Arnaldo Carvalho de Melo Cc: Borislav Petkov , kernel test robot , Andrew Cooper , kbuild-all@lists.01.org, linux-kernel@vger.kernel.org, x86@kernel.org, Peter Zijlstra Subject: Re: [tip:x86/cpu 4/4] Warning: Kernel ABI header at 'tools/arch/x86/include/asm/cpufeatures.h' differs from latest version at 'arch/x86/include/asm/cpufeatures.h': 111< /* free ( 3*32+29) */ Message-ID: References: <20210602094153.GH1271937@shao2-debian> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 08, 2021 at 03:06:57PM -0300, Arnaldo Carvalho de Melo wrote: > > Or, if we start doing that then they don't have to do anything. > > Who? Previously its me doing this work, i.e. keeping things in synch. > Actually it is expected that people doing the kernel work don't touch > tools/ wrt adding the copy, Ok, I think I'm totally confused. First you say that you're trying to keep the headers in sync and now you say that patches adding stuff to the kernel cpufeatures.h header should not touch the copy in tools/... In any case, I was thinking that we could document what people touching cpufeatures.h need to do and put it Documentation/x86/cpuinfo.rst. And then spread the load by asking everyone to do that test and fix the perf build accordingly. So that you don't have to do it all by yourself. -- Regards/Gruss, Boris. SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============8429621274427844321==" MIME-Version: 1.0 From: Borislav Petkov To: kbuild-all@lists.01.org Subject: Re: [tip:x86/cpu 4/4] Warning: Kernel ABI header at 'tools/arch/x86/include/asm/cpufeatures.h' differs from latest version at 'arch/x86/include/asm/cpufeatures.h': 111< /* free ( 3*32+29) */ Date: Tue, 08 Jun 2021 20:46:02 +0200 Message-ID: In-Reply-To: List-Id: --===============8429621274427844321== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Tue, Jun 08, 2021 at 03:06:57PM -0300, Arnaldo Carvalho de Melo wrote: > > Or, if we start doing that then they don't have to do anything. > = > Who? Previously its me doing this work, i.e. keeping things in synch. > Actually it is expected that people doing the kernel work don't touch > tools/ wrt adding the copy, Ok, I think I'm totally confused. First you say that you're trying to keep the headers in sync and now you say that patches adding stuff to the kernel cpufeatures.h header should not touch the copy in tools/... In any case, I was thinking that we could document what people touching cpufeatures.h need to do and put it Documentation/x86/cpuinfo.rst. And then spread the load by asking everyone to do that test and fix the perf build accordingly. So that you don't have to do it all by yourself. -- = Regards/Gruss, Boris. SUSE Software Solutions Germany GmbH, GF: Felix Imend=C3=B6rffer, HRB 36809= , AG N=C3=BCrnberg --===============8429621274427844321==--