diff for duplicates of <1374877620.30721.32@snotra> diff --git a/a/1.txt b/N1/1.txt index 5366bc6..b3106c9 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -4,22 +4,22 @@ On 07/25/2013 03:50:42 AM, Gleb Natapov wrote: > ppc_md.phys_mem_access_prot() is not provided. Making access to MMIO > noncached as a safe fallback makes sense. -There's only one current implementation of -ppc_md.phys_mem_access_prot(), which is pci_phys_mem_access_prot(), -which also uses page_is_ram(). If page_is_ram() returns false then it -checks for write-combining PCI. But yes, we would want to call +There's only one current implementation of =20 +ppc_md.phys_mem_access_prot(), which is pci_phys_mem_access_prot(), =20 +which also uses page_is_ram(). If page_is_ram() returns false then it =20 +checks for write-combining PCI. But yes, we would want to call =20 ppc_md.phys_mem_access_prot() if present. -Copying from the host PTE would be ideal if doesn't come with a -noticeable performance impact compared to other methods, but one way or +Copying from the host PTE would be ideal if doesn't come with a =20 +noticeable performance impact compared to other methods, but one way or =20 another we want to be sure we match. -> It is also make sense to allow noncached access to reserved ram +> It is also make sense to allow noncached access to reserved ram =20 > sometimes. -Perhaps, but that's not KVM's decision to make. You should get the -same result as if you mmaped it -- because QEMU already did and we need -to be consistent. Not to mention the large page kernel mapping that +Perhaps, but that's not KVM's decision to make. You should get the =20 +same result as if you mmaped it -- because QEMU already did and we need =20 +to be consistent. Not to mention the large page kernel mapping that =20 will have been done on e500... --Scott +-Scott= diff --git a/a/content_digest b/N1/content_digest index 5237e6e..5993d95 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,14 +1,14 @@ "ref\020130725085042.GJ16400@redhat.com\0" "From\0Scott Wood <scottwood@freescale.com>\0" "Subject\0Re: [PATCH 2/2] kvm: powerpc: set cache coherency only for kernel managed pages\0" - "Date\0Fri, 26 Jul 2013 22:27:00 +0000\0" + "Date\0Fri, 26 Jul 2013 17:27:00 -0500\0" "To\0Gleb Natapov <gleb@redhat.com>\0" - "Cc\0Alexander Graf <agraf@suse.de>" - Bhushan Bharat-R65777 <R65777@freescale.com> - " \342\200\234tiejun.chen\342\200\235 <tiejun.chen@windriver.com>" - kvm-ppc@vger.kernel.org <kvm-ppc@vger.kernel.org> + "Cc\0Wood Scott-B07421 <B07421@freescale.com>" kvm@vger.kernel.org list <kvm@vger.kernel.org> - Wood Scott-B07421 <B07421@freescale.com> + Alexander Graf <agraf@suse.de> + kvm-ppc@vger.kernel.org <kvm-ppc@vger.kernel.org> + " \342\200\234tiejun.chen\342\200\235 <tiejun.chen@windriver.com>" + Bhushan Bharat-R65777 <R65777@freescale.com> Paolo Bonzini <pbonzini@redhat.com> " linuxppc-dev@lists.ozlabs.org\0" "\00:1\0" @@ -19,24 +19,24 @@ "> ppc_md.phys_mem_access_prot() is not provided. Making access to MMIO\n" "> noncached as a safe fallback makes sense.\n" "\n" - "There's only one current implementation of \n" - "ppc_md.phys_mem_access_prot(), which is pci_phys_mem_access_prot(), \n" - "which also uses page_is_ram(). If page_is_ram() returns false then it \n" - "checks for write-combining PCI. But yes, we would want to call \n" + "There's only one current implementation of =20\n" + "ppc_md.phys_mem_access_prot(), which is pci_phys_mem_access_prot(), =20\n" + "which also uses page_is_ram(). If page_is_ram() returns false then it =20\n" + "checks for write-combining PCI. But yes, we would want to call =20\n" "ppc_md.phys_mem_access_prot() if present.\n" "\n" - "Copying from the host PTE would be ideal if doesn't come with a \n" - "noticeable performance impact compared to other methods, but one way or \n" + "Copying from the host PTE would be ideal if doesn't come with a =20\n" + "noticeable performance impact compared to other methods, but one way or =20\n" "another we want to be sure we match.\n" "\n" - "> It is also make sense to allow noncached access to reserved ram \n" + "> It is also make sense to allow noncached access to reserved ram =20\n" "> sometimes.\n" "\n" - "Perhaps, but that's not KVM's decision to make. You should get the \n" - "same result as if you mmaped it -- because QEMU already did and we need \n" - "to be consistent. Not to mention the large page kernel mapping that \n" + "Perhaps, but that's not KVM's decision to make. You should get the =20\n" + "same result as if you mmaped it -- because QEMU already did and we need =20\n" + "to be consistent. Not to mention the large page kernel mapping that =20\n" "will have been done on e500...\n" "\n" - -Scott + -Scott= -1df115325fed9712fd73c67217ecf7c18f14d3d9d52a21ae8e875a16659201a2 +6a3d4227bbc2506876b6aff25014389b4bc83eb2be17b1c80313c759b2a22ecd
diff --git a/a/content_digest b/N2/content_digest index 5237e6e..73abf96 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,7 +1,7 @@ "ref\020130725085042.GJ16400@redhat.com\0" "From\0Scott Wood <scottwood@freescale.com>\0" "Subject\0Re: [PATCH 2/2] kvm: powerpc: set cache coherency only for kernel managed pages\0" - "Date\0Fri, 26 Jul 2013 22:27:00 +0000\0" + "Date\0Fri, 26 Jul 2013 17:27:00 -0500\0" "To\0Gleb Natapov <gleb@redhat.com>\0" "Cc\0Alexander Graf <agraf@suse.de>" Bhushan Bharat-R65777 <R65777@freescale.com> @@ -39,4 +39,4 @@ "\n" -Scott -1df115325fed9712fd73c67217ecf7c18f14d3d9d52a21ae8e875a16659201a2 +39ae9c723ca1a22177c25b2028d16ae2206441b9f2a4b86080bfca541aa96378
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.