The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Yang Jihong <yangjihong1@huawei.com>
To: "Daniel Díaz" <daniel.diaz@linaro.org>,
	"Namhyung Kim" <namhyung@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	<linux-perf-users@vger.kernel.org>
Subject: Re: [GIT PULL] perf tools changes for v6.7
Date: Sat, 18 Nov 2023 10:59:26 +0800	[thread overview]
Message-ID: <63a2652b-e62a-348e-e92b-47d3c86461ae@huawei.com> (raw)
In-Reply-To: <CAEUSe78g5XUpQ19t4LbeGK4v_PZNTDZ=wjRM325Bm8haiUCoXA@mail.gmail.com>

Hello,

On 2023/11/14 3:28, Daniel Díaz wrote:
> Hello!
> 
> On Thu, 2 Nov 2023 at 09:06, Namhyung Kim <namhyung@kernel.org> wrote:
>> Hi Linus,
>>
>> Please consider pulling the latest perf tools changes.
>>
>> Thanks,
>> Namhyung
> [...]
>> Yang Jihong (29):
>>        perf evlist: Add perf_evlist__go_system_wide() helper
>>        perf evlist: Add evlist__findnew_tracking_event() helper
>>        perf record: Move setting tracking events before record__init_thread_masks()
>>        perf record: Track sideband events for all CPUs when tracing selected CPUs
>>        perf test: Add test case for record sideband events
>>        perf test: Add perf_event_attr test for record dummy event
>>        perf kwork: Fix incorrect and missing free atom in work_push_atom()
>>        perf kwork: Add the supported subcommands to the document
>>        perf kwork: Set ordered_events to true in 'struct perf_tool'
>>        perf kwork: Add `kwork` and `src_type` to work_init() for 'struct kwork_class'
>>        perf kwork: Overwrite original atom in the list when a new atom is pushed.
>>        perf kwork: Set default events list if not specified in setup_event_list()
>>        perf kwork: Add sched record support
>>        perf kwork: Add `root` parameter to work_sort()
>>        perf kwork top: Introduce new top utility
> [...]
> 
> We have found some build regressions on yesterday's 6.7-rc1:
> -----8<-----
>    builtin-kwork.c: In function 'top_print_work':
>    builtin-kwork.c:1646:28: error: format '%ld' expects argument of
> type 'long int', but argument 3 has type 'u64' {aka 'long long
> unsigned int'} [-Werror=format=]
>     1646 |         ret += printf(" %*ld ", PRINT_PID_WIDTH, work->id);
>          |                         ~~~^                     ~~~~~~~~
>          |                            |                         |
>          |                            long int                  u64
> {aka long long unsigned int}
>          |                         %*lld
>    cc1: all warnings being treated as errors
>    make[3]: *** [/builds/linux/tools/build/Makefile.build:106:
> /home/tuxbuild/.cache/tuxmake/builds/1/build/builtin-kwork.o] Error 1
> ----->8-----
> 
> This is when building for Arm (32-bits) and i386. Bisection points to
> commit 55c40e505234 ("perf kwork top: Introduce new top utility").
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> To reproduce locally,
>    tuxmake \
>      --runtime podman \
>      --target-arch arm \
>      --toolchain gcc-13 \
>      --kconfig https://storage.tuxsuite.com/public/linaro/lkft/builds/2Y6I5Blgre1fELnAgUTZxqjByvv/config
> \
>      debugkernel dtbs dtbs-legacy headers kernel modules perf
> 
> Greetings!
> 
Thanks for informing of build error, has send fix patch for it:
https://lore.kernel.org/all/20231118024858.1567039-2-yangjihong1@huawei.com/


Thanks,
Yang
.

      reply	other threads:[~2023-11-18  2:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 15:06 [GIT PULL] perf tools changes for v6.7 Namhyung Kim
2023-11-03 19:53 ` pr-tracker-bot
2023-11-13 19:28 ` Daniel Díaz
2023-11-18  2:59   ` Yang Jihong [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=63a2652b-e62a-348e-e92b-47d3c86461ae@huawei.com \
    --to=yangjihong1@huawei.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=daniel.diaz@linaro.org \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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