public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
	Adrian Bunk <adrian.bunk@movial.fi>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	phil.el@wanadoo.fr, oprofile-list@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: Fwd: Re: [2.6.24 patch] restore ARMv6 OProfile support
Date: Tue, 15 Jan 2008 17:32:51 +0100	[thread overview]
Message-ID: <20080115163251.GC31270@elte.hu> (raw)
In-Reply-To: <alpine.LFD.1.00.0801150811250.2806@woody.linux-foundation.org>


* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> But as mentioned, it's totally untested and I don't have (or really 
> want to have) a cross-compiling environment. And I don't care *that* 
> much. I just want something we can all live with.
> 
> So does something like this work for people?

>  arch/arm/Kconfig                 |    2 +-
>  arch/arm/Kconfig.instrumentation |   52 ++++++++++++++++++++++++++++++++++++++
>  2 files changed, 53 insertions(+), 1 deletions(-)

i like this approach better, not the least because it affects only one 
architecture so late in the .24-rc cycle. Instrumentation bugs tend to 
be found with a few weeks/months of delays. (because historically 
instrumentation has been typically used by folks who cannot change their 
kernel easily to debug it, i.e. by extension they dont run bleeding edge 
kernels either.)

Acked-by: Ingo Molnar <mingo@elte.hu>

	Ingo

  reply	other threads:[~2008-01-15 16:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-28 19:58 Fwd: Re: [2.6.24 patch] restore ARMv6 OProfile support Russell King
2008-01-15 10:45 ` Russell King
2008-01-15 12:02   ` Adrian Bunk
2008-01-15 14:05     ` Mathieu Desnoyers
2008-01-15 16:24   ` Linus Torvalds
2008-01-15 16:32     ` Ingo Molnar [this message]
2008-01-15 17:02     ` Russell King
2008-01-15 17:37     ` Mathieu Desnoyers
2008-01-15 18:52       ` Linus Torvalds
2008-01-15 19:07         ` Mathieu Desnoyers
2008-01-15 19:16           ` Sam Ravnborg
2008-01-15 19:50             ` Mathieu Desnoyers
2008-01-15 20:10           ` Linus Torvalds
2008-01-15 17:49     ` Russell King
2008-01-15 18:06       ` Adrian Bunk

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=20080115163251.GC31270@elte.hu \
    --to=mingo@elte.hu \
    --cc=adrian.bunk@movial.fi \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=oprofile-list@lists.sourceforge.net \
    --cc=phil.el@wanadoo.fr \
    --cc=randy.dunlap@oracle.com \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=torvalds@linux-foundation.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