linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Christoph Lameter <cl@linux.com>
Cc: Tejun Heo <tj@kernel.org>,
	akpm@linuxfoundation.org, Steven Rostedt <srostedt@redhat.com>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [pchecks v2 0/2] percpu v3: Implement Preemption checks for __this_cpu operations
Date: Fri, 4 Oct 2013 08:01:36 +0200	[thread overview]
Message-ID: <20131004060136.GB11399@gmail.com> (raw)
In-Reply-To: <000001417f93f8eb-802d2cf9-29b6-46b7-975e-b909a5c17783-000000@email.amazonses.com>


* Christoph Lameter <cl@linux.com> wrote:

> This patchset introduces preemption checks for __this_cpu operations.
> 
> First we add new raw_cpu operations that perform this cpu operations
> without preempt checks. 
> 
> The second patch then adds the preempt checks by modifying the
> __this_cpu macros in include/linux/percpu.h

Patch submission technical feedback: your 0/2 mail is still non-standard, 
it arrived out of order and looks broken - why isn't it threaded to the 
other patches? Here is how it looks like in my mailer:

You should either use "git send-email" to create proper threading (you can 
use that even if you originally created the series via Quilt), or you can 
send them manually with proper threading (that's what I did years ago when 
I still used Quilt).

You should not burden lkml with broken-format submissions, especially as 
the size of this patch series is expected to grow in the future, as you 
fix false positive warnings.

64877   C Oct 03 Christoph Lamet ( 206) ┬─>[pchecks v2 2/2] percpu: Add preemption checks to __this_cpu ops
64878   C Oct 03 Christoph Lamet ( 121) └─>[pchecks v2 1/2] percpu: Add raw_cpu_ops
64879   C Oct 03 Christoph Lamet (  24) [pchecks v2 0/2] percpu v3: Implement Preemption checks for __this_cpu operatio

> V2->V3:
> 	- Subject line in the raw_cpu_ops patch had ; instead of :.
> 	  Guess I am getting old.
> 	- Improve descriptions and variable names.
> 	- Run tests again with kvm to verify that it still works.
> 		A) No warnings with just the patches applied
> 		B) Lots of warnings with CONFIG_DEBUG_THIS_CPU_OPERATIONS enabled

Patch series technical feedback: it's standard kernel debugging 
infrastructure policy that all warnings that trigger with debugging 
enabled need to be fixed, so your series will need to fix them before I 
can move forward with merging these patches.

Please fix these technical shortcomings before your next submission.

Thanks,

	Ingo

  reply	other threads:[~2013-10-04  6:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03 18:28 [pchecks v2 0/2] percpu v3: Implement Preemption checks for __this_cpu operations Christoph Lameter
2013-10-04  6:01 ` Ingo Molnar [this message]
2013-10-04  8:18 ` Peter Zijlstra
2013-10-04  8:30   ` Ingo Molnar

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=20131004060136.GB11399@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linuxfoundation.org \
    --cc=cl@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=srostedt@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).