# Re: linux-next: manual merge of the kvm-ppc tree with the powerpc-merge tree

- List: linuxppc-dev
- 2 messages, 2 authors
- Page: https://ratatoskr.run/linuxppc-dev/2012/10/3938210/t

## Re: linux-next: manual merge of the kvm-ppc tree with the powerpc-merge tree

- From: Scott Wood \<hidden\>
- Date: 2012-10-11 16:37:24 
- Message: https://ratatoskr.run/linuxppc-dev/2012/10/3938210.md

```text
On 10/11/2012 10:55:42 AM, Timur Tabi wrote:
> Alexander Graf wrote:
>=20
>=20
> > This is about kvm_host.h, which is the part that is exported to user
> > space. It usually contains constants and structs that are required =20
> for
> > the API.
>=20
> Which API?  I'm not familiar with KVM internals.
>=20
> My concern is that when I think of a user-space header file, I think =20
> of a
> user-space application that calls ioctls.  I know that KVM guest =20
> 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 with
> "real" user-space header files.

So where should guest headers go?

-Scott=
```

## Re: linux-next: manual merge of the kvm-ppc tree with the powerpc-merge tree

- From: Timur Tabi \<hidden\>
- Date: 2012-10-11 17:25:08 
- Message: https://ratatoskr.run/linuxppc-dev/2012/10/3938227.md

```text
Scott Wood wrote:
>> > My concern is that when I think of a user-space header file, I think  
>> > 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 with
>> > "real" user-space header files.

> So where should guest headers go?

I admit that I don't have any answers, especially since this whole thing
is new to me.  Like I said, I don't know much about KVM internals, so I
just don't understand why KVM guests need to have access to these kernel
header files as if they're user header files.  The guests are still Linux
kernels (or other OSes that think they're running as privileged code).

-- 
Timur Tabi
Linux kernel developer at Freescale
```