From: Mel Gorman <mgorman@techsingularity.net>
To: Michal Such?nek <msuchanek@suse.de>
Cc: linux-kbuild@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jiri Olsa <jolsa@kernel.org>, Hritik Vijay <hritikxx8@gmail.com>,
bpf <bpf@vger.kernel.org>, Linux-Net <netdev@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: (BTF) [PATCH] mm/page_alloc: Work around a pahole limitation with zero-sized struct pagesets
Date: Wed, 26 May 2021 10:00:40 +0100 [thread overview]
Message-ID: <20210526090040.GY30378@techsingularity.net> (raw)
In-Reply-To: <20210526083342.GY8544@kitsune.suse.cz>
On Wed, May 26, 2021 at 10:33:42AM +0200, Michal Such?nek wrote:
> > lib/Kconfig.debug | 3 +++
> > mm/page_alloc.c | 11 +++++++++++
> > 2 files changed, 14 insertions(+)
> >
> > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> > index 678c13967580..f88a155b80a9 100644
> > --- a/lib/Kconfig.debug
> > +++ b/lib/Kconfig.debug
> > @@ -313,6 +313,9 @@ config DEBUG_INFO_BTF
> > config PAHOLE_HAS_SPLIT_BTF
> > def_bool $(success, test `$(PAHOLE) --version | sed -E 's/v([0-9]+)\.([0-9]+)/\1\2/'` -ge "119")
> >
> > +config PAHOLE_HAS_ZEROSIZE_PERCPU_SUPPORT
> > + def_bool $(success, test `$(PAHOLE) --version | sed -E 's/v([0-9]+)\.([0-9]+)/\1\2/'` -ge "122")
> > +
>
> This does not seem workable with dummy-tools.
>
> Do we even have dummy pahole?
>
I don't think so but if PAHOLE_HAS_ZEROSIZE_PERCPU_SUPPORT is broken for
you then the same problem should have happened for the PAHOLE_HAS_SPLIT_BTF
check.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2021-05-26 9:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 8:07 [PATCH] mm/page_alloc: Work around a pahole limitation with zero-sized struct pagesets Mel Gorman
2021-05-26 8:16 ` David Hildenbrand
2021-05-26 8:33 ` (BTF) " Michal Suchánek
2021-05-26 9:00 ` Mel Gorman [this message]
2021-05-26 17:00 ` Andrii Nakryiko
2021-05-26 17:43 ` Michal Suchánek
2021-05-26 16:57 ` Andrii Nakryiko
2021-05-26 18:13 ` Mel Gorman
2021-05-26 18:41 ` Andrii Nakryiko
2021-05-27 8:04 ` Christoph Hellwig
2021-05-27 9:04 ` Mel Gorman
2021-05-27 9:18 ` Christoph Hellwig
2021-05-27 14:37 ` Andrii Nakryiko
2021-05-27 14:41 ` Andrii Nakryiko
2021-05-28 8:09 ` David Laight
2021-05-28 9:04 ` Mel Gorman
2021-05-28 9:49 ` David Laight
2021-05-28 9:56 ` Michal Suchánek
2021-05-28 13:09 ` David Laight
2021-05-30 0:46 ` Andrii Nakryiko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210526090040.GY30378@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hritikxx8@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=masahiroy@kernel.org \
--cc=msuchanek@suse.de \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.