[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54D3B253.3050000@sr71.net>
Date: Thu, 05 Feb 2015 10:11:31 -0800
From: Dave Hansen <dave@...1.net>
To: Steven Rostedt <rostedt@...dmis.org>
CC: sedat.dilek@...il.com, Paul McKenney <paulmck@...ux.vnet.ibm.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
linux-next <linux-next@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Kristen Carlson Accardi <kristen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...ux.intel.com>,
Rik van Riel <riel@...hat.com>, Mel Gorman <mgorman@...e.de>
Subject: Re: linux-next: Tree for Feb 4
On 02/05/2015 10:08 AM, Steven Rostedt wrote:
> --- a/include/trace/events/tlb.h
> +++ b/include/trace/events/tlb.h
> @@ -13,11 +13,13 @@
> { TLB_LOCAL_SHOOTDOWN, "local shootdown" }, \
> { TLB_LOCAL_MM_SHOOTDOWN, "local mm shootdown" }
>
> -TRACE_EVENT(tlb_flush,
> +TRACE_EVENT_CONDITION(tlb_flush,
>
> TP_PROTO(int reason, unsigned long pages),
> TP_ARGS(reason, pages),
>
> + TP_CONDITION(cpu_online(smp_processor_id())),
That's a pretty reasonable fix, although it would be nice if the
debugging was easier to hit. Did I actually need to be
onlining/offlining CPUs to hit the splat that Sedat was reporting?
--
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