mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gabriele Monaco <gmonaco@redhat.com>
To: kernel test robot <lkp@intel.com>,
	linux-kernel@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	linux-trace-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Ingo Molnar <mingo@redhat.com>,
	Juri Lelli	 <juri.lelli@redhat.com>
Subject: Re: [PATCH v2 04/11] rv: Add option for nested monitors and include sched
Date: Mon, 17 Feb 2025 07:56:23 +0100	[thread overview]
Message-ID: <c5fe1f637a84087afb94ed3f9255810ef3975724.camel@redhat.com> (raw)
In-Reply-To: <202502170630.xSYE4cUk-lkp@intel.com>

On Mon, 2025-02-17 at 06:39 +0800, kernel test robot wrote:
> Hi Gabriele,
> 
> kernel test robot noticed the following build warnings:
> 
> [auto build test WARNING on 4dc1d1bec89864d8076e5ab314f86f46442bfb02]
> 
> url:   
> https://github.com/intel-lab-lkp/linux/commits/Gabriele-Monaco/tracing-Fix-DECLARE_TRACE_CONDITION/20250213-171642
> base:   4dc1d1bec89864d8076e5ab314f86f46442bfb02
> patch link:   
> https://lore.kernel.org/r/20250213090819.419470-5-gmonaco%40redhat.com
> patch subject: [PATCH v2 04/11] rv: Add option for nested monitors
> and include sched
> config: parisc-randconfig-r112-20250217
> (https://download.01.org/0day-ci/archive/20250217/202502170630.xSYE4c
> Uk-lkp@intel.com/config)
> compiler: hppa-linux-gcc (GCC) 14.2.0
> reproduce:
> (https://download.01.org/0day-ci/archive/20250217/202502170630.xSYE4c
> Uk-lkp@intel.com/reproduce)
> 
> 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/202502170630.xSYE4cUk-lkp@intel.com/
> 
> All warnings (new ones prefixed by >>):
> 
>    In file included from include/trace/define_trace.h:119,
>                     from kernel/trace/rv/rv_trace.h:130,
>                     from kernel/trace/rv/rv.c:148:
> > > include/trace/trace_events.h:477:13: warning:
> > > 'print_fmt_error_da_monitor' defined but not used [-Wunused-
> > > variable]
>      477 | static char print_fmt_##call[] =
> print;                                 \
>          |             ^~~~~~~~~~
>    kernel/trace/rv/./rv_trace.h:39:1: note: in expansion of macro
> 'DECLARE_EVENT_CLASS'
>       39 | DECLARE_EVENT_CLASS(error_da_monitor,
>          | ^~~~~~~~~~~~~~~~~~~
> > > include/trace/trace_events.h:477:13: warning:
> > > 'print_fmt_event_da_monitor' defined but not used [-Wunused-
> > > variable]
>      477 | static char print_fmt_##call[] =
> print;                                 \
>          |             ^~~~~~~~~~
>    kernel/trace/rv/./rv_trace.h:12:1: note: in expansion of macro
> 'DECLARE_EVENT_CLASS'
>       12 | DECLARE_EVENT_CLASS(event_da_monitor,
>          | ^~~~~~~~~~~~~~~~~~~
> > > include/trace/trace_events.h:223:37: warning:
> > > 'trace_event_type_funcs_error_da_monitor' defined but not used [-
> > > Wunused-variable]
>      223 | static struct trace_event_functions
> trace_event_type_funcs_##call = {   \
>          |                                    
> ^~~~~~~~~~~~~~~~~~~~~~~
>    kernel/trace/rv/./rv_trace.h:39:1: note: in expansion of macro
> 'DECLARE_EVENT_CLASS'
>       39 | DECLARE_EVENT_CLASS(error_da_monitor,
>          | ^~~~~~~~~~~~~~~~~~~
> > > include/trace/trace_events.h:223:37: warning:
> > > 'trace_event_type_funcs_event_da_monitor' defined but not used [-
> > > Wunused-variable]
>      223 | static struct trace_event_functions
> trace_event_type_funcs_##call = {   \
>          |                                    
> ^~~~~~~~~~~~~~~~~~~~~~~
>    kernel/trace/rv/./rv_trace.h:12:1: note: in expansion of macro
> 'DECLARE_EVENT_CLASS'
>       12 | DECLARE_EVENT_CLASS(event_da_monitor,
>          | ^~~~~~~~~~~~~~~~~~~
> 

This is something hard to trigger, but I didn't remove the select
DA_MON_EVENTS_IMPLICIT in RV_MON_SCHED . As a result if the user
enables the sched monitor without any nested monitor (which is already
a broken configuration but happens if you apply this commit without the
following ones) trace event classes would be created with no event
using them.

I will send a V2 with the fix.


  reply	other threads:[~2025-02-17  6:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13  9:07 [PATCH v2 00/11] rv: Add scheduler specification monitors Gabriele Monaco
2025-02-13  9:07 ` [PATCH v2 01/11] tracing: Fix DECLARE_TRACE_CONDITION Gabriele Monaco
2025-02-13  9:08 ` [PATCH v2 02/11] rv: Add license identifiers to monitor files Gabriele Monaco
2025-02-13  9:08 ` [PATCH v2 03/11] sched: Add sched tracepoints for RV task model Gabriele Monaco
2025-02-14  8:00   ` kernel test robot
2025-02-14 11:15     ` Gabriele Monaco
2025-02-17 16:39       ` Steven Rostedt
2025-02-14  9:52   ` kernel test robot
2025-02-17 16:38   ` Steven Rostedt
2025-02-17 16:49     ` Peter Zijlstra
2025-02-17 17:16       ` Steven Rostedt
2025-02-18  7:06         ` Gabriele Monaco
2025-02-13  9:08 ` [PATCH v2 04/11] rv: Add option for nested monitors and include sched Gabriele Monaco
2025-02-16 22:39   ` kernel test robot
2025-02-17  6:56     ` Gabriele Monaco [this message]
2025-02-13  9:08 ` [PATCH v2 05/11] rv: Add sco and tss per-cpu monitors Gabriele Monaco
2025-02-13  9:08 ` [PATCH v2 06/11] rv: Add snroc per-task monitor Gabriele Monaco
2025-02-13  9:08 ` [PATCH v2 07/11] rv: Add scpd, snep and sncid per-cpu monitors Gabriele Monaco
2025-02-13  9:08 ` [PATCH v2 08/11] tools/rv: Add support for nested monitors Gabriele Monaco
2025-02-13  9:08 ` [PATCH v2 09/11] verification/dot2k: " Gabriele Monaco
2025-02-13  9:08 ` [PATCH v2 10/11] Documentation/rv: Add docs for the sched monitors Gabriele Monaco
2025-02-13  9:08 ` [PATCH v2 11/11] tools/rv: Allow rv list to filter for container Gabriele Monaco
2025-02-17 13:11 [PATCH v2 00/11] rv: Add scheduler specification monitors Gabriele Monaco
2025-02-17 13:11 ` [PATCH v2 04/11] rv: Add option for nested monitors and include sched Gabriele Monaco

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=c5fe1f637a84087afb94ed3f9255810ef3975724.camel@redhat.com \
    --to=gmonaco@redhat.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mingo@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®