diff for duplicates of <20180717131952.GF13582@lst.de> diff --git a/a/1.txt b/N1/1.txt index 436e975..9fff475 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -12,9 +12,11 @@ On Sun, Jul 15, 2018 at 12:29:37PM -0400, John David Anglin wrote: >> and so on. >> >> So, there is definitively some cache-flush missing in this patchset. -> Possibly, the code should use flush_kernel_vmap_range() as it purges the +> Possibly, the code should use flush_kernel_vmap_range() as it purges the = + > TLB entries used -> for the cache flush. Some of the routines in pci-dma.c currently use it. +> for the cache flush.=A0 Some of the routines in pci-dma.c currently use i= +t. That might be worth a try and is already discussed in my description. diff --git a/a/content_digest b/N1/content_digest index a6bd02e..10d46b6 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -28,13 +28,15 @@ ">> and so on.\n" ">>\n" ">> So, there is definitively some cache-flush missing in this patchset.\n" - "> Possibly, the code should use flush_kernel_vmap_range() as it purges the \n" + "> Possibly, the code should use flush_kernel_vmap_range() as it purges the =\n" + "\n" "> TLB entries used\n" - "> for the cache flush.\302\240 Some of the routines in pci-dma.c currently use it.\n" + "> for the cache flush.=A0 Some of the routines in pci-dma.c currently use i=\n" + "t.\n" "\n" "That might be worth a try and is already discussed in my description.\n" "\n" "Also it might be good to check that the last patch really is the culprit,\n" I'm pretty certain it is, but a double check never hurts. -96783c0f2ec4347b3787bf4f1a3a5166672116946d266acac8a55ac636153dcd +37a8284dd98de6712acb67bf93e52f61fb82eda160d8ff3dda2ef0dd5cd7f355
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.