Re: [tip:x86/urgent] x86, trace: Fix CR2 corruption when tracing page faults
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:x86/urgent] x86, trace: Fix CR2 corruption when tracing page faults
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
- Date: Wed, 5 Mar 2014 13:25:35 +0100
- Cc: mingo@xxxxxxxxxx, hpa@xxxxxxxxx, paulus@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, acme@xxxxxxxxxxxxxxxxxx, seiji.aguchi@xxxxxxx, jolsa@xxxxxxxxxx, vincent.weaver@xxxxxxxxx, tglx@xxxxxxxxxxxxx, hpa@xxxxxxxxxxxxxxx, linux-tip-commits@xxxxxxxxxxxxxxx
- In-reply-to: <20140305072022.6f69f699@gandalf.local.home>
- User-agent: Mutt/1.5.21 (2012-12-30)
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@xxxxxxxxxxxxx> 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-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]
