mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>, linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, Ingo Molnar <mingo@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	Yordan Karadzhov <y.karadz@gmail.com>
Subject: Re: [PATCH 3/3] ring-buffer: Add rb_time_t 64 bit operations for speeding up 32 bit
Date: Sat, 27 Jun 2020 14:42:00 +0800	[thread overview]
Message-ID: <202006271451.Nh2Jqysd%lkp@intel.com> (raw)
In-Reply-To: <20200627011349.968148275@goodmis.org>

[-- Attachment #1: Type: text/plain, Size: 2233 bytes --]

Hi Steven,

Thank you for the patch! Perhaps something to improve:

[auto build test WARNING on linus/master]
[also build test WARNING on v5.8-rc2 next-20200626]
[cannot apply to tip/perf/core linux/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use  as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Steven-Rostedt/ring-buffer-Restructure-ftrace-ring-buffer-time-keeping-to-allow-accurate-nested-timing/20200627-091520
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 1590a2e1c681b0991bd42c992cabfd380e0338f2
config: i386-randconfig-m021-20200624 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

smatch warnings:
kernel/trace/ring_buffer.c:685 rb_time_cmpxchg() warn: inconsistent indenting

vim +685 kernel/trace/ring_buffer.c

   677	
   678	static int rb_time_cmpxchg(rb_time_t *t, u64 expect, u64 set)
   679	{
   680		unsigned long cnt, top, bottom;
   681		unsigned long cnt2, top2, bottom2;
   682		u64 val;
   683	
   684		/* The cmpxchg always fails if it interrupted an update */
 > 685		 if (!__rb_time_read(t, &val, &cnt2))
   686			 return false;
   687	
   688		 if (val != expect)
   689			 return false;
   690	
   691		 cnt = local_read(&t->cnt);
   692		 if ((cnt & 3) != cnt2)
   693			 return false;
   694	
   695		 cnt2 = cnt + 1;
   696	
   697		 rb_time_split(val, &top, &bottom);
   698		 top = rb_time_val_cnt(top, cnt);
   699		 bottom = rb_time_val_cnt(bottom, cnt);
   700	
   701		 rb_time_split(set, &top2, &bottom2);
   702		 top2 = rb_time_val_cnt(top2, cnt2);
   703		 bottom2 = rb_time_val_cnt(bottom2, cnt2);
   704	
   705		if (!rb_time_read_cmpxchg(&t->cnt, cnt, cnt2))
   706			return false;
   707		if (!rb_time_read_cmpxchg(&t->top, top, top2))
   708			return false;
   709		if (!rb_time_read_cmpxchg(&t->bottom, bottom, bottom2))
   710			return false;
   711		return true;
   712	}
   713	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 33656 bytes --]

      reply	other threads:[~2020-06-27  6:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-27  1:00 [PATCH 0/3] ring-buffer: Restructure ftrace ring buffer time keeping to allow accurate nested timing Steven Rostedt
2020-06-27  1:00 ` [PATCH 1/3] ring-buffer: Have nested events still record running time stamp Steven Rostedt
2020-06-28 16:23   ` Masami Hiramatsu
2020-06-28 16:43     ` Steven Rostedt
2020-06-27  1:00 ` [PATCH 2/3] ring-buffer: Incorporate absolute timestamp into add_timestamp logic Steven Rostedt
2020-06-27  1:00 ` [PATCH 3/3] ring-buffer: Add rb_time_t 64 bit operations for speeding up 32 bit Steven Rostedt
2020-06-27  6:42   ` kernel test robot [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=202006271451.Nh2Jqysd%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=acme@redhat.com \
    --cc=jolsa@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=y.karadz@gmail.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

all inboxes | Powered by JetHome®