From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Sergey Matyukevich <geomatsi@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/linux-tools: perf: add host-python3 dependency
Date: Mon, 5 Sep 2022 22:17:27 +0200 [thread overview]
Message-ID: <20220905201727.GJ1490660@scaer> (raw)
In-Reply-To: <20220904205702.1488199-1-geomatsi@gmail.com>
Sergey, All,
On 2022-09-04 23:57 +0300, Sergey Matyukevich spake thusly:
> Linux kernel commit 00facc760903 ("perf jevents: Switch build to use
> jevents.py")
00facc760903 is only parts of 6.0-rc kernels so far, so unless one uses
bleeding edge technology, there is no issue. So, paying the price of a
host-pytohn3 build just for release-candidate kernels is a bit too much
in my opinion.
So, I added a config knob to drive this, like we have for host-openssl
and a few other host programs for building the kernel.
Applied to master with the above change, thanks.
Regards,
Yann E. MORIN.
> switched to auto-generation of arch-specific PMU events
> using python script. Now custom PMU events for different platforms of
> the selected target architecture are not embedded into perf binary if
> an appropriate host python interpreter is not present. In practice it
> means that perf is successfully built, but 'perf list pmu' will show
> no custom events on a target platform even if those events are supported
> and properly defined in tools/perf/pmu-events/arch/<target arch>
> directory in the kernel source tree.
>
> Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com>
> ---
> package/linux-tools/linux-tool-perf.mk.in | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/linux-tools/linux-tool-perf.mk.in b/package/linux-tools/linux-tool-perf.mk.in
> index 057c6f80e7..44c1bbdf83 100644
> --- a/package/linux-tools/linux-tool-perf.mk.in
> +++ b/package/linux-tools/linux-tool-perf.mk.in
> @@ -6,7 +6,7 @@
>
> LINUX_TOOLS += perf
>
> -PERF_DEPENDENCIES = host-flex host-bison
> +PERF_DEPENDENCIES = host-flex host-bison host-python3
>
> ifeq ($(NORMALIZED_ARCH),x86_64)
> PERF_ARCH=x86
> --
> 2.37.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-09-05 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 20:57 [Buildroot] [PATCH 1/1] package/linux-tools: perf: add host-python3 dependency Sergey Matyukevich
2022-09-05 20:17 ` Yann E. MORIN [this message]
2022-09-06 19:46 ` Arnout Vandecappelle
2022-09-06 20:07 ` Yann E. MORIN
2022-09-06 20:12 ` Sergey Matyukevich
2022-09-06 20:37 ` Yann E. MORIN
2022-09-07 12:18 ` Arnout Vandecappelle
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=20220905201727.GJ1490660@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=geomatsi@gmail.com \
--cc=thomas.petazzoni@bootlin.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.