From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <ak@suse.de>
Cc: Arjan van de Ven <arjan@infradead.org>,
Dave Airlie <airlied@linux.ie>,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, hch@lst.de, pq@iki.fi,
jbeulich@novell.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "x86: optimize page faults like all other achitectures and kill notifier cruft"
Date: Wed, 9 Jan 2008 16:26:40 +0100 [thread overview]
Message-ID: <20080109152640.GA21909@elte.hu> (raw)
In-Reply-To: <20080109152115.GJ25945@bingen.suse.de>
* Andi Kleen <ak@suse.de> wrote:
> On Wed, Jan 09, 2008 at 07:18:46AM -0800, Arjan van de Ven wrote:
> > On Wed, 9 Jan 2008 03:17:37 +0000 (GMT)
> > Dave Airlie <airlied@linux.ie> wrote:
> >
> > > So all distros with 2.6.24 kernels are useless to mmiotrace I don't
> > > see why leaving things as is until a suitable replacement mechanism
> > > can be used..
> >
> > you work for a distro.. surely you can convince your own distro to
> > carry this patch for one release? Maybe if it's this important.. so
> > can the others...
>
> But if it's good for a major distribution why is it not good for
> mainline?
it's a bit too late to get the out-of-tree module into v2.6.24, and the
revert makes little sense without the extra out-of-tree module. We at a
minimum need a clear explanation of why this functionality cannot be
provided via kprobes/systemtap.
> We had this discussion at last kernel summit and the answer was clear.
it's a clear answer 1 week after the merge window opens, but not 1 week
before the next stable kernel is released.
Ingo
next prev parent reply other threads:[~2008-01-09 15:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 2:34 [PATCH] Revert "x86: optimize page faults like all other achitectures and kill notifier cruft" Dave Airlie
2008-01-09 2:37 ` Andi Kleen
2008-01-09 3:06 ` Andrew Morton
2008-01-09 3:17 ` Dave Airlie
2008-01-09 3:29 ` Andrew Morton
2008-01-09 3:55 ` Dave Airlie
2008-01-09 7:19 ` Christoph Hellwig
2008-01-09 7:23 ` David Miller
2008-01-09 10:41 ` Ingo Molnar
2008-01-09 16:52 ` Mathieu Desnoyers
2008-01-09 19:07 ` Andi Kleen
2008-01-09 20:01 ` Pekka Paalanen
2008-01-09 20:08 ` Andi Kleen
2008-01-09 4:17 ` Andi Kleen
2008-01-09 9:12 ` Jan Beulich
2008-01-09 15:18 ` Arjan van de Ven
2008-01-09 15:21 ` Andi Kleen
2008-01-09 15:26 ` Ingo Molnar [this message]
2008-01-09 7:17 ` Christoph Hellwig
2008-01-09 7:22 ` David Miller
2008-01-09 13:19 ` Jiri Kosina
2008-01-09 13:48 ` David Miller
2008-01-09 14:23 ` Andi Kleen
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=20080109152640.GA21909@elte.hu \
--to=mingo@elte.hu \
--cc=airlied@linux.ie \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=hch@lst.de \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pq@iki.fi \
--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 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.