diff options
Diffstat (limited to '0028-x86-pv-Track-and-flush-non-coherent-mappings-of-RAM.patch')
| -rw-r--r-- | 0028-x86-pv-Track-and-flush-non-coherent-mappings-of-RAM.patch | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/0028-x86-pv-Track-and-flush-non-coherent-mappings-of-RAM.patch b/0028-x86-pv-Track-and-flush-non-coherent-mappings-of-RAM.patch index 66cd741..af60348 100644 --- a/0028-x86-pv-Track-and-flush-non-coherent-mappings-of-RAM.patch +++ b/0028-x86-pv-Track-and-flush-non-coherent-mappings-of-RAM.patch @@ -1,7 +1,7 @@ From dc020d8d1ba420e2dd0e7a40f5045db897f3c4f4 Mon Sep 17 00:00:00 2001 From: Andrew Cooper <andrew.cooper3@citrix.com> Date: Thu, 9 Jun 2022 15:29:38 +0200 -Subject: [PATCH 28/32] x86/pv: Track and flush non-coherent mappings of RAM +Subject: [PATCH 28/51] x86/pv: Track and flush non-coherent mappings of RAM There are legitimate uses of WC mappings of RAM, e.g. for DMA buffers with devices that make non-coherent writes. The Linux sound subsystem makes |