diff for duplicates of <1349976536.6903.7@snotra> diff --git a/a/1.txt b/N1/1.txt index 2d9b577..d52f4ce 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,29 +1,29 @@ 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 +> >> > My concern is that when I think of a user-space header file, I =20 > 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 +> >> > run as user-space processes, but that does not seem like a =20 > reason to -> >> > combine all of the header files that the KVM guest kernel needs +> >> > combine all of the header files that the KVM guest kernel needs =20 > with > >> > "real" user-space header files. -> +>=20 > > So where should guest headers go? -> -> I admit that I don't have any answers, especially since this whole +>=20 +> I admit that I don't have any answers, especially since this whole =20 > thing -> is new to me. Like I said, I don't know much about KVM internals, so +> is new to me. Like I said, I don't know much about KVM internals, so =20 > I -> just don't understand why KVM guests need to have access to these +> just don't understand why KVM guests need to have access to these =20 > kernel -> header files as if they're user header files. The guests are still +> header files as if they're user header files. The guests are still =20 > Linux > kernels (or other OSes that think they're running as privileged code). -For hypercalls and other paravirt. That's the point -- they're not +For hypercalls and other paravirt. That's the point -- they're not =20 kernel headers. They're guest API headers. --scott +-scott= diff --git a/a/content_digest b/N1/content_digest index a11a47c..a29643a 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -10,8 +10,8 @@ "Subject\0Re: linux-next: manual merge of the kvm-ppc tree with the powerpc-merge tree\0" "Date\0Thu, 11 Oct 2012 12:28:56 -0500\0" "To\0Timur Tabi <B04825@freescale.com>\0" - "Cc\0Alexander Graf <agraf@suse.de>" - Stephen Rothwell <sfr@canb.auug.org.au> + "Cc\0Stephen 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> @@ -21,32 +21,32 @@ "b\0" "On 10/11/2012 12:24:59 PM, Timur Tabi wrote:\n" "> Scott Wood wrote:\n" - "> >> > My concern is that when I think of a user-space header file, I \n" + "> >> > My concern is that when I think of a user-space header file, I =20\n" "> think\n" "> >> > of a\n" "> >> > user-space application that calls ioctls. I know that KVM guest\n" "> >> > kernels\n" - "> >> > run as user-space processes, but that does not seem like a \n" + "> >> > run as user-space processes, but that does not seem like a =20\n" "> reason to\n" - "> >> > combine all of the header files that the KVM guest kernel needs \n" + "> >> > combine all of the header files that the KVM guest kernel needs =20\n" "> with\n" "> >> > \"real\" user-space header files.\n" - "> \n" + ">=20\n" "> > So where should guest headers go?\n" - "> \n" - "> I admit that I don't have any answers, especially since this whole \n" + ">=20\n" + "> I admit that I don't have any answers, especially since this whole =20\n" "> thing\n" - "> is new to me. Like I said, I don't know much about KVM internals, so \n" + "> is new to me. Like I said, I don't know much about KVM internals, so =20\n" "> I\n" - "> just don't understand why KVM guests need to have access to these \n" + "> just don't understand why KVM guests need to have access to these =20\n" "> kernel\n" - "> header files as if they're user header files. The guests are still \n" + "> header files as if they're user header files. The guests are still =20\n" "> Linux\n" "> kernels (or other OSes that think they're running as privileged code).\n" "\n" - "For hypercalls and other paravirt. That's the point -- they're not \n" + "For hypercalls and other paravirt. That's the point -- they're not =20\n" "kernel headers. They're guest API headers.\n" "\n" - -scott + -scott= -05b16e52e1ed98fbb97f7b49163cd33996ccf99e33cf3fc0a2fb382f9c9c8d7d +cd20a3389fa48fb2d5db3c05e92e73e19e19df4598fc94b187a03e7e5f0a3f81
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.