dwarves.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Martin Reboredo <yakoyoku@gmail.com>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
	Luna Jernberg <droidbittin@gmail.com>,
	dwarves@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Alibek Omarov <a1ba.omarov@gmail.com>,
	Kornilios Kourtis <kornilios@isovalent.com>,
	Kui-Feng Lee <kuifeng@fb.com>, Yonghong Song <yhs@fb.com>,
	bpf@vger.kernel.org
Subject: Re: ANNOUNCE: pahole v1.24 (Faster BTF encoding, 64-bit BTF enum entries)
Date: Sun, 28 Aug 2022 09:38:09 +0200	[thread overview]
Message-ID: <YwsbYX3g5dvaRABt@krava> (raw)
In-Reply-To: <538ebda0-0f8a-ebae-f02f-c8f8736ca12b@gmail.com>

On Wed, Aug 24, 2022 at 07:50:39PM -0300, Martin Reboredo wrote:
> On 8/24/22 11:38, Luna Jernberg wrote:
> > https://forum.endeavouros.com/t/failed-to-start-load-kernel-modules-on-boot-after-system-update-nvidia/30584/17?u=sradjoker
> > 
> > On 8/24/22, Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com> wrote:
> >> Em Wed, Aug 24, 2022 at 04:36:18PM +0200, Luna Jernberg escreveu:

SNIP

> 
> Can you try a build of the kernel or the by passing the
> --skip_encoding_btf_enum64 to scripts/pahole-flags.sh?

Martin,
could you please send formal patch this?

thanks,
jirka

> 
> Here's a patch for either in tree scripts/pahole-flags.sh or
> /usr/lib/modules/5.19.3-arch1-1/build/scripts/pahole-flags.sh
> 
> diff --git a/scripts/pahole-flags.sh b/scripts/pahole-flags.sh
> index 0d99ef17e4a528..1f1f1d397c399a 100755
> --- a/scripts/pahole-flags.sh
> +++ b/scripts/pahole-flags.sh
> @@ -19,5 +19,9 @@ fi
>  if [ "${pahole_ver}" -ge "122" ]; then
>  	extra_paholeopt="${extra_paholeopt} -j"
>  fi
> +if [ "${pahole_ver}" -ge "124" ]; then
> +	# see PAHOLE_HAS_LANG_EXCLUDE
> +	extra_paholeopt="${extra_paholeopt} --skip_encoding_btf_enum64"
> +fi
> 
>  echo ${extra_paholeopt}
> 
> - Martin Rodriguez Reboredo

  reply	other threads:[~2022-08-28  7:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 23:28 ANNOUNCE: pahole v1.24 (Faster BTF encoding, 64-bit BTF enum entries) Arnaldo Carvalho de Melo
     [not found] ` <CADo9pHhW9w+ciNbQr+7u4mezuQ1USyh0k2Wshy=wkdEcxRiDLA@mail.gmail.com>
2022-08-24 14:32   ` Arnaldo Carvalho de Melo
2022-08-24 14:36     ` Luna Jernberg
2022-08-24 14:37       ` Arnaldo Carvalho de Melo
2022-08-24 14:38         ` Luna Jernberg
2022-08-24 22:50           ` Martin Reboredo
2022-08-28  7:38             ` Jiri Olsa [this message]
2022-08-28 14:29               ` Martin Rodriguez Reboredo
2022-08-28 17:01                 ` Jiri Olsa
2022-08-24 16:24 ` Nathan Chancellor
2022-08-24 17:15   ` Arnaldo Carvalho de Melo
2022-08-24 17:55     ` Arnaldo Carvalho de Melo
2022-08-25 13:19       ` [PATCH] core: Conditionally define language encodings entries) Arnaldo Carvalho de Melo
2022-08-25 14:58         ` Martin Rodriguez Reboredo
2022-08-25 16:12         ` Nathan Chancellor
2022-08-24 17:59     ` ANNOUNCE: pahole v1.24 (Faster BTF encoding, 64-bit BTF enum entries) Luna Jernberg

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=YwsbYX3g5dvaRABt@krava \
    --to=olsajiri@gmail.com \
    --cc=a1ba.omarov@gmail.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=droidbittin@gmail.com \
    --cc=dwarves@vger.kernel.org \
    --cc=kornilios@isovalent.com \
    --cc=kuifeng@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yakoyoku@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).