diff for duplicates of <1371458225.21896.153.camel@pasglop> diff --git a/a/1.txt b/N1/1.txt index caa8ecf..cf6777b 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,11 +1,13 @@ On Mon, 2013-06-17 at 17:55 +1000, Alexey Kardashevskiy wrote: > David: -> => So, in the case of MULTITCE, that's not quite right. PR KVM can +> === +> So, in the case of MULTITCE, that's not quite right. PR KVM can > emulate a PAPR system on a BookE machine, and there's no reason not to > allow TCE acceleration as well. We can't make it dependent on PAPR > mode being selected, because that's enabled per-vcpu, whereas these > capabilities are queried on the VM before the vcpus are created. -> => +> === +> > Wrong? The capability just tells qemu the kernel supports it, it doesn't have diff --git a/a/content_digest b/N1/content_digest index 5ea6c6a..76e489f 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,25 +4,27 @@ "ref\051BEC0FE.4020805@ozlabs.ru\0" "From\0Benjamin Herrenschmidt <benh@kernel.crashing.org>\0" "Subject\0Re: [PATCH 1/4] KVM: PPC: Add support for multiple-TCE hcalls\0" - "Date\0Mon, 17 Jun 2013 08:37:05 +0000\0" + "Date\0Mon, 17 Jun 2013 18:37:05 +1000\0" "To\0Alexey Kardashevskiy <aik@ozlabs.ru>\0" - "Cc\0Alexander Graf <agraf@suse.de>" - linuxppc-dev@lists.ozlabs.org - David Gibson <david@gibson.dropbear.id.au> - Paul Mackerras <paulus@samba.org> - kvm@vger.kernel.org + "Cc\0kvm@vger.kernel.org" linux-kernel@vger.kernel.org - " kvm-ppc@vger.kernel.org\0" + kvm-ppc@vger.kernel.org + Alexander Graf <agraf@suse.de> + Paul Mackerras <paulus@samba.org> + linuxppc-dev@lists.ozlabs.org + " David Gibson <david@gibson.dropbear.id.au>\0" "\00:1\0" "b\0" "On Mon, 2013-06-17 at 17:55 +1000, Alexey Kardashevskiy wrote:\n" "> David:\n" - "> => So, in the case of MULTITCE, that's not quite right. PR KVM can\n" + "> ===\n" + "> So, in the case of MULTITCE, that's not quite right. PR KVM can\n" "> emulate a PAPR system on a BookE machine, and there's no reason not to\n" "> allow TCE acceleration as well. We can't make it dependent on PAPR\n" "> mode being selected, because that's enabled per-vcpu, whereas these\n" "> capabilities are queried on the VM before the vcpus are created.\n" - "> => \n" + "> ===\n" + "> \n" "> Wrong?\n" "\n" "The capability just tells qemu the kernel supports it, it doesn't have\n" @@ -31,4 +33,4 @@ "Cheers,\n" Ben. -4e8ec7a4a511ef1d8a7f31c978446e90cf81ed4a44befbc8d31b5da9c3fbdb3c +fb9ed64c82408ec8c8d14448db3a3a593c10855c5485cdcfc6a6289bb65b14b4
diff --git a/a/1.txt b/N2/1.txt index caa8ecf..cf6777b 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,11 +1,13 @@ On Mon, 2013-06-17 at 17:55 +1000, Alexey Kardashevskiy wrote: > David: -> => So, in the case of MULTITCE, that's not quite right. PR KVM can +> === +> So, in the case of MULTITCE, that's not quite right. PR KVM can > emulate a PAPR system on a BookE machine, and there's no reason not to > allow TCE acceleration as well. We can't make it dependent on PAPR > mode being selected, because that's enabled per-vcpu, whereas these > capabilities are queried on the VM before the vcpus are created. -> => +> === +> > Wrong? The capability just tells qemu the kernel supports it, it doesn't have diff --git a/a/content_digest b/N2/content_digest index 5ea6c6a..3cbc359 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -4,7 +4,7 @@ "ref\051BEC0FE.4020805@ozlabs.ru\0" "From\0Benjamin Herrenschmidt <benh@kernel.crashing.org>\0" "Subject\0Re: [PATCH 1/4] KVM: PPC: Add support for multiple-TCE hcalls\0" - "Date\0Mon, 17 Jun 2013 08:37:05 +0000\0" + "Date\0Mon, 17 Jun 2013 18:37:05 +1000\0" "To\0Alexey Kardashevskiy <aik@ozlabs.ru>\0" "Cc\0Alexander Graf <agraf@suse.de>" linuxppc-dev@lists.ozlabs.org @@ -17,12 +17,14 @@ "b\0" "On Mon, 2013-06-17 at 17:55 +1000, Alexey Kardashevskiy wrote:\n" "> David:\n" - "> => So, in the case of MULTITCE, that's not quite right. PR KVM can\n" + "> ===\n" + "> So, in the case of MULTITCE, that's not quite right. PR KVM can\n" "> emulate a PAPR system on a BookE machine, and there's no reason not to\n" "> allow TCE acceleration as well. We can't make it dependent on PAPR\n" "> mode being selected, because that's enabled per-vcpu, whereas these\n" "> capabilities are queried on the VM before the vcpus are created.\n" - "> => \n" + "> ===\n" + "> \n" "> Wrong?\n" "\n" "The capability just tells qemu the kernel supports it, it doesn't have\n" @@ -31,4 +33,4 @@ "Cheers,\n" Ben. -4e8ec7a4a511ef1d8a7f31c978446e90cf81ed4a44befbc8d31b5da9c3fbdb3c +fa60fd83be8738c759ec1249d51781e6706b37b733a17a05d32cef452e4e93c2
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.