lkml.org 
[lkml]   [2010]   [Mar]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC] Unify KVM kernel-space and user-space code into a single project

* Avi Kivity <avi@redhat.com> wrote:

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

And why do you say that it makes no sense to profile them?

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.

Ingo


\
 
 \ /
  Last update: 2010-03-22 21:37    [from the cache]
©2003-2011 Jasper Spaans