linux-next: manual merge of the kvm-ppc tree with the powerpc-merge tree
scottwood at freescale.com
Fri Oct 12 04:28:56 EST 2012
On 10/11/2012 12:24:59 PM, Timur Tabi wrote:
> Scott Wood wrote:
> >> > My concern is that when I think of a user-space header file, I
> >> > of a
> >> > user-space application that calls ioctls. I know that KVM guest
> >> > kernels
> >> > run as user-space processes, but that does not seem like a
> reason to
> >> > combine all of the header files that the KVM guest kernel needs
> >> > "real" user-space header files.
> > So where should guest headers go?
> I admit that I don't have any answers, especially since this whole
> is new to me. Like I said, I don't know much about KVM internals, so
> just don't understand why KVM guests need to have access to these
> header files as if they're user header files. The guests are still
> kernels (or other OSes that think they're running as privileged code).
For hypercalls and other paravirt. That's the point -- they're not
kernel headers. They're guest API headers.
More information about the Linuxppc-dev