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 09:22 PM, Ingo Molnar wrote:

Transitive had a product that was using a KVM context to run their
binary translator which allowed them full access to the host
processes virtual address space range.  In this case, there is no
kernel and there are no devices.
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.

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