linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Yang Jihong <yangjihong1@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
	alexander.shishkin@linux.intel.com, jolsa@kernel.org,
	namhyung@kernel.org, pc@us.ibm.com, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org
Subject: Re: [RFC v3 06/17] perf kwork: Implement perf kwork report
Date: Wed, 27 Jul 2022 11:04:35 -0300	[thread overview]
Message-ID: <YuFF83qDSyzBrhBm@kernel.org> (raw)
In-Reply-To: <b865f96a-856c-6a7d-a66a-c3343097ee5a@huawei.com>

Em Wed, Jul 27, 2022 at 08:39:33AM +0800, Yang Jihong escreveu:
> Hello,
> 
> On 2022/7/27 1:40, Arnaldo Carvalho de Melo wrote:
> > Em Sat, Jul 09, 2022 at 09:50:22AM +0800, Yang Jihong escreveu:
> > > +
> > > +static void report_print_work(struct perf_kwork *kwork,
> > > +			      struct kwork_work *work)
> > > +{
> > > +	int ret = 0;
> > > +	char kwork_name[PRINT_KWORK_NAME_WIDTH];
> > > +	char max_runtime_start[32], max_runtime_end[32];
> > 
> > Committer notes:
> > 
> > - Add some {} for multiline for/if blocks
> > 
> > - Return the calculated number of printed bytes in report_print_work,
> >    otherwise soem compilers will complain that variable isn't used, e.g.:
> > 
> >     2    92.64 almalinux:9                   : FAIL clang version 13.0.1 (Red Hat 13.0.1-1.el9)
> >      builtin-kwork.c:1061:6: error: variable 'ret' set but not used [-Werror,-Wunused-but-set-variable]
> >              int ret = 0;
> > 
> > 
> OK, I'll fix it in next version.

your work with these fixups is already at acme/perf/core:

git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git perf/core

Please continue from there. Please let me know if I made some mistake.

Thanks for working on this!

- Arnaldo

  reply	other threads:[~2022-07-27 14:04 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09  1:50 [RFC v3 00/17] perf: Add perf kwork Yang Jihong
2022-07-09  1:50 ` [RFC v3 01/17] perf kwork: New tool Yang Jihong
2022-07-26 17:27   ` Arnaldo Carvalho de Melo
2022-07-27  0:38     ` Yang Jihong
2022-07-27 23:33   ` Namhyung Kim
2022-07-28 11:48     ` Yang Jihong
2022-07-09  1:50 ` [RFC v3 02/17] perf kwork: Add irq kwork record support Yang Jihong
2022-07-27 23:42   ` Namhyung Kim
2022-07-28 11:50     ` Yang Jihong
2022-07-09  1:50 ` [RFC v3 03/17] perf kwork: Add softirq " Yang Jihong
2022-07-09  1:50 ` [RFC v3 04/17] perf kwork: Add workqueue " Yang Jihong
2022-07-09  1:50 ` [RFC v3 05/17] tools lib: Add list_last_entry_or_null Yang Jihong
2022-07-09  1:50 ` [RFC v3 06/17] perf kwork: Implement perf kwork report Yang Jihong
2022-07-26 17:40   ` Arnaldo Carvalho de Melo
2022-07-27  0:39     ` Yang Jihong
2022-07-27 14:04       ` Arnaldo Carvalho de Melo [this message]
2022-07-28 12:01         ` Yang Jihong
2022-07-28  0:00   ` Namhyung Kim
2022-07-28 11:55     ` Yang Jihong
2022-07-09  1:50 ` [RFC v3 07/17] perf kwork: Add irq report support Yang Jihong
2022-07-09  1:50 ` [RFC v3 08/17] perf kwork: Add softirq " Yang Jihong
2022-07-09  1:50 ` [RFC v3 09/17] perf kwork: Add workqueue " Yang Jihong
2022-07-09  1:50 ` [RFC v3 10/17] perf kwork: Implement perf kwork latency Yang Jihong
2022-07-09  1:50 ` [RFC v3 11/17] perf kwork: Add softirq latency support Yang Jihong
2022-07-09  1:50 ` [RFC v3 12/17] perf kwork: Add workqueue " Yang Jihong
2022-07-09  1:50 ` [RFC v3 13/17] perf kwork: Implement perf kwork timehist Yang Jihong
2022-07-09  1:50 ` [RFC v3 14/17] perf kwork: Implement bpf trace Yang Jihong
2022-07-09  1:50 ` [RFC v3 15/17] perf kwork: Add irq trace bpf support Yang Jihong
2022-07-25 21:39   ` Arnaldo Carvalho de Melo
2022-07-09  1:50 ` [RFC v3 16/17] perf kwork: Add softirq " Yang Jihong
2022-07-09  1:50 ` [RFC v3 17/17] perf kwork: Add workqueue " Yang Jihong
2022-07-16  9:14 ` [RFC v3 00/17] perf: Add perf kwork Yang Jihong
2022-07-17 13:29   ` Arnaldo Carvalho de Melo
2022-07-25 21:45 ` [RFC v3 00/17] perf: Add perf kwork (using BPF skels) Arnaldo Carvalho de Melo
2022-07-27  0:36   ` Yang Jihong

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=YuFF83qDSyzBrhBm@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --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=pc@us.ibm.com \
    --cc=peterz@infradead.org \
    --cc=yangjihong1@huawei.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).