From: Ingo Molnar <mingo@kernel.org>
To: Christoph Lameter <cl@linux.com>
Cc: Tejun Heo <tj@kernel.org>,
akpm@linuxfoundation.org, linux-arch@vger.kernel.org,
Steven Rostedt <srostedt@redhat.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [pchecks v2 2/2] percpu: Add preemption checks to __this_cpu ops
Date: Thu, 3 Oct 2013 09:26:03 +0200 [thread overview]
Message-ID: <20131003072603.GB5775@gmail.com> (raw)
In-Reply-To: <0000014179b908eb-29821dc1-7b08-4dd5-b86b-a88c00864249-000000@email.amazonses.com>
* Christoph Lameter <cl@linux.com> wrote:
> > > That is exactly what this patch does. There will only be warning if
> > > the user enabled them.
> >
> > You didn't understand me apparently: all warnings that trigger with
> > the debug CONFIG option enabled must be fixed before this can be sent
> > upstream.
>
> This patchset is required to determine the warnings that will be
> triggered and to get the work to address these issues done. The feedback
> so far indicates that there may be lots of discussions regarding the
> warnings that have been discovered so far. Its not realistic to do this
> in one go.
Please submit them once you had the time to ensure that they are ready and
produce no warnings on your system(s) with debugging enabled.
To help out I can stage them for you in a branch within the scheduler tree
if you think there are spurious warnings - as long as you fix and address
any bug reports and review feedback received in a timely fashion. I'll
send it upstream once the debug code has settled down and doesn't produce
false warnings.
Also, just to make it clear, as I mentioned it in my previous mail: until
the debug code becomes upstream worthy and converge, consider all your
__this_cpu patches NAK-ed by me.
Thanks,
Ingo
next prev parent reply other threads:[~2013-10-03 7:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130924154159.855373283@linux.com>
2013-09-24 15:41 ` [pchecks v2 1/2] Subject; percpu: Add raw_cpu_ops Christoph Lameter
2013-09-24 15:41 ` Christoph Lameter
2013-09-24 15:41 ` [pchecks v2 2/2] percpu: Add preemption checks to __this_cpu ops Christoph Lameter
2013-09-24 15:41 ` Christoph Lameter
2013-09-24 17:10 ` Ingo Molnar
2013-09-25 16:40 ` Christoph Lameter
2013-09-25 18:11 ` Ingo Molnar
2013-09-27 13:54 ` Christoph Lameter
2013-09-28 8:39 ` Ingo Molnar
2013-10-02 15:11 ` Christoph Lameter
2013-10-03 7:26 ` Ingo Molnar [this message]
2013-09-28 8:44 ` Ingo Molnar
2013-10-02 15:08 ` Christoph Lameter
2013-10-03 7:21 ` Ingo Molnar
2013-10-03 13:55 ` Peter Zijlstra
2013-10-03 14:15 ` Christoph Lameter
2013-10-03 15:35 ` Ingo Molnar
2013-10-03 15:59 ` Christoph Lameter
2013-10-03 16:44 ` Ingo Molnar
[not found] <20131003182902.174251532@linux.com>
2013-10-03 18:28 ` Christoph Lameter
2013-10-04 8:27 ` Peter Zijlstra
2013-10-04 8:37 ` Ingo Molnar
2013-10-04 15:27 ` Christoph Lameter
2013-10-04 16:52 ` Peter Zijlstra
2013-10-04 17:26 ` Christoph Lameter
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=20131003072603.GB5775@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linuxfoundation.org \
--cc=cl@linux.com \
--cc=linux-arch@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.