[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140305122535.GA9987@twins.programming.kicks-ass.net>
Date: Wed, 5 Mar 2014 13:25:35 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: mingo@...nel.org, hpa@...or.com, paulus@...ba.org,
linux-kernel@...r.kernel.org, acme@...stprotocols.net,
seiji.aguchi@....com, jolsa@...hat.com, vincent.weaver@...ne.edu,
tglx@...utronix.de, hpa@...ux.intel.com,
linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/urgent] x86, trace: Fix CR2 corruption when tracing
page faults
On Wed, Mar 05, 2014 at 07:20:22AM -0500, Steven Rostedt wrote:
> On Wed, 5 Mar 2014 12:14:15 +0100
> Peter Zijlstra <peterz@...radead.org> wrote:
>
> Please no! I used tracing of the do_page_fault function all the time.
> It is very useful.
Why do you trace do_page_fault and not the __do_page_fault() function?
do_page_fault() is a minimal wrapper which doesn't actually do all that
much?
--
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