From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Peter Hurley" <peter@hurleysoftware.com>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"Bruno Prémont" <bonbons@linux-vserver.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ilya Dryomov" <ilya.dryomov@inktank.com>,
"Mike Galbraith" <umgwanakikbuti@gmail.com>,
"Oleg Nesterov" <oleg@redhat.com>
Subject: Re: Linux 3.19-rc5
Date: Tue, 3 Feb 2015 12:18:59 +0100 [thread overview]
Message-ID: <20150203111859.GA2511@gmail.com> (raw)
In-Reply-To: <20150131094811.GC32343@twins.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Thu, Jan 29, 2015 at 05:25:07PM -0800, Linus Torvalds wrote:
>
> > PeterZ, please don't make "debugging" patches like this. Ever
> > again. Because this was just stupid, and it took me too long
> > to realize that despite the warning being shut up, the debug
> > patch was still actively doing bad bad things.
>
> Understood.
It was my fault too - I should have realized this side effect of
the new debugging facility when I merged it, which side effect,
as Linus pointed it out, is a really bad idea.
We are generally pretty good at doing transparent debugging in
the scheduler and in the locking code, but screwed up this time
around :-(
Thanks,
Ingo
next prev parent reply other threads:[~2015-02-03 11:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 9:17 Linux 3.19-rc5 Linus Torvalds
2015-01-19 18:02 ` Bruno Prémont
2015-01-20 6:24 ` Linus Torvalds
2015-01-21 20:37 ` Bruno Prémont
2015-01-21 21:37 ` Bruno Prémont
2015-01-21 22:12 ` Davidlohr Bueso
2015-01-21 22:54 ` Peter Hurley
2015-01-30 1:22 ` Rafael J. Wysocki
2015-01-30 1:12 ` Linus Torvalds
2015-01-30 1:25 ` Linus Torvalds
2015-01-30 1:35 ` Linus Torvalds
2015-01-30 2:06 ` Rafael J. Wysocki
2015-01-30 15:47 ` Oleg Nesterov
2015-01-31 18:32 ` Linus Torvalds
2015-01-31 20:16 ` Peter Zijlstra
2015-01-31 21:54 ` Linus Torvalds
2015-02-02 13:19 ` Peter Zijlstra
2015-02-01 19:43 ` Oleg Nesterov
2015-02-01 20:09 ` Linus Torvalds
2015-02-01 20:19 ` Oleg Nesterov
2015-02-02 15:34 ` Peter Zijlstra
2015-01-31 9:16 ` Bruno Prémont
2015-01-31 9:48 ` Peter Zijlstra
2015-02-03 11:18 ` Ingo Molnar [this message]
2015-02-05 21:14 ` Bruno Prémont
2015-02-06 11:50 ` Peter Zijlstra
2015-02-06 16:02 ` Linus Torvalds
2015-02-06 16:39 ` Peter Zijlstra
2015-02-06 16:46 ` Linus Torvalds
2015-01-30 1:49 ` Rafael J. Wysocki
2015-02-02 9:48 ` Zdenek Kabelac
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=20150203111859.GA2511@gmail.com \
--to=mingo@kernel.org \
--cc=bonbons@linux-vserver.org \
--cc=dave@stgolabs.net \
--cc=ilya.dryomov@inktank.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peter@hurleysoftware.com \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=umgwanakikbuti@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