Re: [PATCH v2] KVM: trace the events of mmu_notifier

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 09/14/2012 08:59 AM, Xiao Guangrong wrote:
> On 09/10/2012 05:26 PM, Xiao Guangrong wrote:
>> On 09/10/2012 05:09 PM, Avi Kivity wrote:
>>> On 09/07/2012 09:16 AM, Xiao Guangrong wrote:
>>>> mmu_notifier is the interface to broadcast the mm events to KVM, the
>>>> tracepoints introduced in this patch can trace all these events, it is
>>>> very helpful for us to notice and fix the bug caused by mm
>>>
>>> There is nothing kvm specific here.  Perhaps this can be made generic
>>> (with a mm parameter so we can filter by process).
>> 
>> Hmm, i would like to put these tracepoints in the mmu-lock then we can clearly
>> know the sequence between mm and kvm mmu. It is useful for us to detect the
>> issue/race between them.
>> 
> 
> Ping...?

Sorry.  Yes you are right, knowing the exact sequence is valuable.  Yet
it will be hard to associate these events with the mmu since we don't
have gpas there.


-- 
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux