From: kernel test robot <lkp@intel.com>
To: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Weilin Wang <weilin.wang@intel.com>,
James Clark <james.clark@linaro.org>, Xu Yang <xu.yang_2@nxp.com>,
John Garry <john.g.garry@oracle.com>,
Howard Chu <howardchu95@gmail.com>,
Levi Yun <yeoreum.yun@arm.com>,
Dominique Martinet <asmadeus@codewreck.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v2 13/16] perf intel-tpebs: Use stats for retirement latency statistics
Date: Tue, 8 Apr 2025 04:39:49 +0800 [thread overview]
Message-ID: <202504080043.E3FPjBvv-lkp@intel.com> (raw)
In-Reply-To: <20250407050101.1389825-14-irogers@google.com>
Hi Ian,
kernel test robot noticed the following build warnings:
[auto build test WARNING on perf-tools-next/perf-tools-next]
[also build test WARNING on perf-tools/perf-tools linus/master v6.15-rc1 next-20250407]
[cannot apply to tip/perf/core acme/perf/core]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ian-Rogers/perf-intel-tpebs-Cleanup-header/20250407-130741
base: https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git perf-tools-next
patch link: https://lore.kernel.org/r/20250407050101.1389825-14-irogers%40google.com
patch subject: [PATCH v2 13/16] perf intel-tpebs: Use stats for retirement latency statistics
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202504080043.E3FPjBvv-lkp@intel.com/
includecheck warnings: (new ones prefixed by >>)
>> tools/perf/util/intel-tpebs.c: stat.h is included more than once.
vim +21 tools/perf/util/intel-tpebs.c
> 21 #include "stat.h"
22 #include "tool.h"
23 #include "cpumap.h"
24 #include "metricgroup.h"
> 25 #include "stat.h"
> 26 #include <sys/stat.h>
27 #include <sys/file.h>
28 #include <poll.h>
29 #include <math.h>
30
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-04-07 20:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 5:00 [PATCH v2 00/16] Intel TPEBS min/max/mean/last support Ian Rogers
2025-04-07 5:00 ` [PATCH v2 01/16] perf intel-tpebs: Cleanup header Ian Rogers
2025-04-07 5:00 ` [PATCH v2 02/16] perf intel-tpebs: Simplify tpebs_cmd Ian Rogers
2025-04-07 5:00 ` [PATCH v2 03/16] perf intel-tpebs: Rename tpebs_start to evsel__tpebs_open Ian Rogers
2025-04-07 5:00 ` [PATCH v2 04/16] perf intel-tpebs: Separate evsel__tpebs_prepare out of evsel__tpebs_open Ian Rogers
2025-04-07 5:00 ` [PATCH v2 05/16] perf intel-tpebs: Move cpumap_buf " Ian Rogers
2025-04-07 5:00 ` [PATCH v2 06/16] perf intel-tpebs: Reduce scope of tpebs_events_size Ian Rogers
2025-04-07 5:00 ` [PATCH v2 07/16] perf intel-tpebs: Inline get_perf_record_args Ian Rogers
2025-04-07 5:00 ` [PATCH v2 08/16] perf intel-tpebs: Ensure events are opened, factor out finding Ian Rogers
2025-04-07 5:00 ` [PATCH v2 09/16] perf intel-tpebs: Refactor tpebs_results list Ian Rogers
2025-04-07 19:33 ` Liang, Kan
2025-04-07 20:03 ` Ian Rogers
2025-04-07 5:00 ` [PATCH v2 10/16] perf intel-tpebs: Add support for updating counts in evsel__tpebs_read Ian Rogers
2025-04-07 19:37 ` Liang, Kan
2025-04-07 20:07 ` Ian Rogers
2025-04-07 5:00 ` [PATCH v2 11/16] perf intel-tpebs: Add mutex for tpebs_results Ian Rogers
2025-04-07 19:49 ` Liang, Kan
2025-04-07 20:10 ` Ian Rogers
2025-04-07 5:00 ` [PATCH v2 12/16] perf intel-tpebs: Don't close record on read Ian Rogers
2025-04-07 5:00 ` [PATCH v2 13/16] perf intel-tpebs: Use stats for retirement latency statistics Ian Rogers
2025-04-07 20:39 ` kernel test robot [this message]
2025-04-07 5:00 ` [PATCH v2 14/16] perf stat: Add mean, min, max and last --tpebs-mode options Ian Rogers
2025-04-07 19:56 ` Liang, Kan
2025-04-07 20:10 ` Ian Rogers
2025-04-07 5:01 ` [PATCH v2 15/16] perf pmu-events: Add retirement latency to JSON events inside of perf Ian Rogers
2025-04-07 5:01 ` [PATCH v2 16/16] perf record: Retirement latency cleanup in evsel__config Ian Rogers
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=202504080043.E3FPjBvv-lkp@intel.com \
--to=lkp@intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=asmadeus@codewreck.org \
--cc=howardchu95@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=weilin.wang@intel.com \
--cc=xu.yang_2@nxp.com \
--cc=yeoreum.yun@arm.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