On 20.11.14 11:40, Aneesh Kumar K.V wrote:
> "Suresh E. Warrier" <warr...@linux.vnet.ibm.com> writes:
> 
>> This patch adds trace points in the guest entry and exit code and also
>> for exceptions handled by the host in kernel mode - hypercalls and page
>> faults. The new events are added to /sys/kernel/debug/tracing/events
>> under a new subsystem called kvm_hv.
> 
> ........
> 
>>      /* Set this explicitly in case thread 0 doesn't have a vcpu */
>> @@ -1687,6 +1691,9 @@ static void kvmppc_run_core(struct kvmppc_vcore *vc)
>>  
>>      vc->vcore_state = VCORE_RUNNING;
>>      preempt_disable();
>> +
>> +    trace_kvmppc_run_core(vc, 0);
>> +
>>      spin_unlock(&vc->lock);
> 
> Do we really want to call tracepoint with spin lock held ? Is that a good
> thing to do ?. 

I thought it was safe to call tracepoints inside of spin lock regions?
Steve?


Alex
--
To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to