public inbox for linux-perf-users@vger.kernel.org
 help / color / mirror / Atom feed
From: cp0613@linux.alibaba.com
To: irogers@google.com
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	namhyung@kernel.org, guoren@kernel.org,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf build: Avoid argument list too long in orphan pruning
Date: Tue, 17 Mar 2026 09:44:34 +0800	[thread overview]
Message-ID: <20260317014434.1440-1-cp0613@linux.alibaba.com> (raw)
In-Reply-To: <CAP-5=fUAf5bhbHiy_45xP4LhUM-qOa6YykQaMF4yp4Ta7qmbog@mail.gmail.com>

On Fri, 13 Mar 2026 08:47:31 -0700, irogers@google.com:
> 
> > The original problem was encountered when compiling the Linux tool perf in
> > buildroot. I think it might also occur in buildroot or yocto environments.
> >
> > I also constructed a method to reproduce the issue in an x86 native
> > environment by extracting a long file list. The problem can be reproduced
> > using:
> >   make -C tools/perf O=./patches-perf NO_LIBTRACEEVENT=1 NO_LIBPYTHON=1
> 
> Hi cp0613,
> 
> I'm not sure what the patch diff is, but I think you're encountering
> the issue discussed here:
> https://lore.kernel.org/lkml/20260303211503.165337-1-mmayer@broadcom.com/
> The fix has been merged, so I'm not sure why it remains a problem.
> 
> Thanks,
> Ian

Oh, I just wanted to provide a way to reproduce the issue with this patch.
It looks like the same problem, but maybe I haven't updated my local code
as soon as possible. Thanks for reminding me.

Thanks,
Pei

      reply	other threads:[~2026-03-17  1:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13  7:24 [PATCH] perf build: Avoid argument list too long in orphan pruning cp0613
2026-03-13  8:36 ` cp0613
2026-03-13 15:47   ` Ian Rogers
2026-03-17  1:44     ` cp0613 [this message]

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=20260317014434.1440-1-cp0613@linux.alibaba.com \
    --to=cp0613@linux.alibaba.com \
    --cc=acme@kernel.org \
    --cc=guoren@kernel.org \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    /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