[PATCH 5/7] context_tracking: Run vtime_user_enter/exit only when state == CONTEXT_USER

2015-03-10 Thread Frederic Weisbecker
From: Rik van Riel Only run vtime_user_enter, vtime_user_exit, and the user enter & exit trace points when we are entering or exiting user state, respectively. The KVM code in guest_enter and guest_exit already take care of calling vtime_guest_enter and vtime_guest_exit, respectively. The RCU

[PATCH 5/7] context_tracking: Run vtime_user_enter/exit only when state == CONTEXT_USER

2015-03-10 Thread Frederic Weisbecker
From: Rik van Riel r...@redhat.com Only run vtime_user_enter, vtime_user_exit, and the user enter exit trace points when we are entering or exiting user state, respectively. The KVM code in guest_enter and guest_exit already take care of calling vtime_guest_enter and vtime_guest_exit,

[PATCH 5/7] context_tracking: Run vtime_user_enter/exit only when state == CONTEXT_USER

2015-03-04 Thread Frederic Weisbecker
From: Rik van Riel Only run vtime_user_enter, vtime_user_exit, and the user enter & exit trace points when we are entering or exiting user state, respectively. The KVM code in guest_enter and guest_exit already take care of calling vtime_guest_enter and vtime_guest_exit, respectively. The RCU

[PATCH 5/7] context_tracking: Run vtime_user_enter/exit only when state == CONTEXT_USER

2015-03-04 Thread Frederic Weisbecker
From: Rik van Riel r...@redhat.com Only run vtime_user_enter, vtime_user_exit, and the user enter exit trace points when we are entering or exiting user state, respectively. The KVM code in guest_enter and guest_exit already take care of calling vtime_guest_enter and vtime_guest_exit,