diff for duplicates of <1349973211.6903.3@snotra> diff --git a/a/1.txt b/N1/1.txt index 4d9bdf0..ed59fe0 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,49 +1,49 @@ On 10/11/2012 10:56:51 AM, Alexander Graf wrote: -> +>=20 > On 11.10.2012, at 17:50, Scott Wood wrote: -> +>=20 > > On 10/11/2012 08:04:58 AM, Alexander Graf wrote: > >> On 11.10.2012, at 05:32, Tabi Timur-B04825 wrote: -> >> > On Wed, Oct 10, 2012 at 9:47 PM, Stephen Rothwell +> >> > On Wed, Oct 10, 2012 at 9:47 PM, Stephen Rothwell =20 > <sfr@canb.auug.org.au> wrote: > >> > > >> >> Commit 549d62d889b4 ("KVM: PPC: use definitions in epapr header -> >> >> for hcalls") from the kvm-ppc tree added an include of +> >> >> for hcalls") from the kvm-ppc tree added an include of =20 > asm/epapr_hcall.h -> >> >> to the user visible part of asm/kvm_para.h so asm/epapr_hcall.h +> >> >> to the user visible part of asm/kvm_para.h so asm/epapr_hcall.h =20 > became a > >> >> user visible header file. > >> > -> >> > Any real user-space code that tries to call any of the functions +> >> > Any real user-space code that tries to call any of the functions =20 > in > >> > epapr_hcall.h will cause an exception. > > -> > Actually it'll cause a linker error, as of the "Don't use hardcoded +> > Actually it'll cause a linker error, as of the "Don't use hardcoded =20 > opcode for ePAPR hcall invocation" patch. > > > >> > Claiming that kernel header files that KVM needs are suddenly -> >> > user-space header files doesn't make much sense to me, but I +> >> > user-space header files doesn't make much sense to me, but I =20 > guess > >> > it's not my decision. -> >> This is about kvm_host.h, which is the part that is exported to -> user space. It usually contains constants and structs that are +> >> This is about kvm_host.h, which is the part that is exported to =20 +> user space. It usually contains constants and structs that are =20 > required for the API. > > > > s/kvm_host/kvm_para/ > > -> > I'm not sure anything in kvm_para.h or epapr_hcalls.h would be of -> use to userspace, but it would be of use to the guest OS, so it's +> > I'm not sure anything in kvm_para.h or epapr_hcalls.h would be of =20 +> use to userspace, but it would be of use to the guest OS, so it's =20 > still not kernel-internal. > > -> > The variable externs should be #ifdef __KERNEL__ as David points -> out. The asm stuff could still be useful in a guest OS if the guest +> > The variable externs should be #ifdef __KERNEL__ as David points =20 +> out. The asm stuff could still be useful in a guest OS if the guest =20 > provides epapr_hypercall_start. -> -> I don't think we should worry about guest kernel code potentially -> having use for this. Let's make the user space headers be great for +>=20 +> I don't think we should worry about guest kernel code potentially =20 +> having use for this. Let's make the user space headers be great for =20 > user space usage, not for guest code usage :). -Well, that asm stuff started out as a guest header (from Freescale's +Well, that asm stuff started out as a guest header (from Freescale's =20 Topaz hypervisor), not a Linux header. :-) --Scott +-Scott= diff --git a/a/content_digest b/N1/content_digest index 89ae365..0a4b58c 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,8 +4,8 @@ "Subject\0Re: linux-next: manual merge of the kvm-ppc tree with the powerpc-merge tree\0" "Date\0Thu, 11 Oct 2012 11:33:31 -0500\0" "To\0Alexander Graf <agraf@suse.de>\0" - "Cc\0Tabi Timur-B04825 <B04825@freescale.com>" - Stephen Rothwell <sfr@canb.auug.org.au> + "Cc\0Stephen Rothwell <sfr@canb.auug.org.au>" + Tabi Timur-B04825 <B04825@freescale.com> 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> @@ -14,53 +14,53 @@ "\00:1\0" "b\0" "On 10/11/2012 10:56:51 AM, Alexander Graf wrote:\n" - "> \n" + ">=20\n" "> On 11.10.2012, at 17:50, Scott Wood wrote:\n" - "> \n" + ">=20\n" "> > On 10/11/2012 08:04:58 AM, Alexander Graf wrote:\n" "> >> On 11.10.2012, at 05:32, Tabi Timur-B04825 wrote:\n" - "> >> > On Wed, Oct 10, 2012 at 9:47 PM, Stephen Rothwell \n" + "> >> > On Wed, Oct 10, 2012 at 9:47 PM, Stephen Rothwell =20\n" "> <sfr@canb.auug.org.au> wrote:\n" "> >> >\n" "> >> >> Commit 549d62d889b4 (\"KVM: PPC: use definitions in epapr header\n" - "> >> >> for hcalls\") from the kvm-ppc tree added an include of \n" + "> >> >> for hcalls\") from the kvm-ppc tree added an include of =20\n" "> asm/epapr_hcall.h\n" - "> >> >> to the user visible part of asm/kvm_para.h so asm/epapr_hcall.h \n" + "> >> >> to the user visible part of asm/kvm_para.h so asm/epapr_hcall.h =20\n" "> became a\n" "> >> >> user visible header file.\n" "> >> >\n" - "> >> > Any real user-space code that tries to call any of the functions \n" + "> >> > Any real user-space code that tries to call any of the functions =20\n" "> in\n" "> >> > epapr_hcall.h will cause an exception.\n" "> >\n" - "> > Actually it'll cause a linker error, as of the \"Don't use hardcoded \n" + "> > Actually it'll cause a linker error, as of the \"Don't use hardcoded =20\n" "> opcode for ePAPR hcall invocation\" patch.\n" "> >\n" "> >> > Claiming that kernel header files that KVM needs are suddenly\n" - "> >> > user-space header files doesn't make much sense to me, but I \n" + "> >> > user-space header files doesn't make much sense to me, but I =20\n" "> guess\n" "> >> > it's not my decision.\n" - "> >> This is about kvm_host.h, which is the part that is exported to \n" - "> user space. It usually contains constants and structs that are \n" + "> >> This is about kvm_host.h, which is the part that is exported to =20\n" + "> user space. It usually contains constants and structs that are =20\n" "> required for the API.\n" "> >\n" "> > s/kvm_host/kvm_para/\n" "> >\n" - "> > I'm not sure anything in kvm_para.h or epapr_hcalls.h would be of \n" - "> use to userspace, but it would be of use to the guest OS, so it's \n" + "> > I'm not sure anything in kvm_para.h or epapr_hcalls.h would be of =20\n" + "> use to userspace, but it would be of use to the guest OS, so it's =20\n" "> still not kernel-internal.\n" "> >\n" - "> > The variable externs should be #ifdef __KERNEL__ as David points \n" - "> out. The asm stuff could still be useful in a guest OS if the guest \n" + "> > The variable externs should be #ifdef __KERNEL__ as David points =20\n" + "> out. The asm stuff could still be useful in a guest OS if the guest =20\n" "> provides epapr_hypercall_start.\n" - "> \n" - "> I don't think we should worry about guest kernel code potentially \n" - "> having use for this. Let's make the user space headers be great for \n" + ">=20\n" + "> I don't think we should worry about guest kernel code potentially =20\n" + "> having use for this. Let's make the user space headers be great for =20\n" "> user space usage, not for guest code usage :).\n" "\n" - "Well, that asm stuff started out as a guest header (from Freescale's \n" + "Well, that asm stuff started out as a guest header (from Freescale's =20\n" "Topaz hypervisor), not a Linux header. :-)\n" "\n" - -Scott + -Scott= -ae146f44a3be228eb601317787c344bf85d10eb054462cb987d4c7b8c459955d +af160600ae005092ad87f800e57b1ae8365a140805d64dca7f46a14796894b4e
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.