diff options
| author | Steven Rostedt <srostedt@redhat.com> | 2011-05-27 23:11:24 -0400 |
|---|---|---|
| committer | Steven Rostedt <rostedt@goodmis.org> | 2011-05-27 23:47:16 -0400 |
| commit | 89e1be50c68eb5e58b873dce87bbac627ee18d1f (patch) | |
| tree | c34f3e5c37b706accec93a2dab629a1b96d57a58 /kernel/events | |
| parent | f23a5e1405e47df6cdc86568ea75df266b9e151f (diff) | |
| download | linux-stable-89e1be50c68eb5e58b873dce87bbac627ee18d1f.tar.gz linux-stable-89e1be50c68eb5e58b873dce87bbac627ee18d1f.tar.bz2 linux-stable-89e1be50c68eb5e58b873dce87bbac627ee18d1f.zip | |
x86: Put back -pg to tsc.o and add no GCOV to vread_tsc_64.o
The commit 44259b1abfaa8bb819d25d41d71e8e33e25dd36a
Author: Andy Lutomirski <luto@MIT.EDU>
x86-64: Move vread_tsc into a new file with sensible options
Removed the -pg from tsc.o which caused the function graph tracer
to go into an infinite function call recursion as it uses the tsc
internally outside its recursion protection, thus tracing the tsc
breaks the function graph tracer.
This commit also added the file vread_tsc_64.c that gets used
by vdso but failed to prevent GCOV from monkeying with it,
causing userspace to try to access kernel data when GCOV was
enabled.
Thanks to Thomas Gleixner for pointing out GCOV as the likely
culprit that added strange kernel accesses into the vread_tsc()
call.
Cc: Author: Andy Lutomirski <luto@MIT.EDU>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'kernel/events')
0 files changed, 0 insertions, 0 deletions