Re: [RFC 2/3] lockdep: be nice about compiling from userspace

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

 



On 10/25/2012 01:06 PM, Ingo Molnar wrote:
> * Sasha Levin <sasha.levin@xxxxxxxxxx> wrote:
>> Yes, we can wrap both static_obj() and debug_show_all_locks() 
>> with #ifndefs and let kvmtool provide it's own version of 
>> those two.
> 
> Only static_obj() - I see no immediate reason why you shouldn't 
> be able to utilize debug_show_all_locks(). 'vm debug -a' already 
> lists all backtraces on all vcpus - so 'vm debug lockdep -a' 
> could list all current locks and indicate which one is held and 
> by whom.

I'm not sure how we'd make debug_show_all_locks() work in userspace
since it would require us to wrap do_each_thread() & friends to iterate
over all our task_structs.

I was thinking about writing a corresponding debug_show_all_locks() that
would simply iterate a list of our dummy task_structs.


Thanks,
Sasha
--
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