Date: Tue, 2 Jun 2009 01:14:28 +0200
From: Ingo Molnar <mingo@elte.hu>
To: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf_counter: Provide functions for locking and
	pinning the context for a task
Message-ID: <20090601231428.GF749@elte.hu>
References: <18979.34748.755674.596386@cargo.ozlabs.ibm.com> <18979.35192.995732.609215@cargo.ozlabs.ibm.com> <20090601162109.GA8459@elte.hu> <18980.19019.158462.125715@cargo.ozlabs.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <18980.19019.158462.125715@cargo.ozlabs.ibm.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 813
Lines: 24


* Paul Mackerras <paulus@samba.org> wrote:

> Ingo Molnar writes:
> 
> > -tip testing found that these patches are causing a crash:
> 
> Argh.  What was userspace doing at the time of the crash, do you 
> know? It looks like it might have been on/off-lining a cpu, 
> judging by the stack trace.  Would there have been any counters 
> attached to the task doing there, or were there any per-cpu 
> counters active?

Yeah, indeed that box has a CPU hotplug testcase - sets cpu1 to 
offline then online.

There should be no counters active anywhere during that.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/