From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Linux v5.19-rc1] tools/perf/a.out remains after make -C tools/perf clean
Date: Sun, 26 Jun 2022 12:31:05 -0300 [thread overview]
Message-ID: <Yrh7uSL0AybSqd0V@kernel.org> (raw)
In-Reply-To: <CA+icZUUx_Re+w9S7eHXma9aC=8T8ypp8=+tkJy7zJMrUocMSKQ@mail.gmail.com>
Em Wed, Jun 15, 2022 at 12:11:48AM +0200, Sedat Dilek escreveu:
> On Tue, Jun 14, 2022 at 9:24 PM Arnaldo Carvalho de Melo
> <arnaldo.melo@gmail.com> wrote:
> >
> > Em Tue, Jun 07, 2022 at 08:59:31PM +0200, Sedat Dilek escreveu:
> > > Hi,
> > >
> > > I observed this some time ago - so this is not only Linux v5.19-rc1 related.
> > >
> > > $ LC_ALL=C make -C tools/perf clean 2>&1 | tee ../make-log_perf-clean.txt
> > > make: Entering directory '/home/dileks/src/linux-kernel/git/tools/perf'
> > > CLEAN x86
> > > CLEAN libtraceevent
> > > CLEAN libapi
> > > CLEAN libbpf
> > > CLEAN libsubcmd
> > > CLEAN libperf
> > > CLEAN fixdep
> > > CLEAN feature-detect
> > > CLEAN python
> > > CLEAN bpf-skel
> > > CLEAN core-objs
> > > CLEAN core-progs
> > > CLEAN core-gen
> > > CLEAN Documentation
> > > make: Leaving directory '/home/dileks/src/linux-kernel/git/tools/perf'
> > >
> > > $ git status -s
> > > M tools/perf/util/unwind-libunwind-local.c
> > > ?? tools/perf/a.out
> > >
> > > $ rm -v tools/perf/a.out
> > > 'tools/perf/a.out' deleted
> > >
> > > $ git checkout -- tools/perf/util/unwind-libunwind-local.c
> > >
> > > $ git status -s
> > > [ empty ]
> >
> > Interesting, since Linus complained at some point that after building
> > perf some new temp file was left there I added 'git status' to my
> > scripts to always get this flagged.
> >
> > I'm not seeing this here.
> >
>
> Just re-checked with Linux v5.19-rc2 and attaching tools/perf/a.out +
> tools/perf/Makefile.config.
>
> Check perf binary:
>
> $ ~/bin/perf -vv
> perf version 5.19.0-rc2
> dwarf: [ on ] # HAVE_DWARF_SUPPORT
> dwarf_getlocations: [ on ] # HAVE_DWARF_GETLOCATIONS_SUPPORT
> glibc: [ on ] # HAVE_GLIBC_SUPPORT
> syscall_table: [ on ] # HAVE_SYSCALL_TABLE_SUPPORT
> libbfd: [ on ] # HAVE_LIBBFD_SUPPORT
> debuginfod: [ OFF ] # HAVE_DEBUGINFOD_SUPPORT
> libelf: [ on ] # HAVE_LIBELF_SUPPORT
> libnuma: [ on ] # HAVE_LIBNUMA_SUPPORT
> numa_num_possible_cpus: [ on ] # HAVE_LIBNUMA_SUPPORT
> libperl: [ on ] # HAVE_LIBPERL_SUPPORT
> libpython: [ on ] # HAVE_LIBPYTHON_SUPPORT
> libslang: [ on ] # HAVE_SLANG_SUPPORT
> libcrypto: [ on ] # HAVE_LIBCRYPTO_SUPPORT
> libunwind: [ on ] # HAVE_LIBUNWIND_SUPPORT
> libdw-dwarf-unwind: [ on ] # HAVE_DWARF_SUPPORT
> zlib: [ on ] # HAVE_ZLIB_SUPPORT
> lzma: [ on ] # HAVE_LZMA_SUPPORT
> get_cpuid: [ on ] # HAVE_AUXTRACE_SUPPORT
> bpf: [ on ] # HAVE_LIBBPF_SUPPORT
> aio: [ on ] # HAVE_AIO_SUPPORT
> zstd: [ on ] # HAVE_ZSTD_SUPPORT
> libpfm4: [ OFF ] # HAVE_LIBPFM
>
> Tried `make distclean`.
> Tried `make tools/ clean` but tools/tracing/rtla produces errors (rm clean).
> Still exists: tools/perf/a.out.
I started seeing this here, will investigate and re-read your reports,
thanks for sending them!
- Arnaldo
next prev parent reply other threads:[~2022-06-26 15:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 0:08 [PATCH] perf unwind: Fix uninitialized variable Ian Rogers
2022-06-07 0:26 ` Fangrui Song
2022-06-09 16:34 ` Arnaldo Carvalho de Melo
2022-06-07 18:12 ` Sedat Dilek
2022-06-08 19:29 ` Sedat Dilek
2022-06-07 18:59 ` [Linux v5.19-rc1] tools/perf/a.out remains after make -C tools/perf clean Sedat Dilek
2022-06-14 19:24 ` Arnaldo Carvalho de Melo
2022-06-14 22:11 ` Sedat Dilek
2022-06-26 15:31 ` Arnaldo Carvalho de Melo [this message]
2022-06-27 6:20 ` Sedat Dilek
2022-06-28 14:39 ` Arnaldo Carvalho de Melo
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=Yrh7uSL0AybSqd0V@kernel.org \
--to=acme@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sedat.dilek@gmail.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).