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

[Avi Kivity]

On 03/22/2010 01:48 PM, Ingo Molnar wrote:
> * Avi Kivity<avi@xxxxxxxxxx>  wrote:
>
>    
> > > My 10+ years experience with kernel instrumentation solutions is that
> > > kernel-driven, self-sufficient, robust, trustable, well-enumerated sources
> > > of information work far better in practice.
> > >        
> > What about line number information?  And the source?  Into the kernel with
> > them as well?
> >      
> Sigh. Please read the _very first_ suggestion i made, which solves all that. I
> rarely go into discussions without suggesting technical solutions - i'm not
> interested in flaming, i'm interested in real solutions.
>
> Here it is, repeated for the Nth time:
>
> Allow a guest to (optionally) integrate its VFS namespace with the host side
> as well. An example scheme would be:
>
>     /guests/Fedora-G1/
>    

[...]

You're missing something.  This sub-thread is about someone launching a 
kernel with 'qemu -kernel', the kernel lives outside the guest disk 
image, they don't want a custom initrd because it's hard to make.

--
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/