[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1258980648.4531.390.camel@laptop>
Date: Mon, 23 Nov 2009 13:50:48 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: mingo@...hat.com, hpa@...or.com, paulus@...ba.org,
linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...e.hu,
linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] perf_events: Undo some recursion damage
On Mon, 2009-11-23 at 13:39 +0100, Frederic Weisbecker wrote:
> On Mon, Nov 23, 2009 at 11:55:08AM +0000, tip-bot for Peter Zijlstra wrote:
> > Commit-ID: 4ed7c92d68a5387ba5f7030dc76eab03558e27f5
> > Gitweb: http://git.kernel.org/tip/4ed7c92d68a5387ba5f7030dc76eab03558e27f5
> > Author: Peter Zijlstra <a.p.zijlstra@...llo.nl>
> > AuthorDate: Mon, 23 Nov 2009 11:37:29 +0100
> > Committer: Ingo Molnar <mingo@...e.hu>
> > CommitDate: Mon, 23 Nov 2009 11:49:57 +0100
> >
> > perf_events: Undo some recursion damage
> >
> > Make perf_swevent_get_recursion_context return a context number
> > and disable preemption.
> >
> > This could be used to remove the IRQ disable from the trace bit
> > and index the per-cpu buffer with.
>
>
> But if I do that, it means I will lose traces once irq nest.
Ah yes, that crap :-(
Maybe its about time we extend the generic irq bits to know about nested
irqs, or firmly kill the whole notion.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists