diff options
author | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2018-11-09 15:22:07 -0500 |
---|---|---|
committer | Borislav Petkov <bp@suse.de> | 2018-11-09 21:39:14 +0100 |
commit | 15035388439f892017d38b05214d3cda6578af64 (patch) | |
tree | ff9500df39c6cd0e13a89450e4ac1f801c832857 /arch/x86/include | |
parent | a48777fdda7d13179979a889e1fb87655a783cc0 (diff) | |
download | linux-15035388439f892017d38b05214d3cda6578af64.tar.bz2 |
x86/cpu/vmware: Do not trace vmware_sched_clock()
When running function tracing on a Linux guest running on VMware
Workstation, the guest would crash. This is due to tracing of the
sched_clock internal call of the VMware vmware_sched_clock(), which
causes an infinite recursion within the tracing code (clock calls must
not be traced).
Make vmware_sched_clock() not traced by ftrace.
Fixes: 80e9a4f21fd7c ("x86/vmware: Add paravirt sched clock")
Reported-by: GwanYeong Kim <gy741.kim@gmail.com>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Signed-off-by: Borislav Petkov <bp@suse.de>
CC: Alok Kataria <akataria@vmware.com>
CC: GwanYeong Kim <gy741.kim@gmail.com>
CC: "H. Peter Anvin" <hpa@zytor.com>
CC: Ingo Molnar <mingo@kernel.org>
Cc: stable@vger.kernel.org
CC: Thomas Gleixner <tglx@linutronix.de>
CC: virtualization@lists.linux-foundation.org
CC: x86-ml <x86@kernel.org>
Link: http://lkml.kernel.org/r/20181109152207.4d3e7d70@gandalf.local.home
Diffstat (limited to 'arch/x86/include')
0 files changed, 0 insertions, 0 deletions