From: Scott Wood <scottwood@freescale.com>
To: Timur Tabi <B04825@freescale.com>
Cc: Alexander Graf <agraf@suse.de>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: linux-next: manual merge of the kvm-ppc tree with the powerpc-merge tree
Date: Thu, 11 Oct 2012 11:37:18 -0500 [thread overview]
Message-ID: <1349973438.6903.4@snotra> (raw)
In-Reply-To: <5076EBFE.5060208@freescale.com> (from B04825@freescale.com on Thu Oct 11 10:55:42 2012)
On 10/11/2012 10:55:42 AM, Timur Tabi wrote:
> Alexander Graf wrote:
>
>
> > 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
> for
> > the API.
>
> Which API? I'm not familiar with KVM internals.
>
> 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?
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood@freescale.com>
To: Timur Tabi <B04825@freescale.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Alexander Graf <agraf@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: linux-next: manual merge of the kvm-ppc tree with the powerpc-merge tree
Date: Thu, 11 Oct 2012 11:37:18 -0500 [thread overview]
Message-ID: <1349973438.6903.4@snotra> (raw)
In-Reply-To: <5076EBFE.5060208@freescale.com> (from B04825@freescale.com on Thu Oct 11 10:55:42 2012)
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=
next prev parent reply other threads:[~2012-10-11 16:37 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 1:18 linux-next: manual merge of the kvm-ppc tree with the powerpc-merge tree Stephen Rothwell
2012-10-11 1:18 ` Stephen Rothwell
2012-10-11 1:18 ` Stephen Rothwell
2012-10-11 1:47 ` Tabi Timur-B04825
2012-10-11 1:47 ` Tabi Timur-B04825
2012-10-11 2:47 ` Stephen Rothwell
2012-10-11 2:47 ` Stephen Rothwell
2012-10-11 3:32 ` Tabi Timur-B04825
2012-10-11 3:32 ` Tabi Timur-B04825
2012-10-11 3:32 ` Tabi Timur-B04825
2012-10-11 13:04 ` Alexander Graf
2012-10-11 13:04 ` Alexander Graf
2012-10-11 15:50 ` Scott Wood
2012-10-11 15:50 ` Scott Wood
2012-10-11 15:56 ` Alexander Graf
2012-10-11 15:56 ` Alexander Graf
2012-10-11 16:33 ` Scott Wood
2012-10-11 16:33 ` Scott Wood
2012-10-11 15:55 ` Timur Tabi
2012-10-11 15:55 ` Timur Tabi
2012-10-11 16:37 ` Scott Wood [this message]
2012-10-11 16:37 ` Scott Wood
2012-10-11 17:24 ` Timur Tabi
2012-10-11 17:24 ` Timur Tabi
2012-10-11 17:28 ` Scott Wood
2012-10-11 17:28 ` Scott Wood
2012-10-11 17:30 ` Timur Tabi
2012-10-11 17:30 ` Timur Tabi
2012-10-11 9:28 ` David Howells
2012-10-11 9:28 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2012-10-11 1:05 Stephen Rothwell
2012-10-11 1:05 ` Stephen Rothwell
2012-10-11 1:05 ` Stephen Rothwell
2012-10-11 9:27 ` David Howells
2012-10-11 9:27 ` David Howells
2012-10-11 13:08 ` Alexander Graf
2012-10-11 13:08 ` Alexander Graf
2012-10-11 16:05 ` David Howells
2012-10-11 16:05 ` David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1349973438.6903.4@snotra \
--to=scottwood@freescale.com \
--cc=B04825@freescale.com \
--cc=agraf@suse.de \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.