Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp1091559pxv; Fri, 16 Jul 2021 01:09:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJydv5uNjb0QXWZRC3wydX6fjjB8kh84R7imrT2N9/Bh7d5j+Csna8tcLPyFWZYD6YxI9Bp5 X-Received: by 2002:aa7:dbc3:: with SMTP id v3mr13149399edt.63.1626422961775; Fri, 16 Jul 2021 01:09:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626422961; cv=none; d=google.com; s=arc-20160816; b=Ic6NkpR6Ty6f2cw/fNMTkWo1ZGzL8sUOn2oO8p7d1I5loqLPM9f8lvcgInuyb1Gjq7 onaiLu568CitdWrwH9hu0ItycQBt4AiC7iskYurlGnvKD38uD+zOs8ygB3PkG1zm5CHr bNfPV9ERa1qgbbxrNPxUCv3i5ExDXogbx6qchctZ9YacYbzt4h7dSx5It7kigOVmyIvy 5LdP9SwsOsQPlSD9i0gBOLDDyid0LnqzO6TORU/3ziYitYtZ71WyzEvy2Qqung7zOGf8 n3lpYVeIPOn22oPRzitC6wN7mXXDoF14AYuVzTFRJglKOE0INZZbxp92uoXFqLwUhvTx NuRg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=nPTerp1i0W46OV+t8g83f/eY2V3qA6tBiCBY7dghfdI=; b=Ubqpq15gtzO7kLamqkcJPua2xriu1bi/8LqWrEG1VIeLACO2Iz6YNmdxyp8kG4djh2 2hpknFyQU683f2DsIoTjfzx/rO6VB324f6u0SOv0URkT+t4j8l1451pbMGKdG+O3yh1F VOHuuHxd7tkdRVdjMigQfvHcH5WyMd2YnKUHOAkjuvRsEA2Zdl2HkQOu3G2Ed1Dwf4Ss vzcnmN1CPIQvmAFcTm11nT1ZU1WAZhOU1yvxnUUPIQsP7EUsMk9clrlPexPcf9KEAWUC Godfw2Y9Bx+qOxDqJyb1PcOuAjkZuON24v3kRBS/lcvkmrGjmD2sAPYFpaWY0NmhU3/e jFqw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id gh10si8781523ejc.319.2021.07.16.01.08.59; Fri, 16 Jul 2021 01:09:21 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236777AbhGPIK2 (ORCPT + 99 others); Fri, 16 Jul 2021 04:10:28 -0400 Received: from outbound-smtp44.blacknight.com ([46.22.136.52]:53877 "EHLO outbound-smtp44.blacknight.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236794AbhGPIK2 (ORCPT ); Fri, 16 Jul 2021 04:10:28 -0400 Received: from mail.blacknight.com (pemlinmail05.blacknight.ie [81.17.254.26]) by outbound-smtp44.blacknight.com (Postfix) with ESMTPS id CEA89F8545 for ; Fri, 16 Jul 2021 09:07:32 +0100 (IST) Received: (qmail 22557 invoked from network); 16 Jul 2021 08:07:32 -0000 Received: from unknown (HELO techsingularity.net) (mgorman@techsingularity.net@[84.203.17.255]) by 81.17.254.9 with ESMTPSA (AES256-SHA encrypted, authenticated); 16 Jul 2021 08:07:32 -0000 Date: Fri, 16 Jul 2021 09:07:30 +0100 From: Mel Gorman To: Michal Such?nek Cc: Andrii Nakryiko , Andrew Morton , Christoph Hellwig , Arnaldo Carvalho de Melo , Alexei Starovoitov , Daniel Borkmann , Martin KaFai Lau , Song Liu , Yonghong Song , John Fastabend , KP Singh , LKML , Jiri Olsa , Hritik Vijay , Linux-BPF , Linux-Net , Linux-MM , clm@fb.com Subject: Re: [PATCH v3] mm/page_alloc: Require pahole v1.22 to cope with zero-sized struct pagesets Message-ID: <20210716080730.GU3809@techsingularity.net> References: <20210527171923.GG30378@techsingularity.net> <20210528074248.GI30378@techsingularity.net> <20210531093554.GT30378@techsingularity.net> <20210715194453.GI24916@kitsune.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <20210715194453.GI24916@kitsune.suse.cz> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 15, 2021 at 09:44:53PM +0200, Michal Such?nek wrote: > > > Well, luckily it seems we anticipated issues like that and added > > > --skip_encoding_btf_vars argument, which I completely forgot about and > > > just accidentally came across reviewing Arnaldo's latest pahole patch. > > > I think that one is a much better solution, as then it will impact > > > only those that explicitly relies on availability of BTF for per-CPU > > > variables, which is a subset of all possible uses for kernel BTF. Sent > > > a patch ([0]), please take a look. > > > > > > [0] https://lore.kernel.org/linux-mm/20210530002536.3193829-1-andrii@kernel.org/T/#u > > > > I'm happy to have this patch used as an alternative to forcing 1.22 to > > be the minimum version of pahole required. > > Is pahole 1.22 available already? > Ultimately it was of less importance because of a0b8200d06ad ("kbuild: skip per-CPU BTF generation for pahole v1.18-v1.21"). As I write this, pahole v1.22 has not been tagged. -- Mel Gorman SUSE Labs