Re: [RFC] Unify KVM kernel-space and user-space code into a single project

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

 



On 03/22/2010 10:35 PM, Ingo Molnar wrote:

And your point is that such vcpus should be excluded from profiling just
because they fall outside the Qemu/libvirt umbrella?

That is a ridiculous position.

Non-guest vcpus will not be able to provide Linux-style symbols.
And why do you say that it makes no sense to profile them?

It makes sense to profile them, but you don't need to contact their userspace tool for that.

Also, why do you define 'guest vcpus' to be 'Qemu started guest vcpus'? If
some other KVM using project (which you encouraged just a few mails ago)
starts a vcpu we still want to be able to profile them.


Maybe it should provide a mechanism for libvirt to list it.

--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

--
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