All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <55A3A796.4050108@plexistor.com>

diff --git a/a/1.txt b/N1/1.txt
index 2c9e33f..857f0a4 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -26,48 +26,3 @@ destination is the cow-to page so surly it is not yet mapped to user-space
 mapping.
 
 the from is pmem which is just there.
-
-From what I understand copy_user_page means:
-    On these ARCHs that each user-mapping has its own VM cache, please invalidate
-    the other VM caches.
-Like on arm64 (arch/arm64/mm/copypage.c):
-	copy_page(kto, kfrom);
-	__flush_dcache_area(kto, PAGE_SIZE);
-
-So what I do not understand is why copy_user_page does not have a default
-implementation for those ARCHs that don't override it.
-
-But again I think the above copy_user_page use is not at all needed.
-
-And of course what do I know?
-
-Thanks
-Boaz
-
-> We already have a list of architectures that are known to be incompatible,
-> but the list is missing ARC and SH at the moment. Further, blackfin and
-> c6x also lack support for this function, but are already excluded because
-> they do not support MMU-based kernels.
-> 
-> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
-> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
-> [Geert: s/SH/SUPERH/, as reported by Paul Bolle <pebolle@tiscali.nl>]
-> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
-> ---
->  fs/Kconfig | 2 +-
->  1 file changed, 1 insertion(+), 1 deletion(-)
-> 
-> diff --git a/fs/Kconfig b/fs/Kconfig
-> index 011f43365d7b1e53..53326a50a3ce3830 100644
-> --- a/fs/Kconfig
-> +++ b/fs/Kconfig
-> @@ -37,7 +37,7 @@ source "fs/f2fs/Kconfig"
->  config FS_DAX
->  	bool "Direct Access (DAX) support"
->  	depends on MMU
-> -	depends on !(ARM || MIPS || SPARC)
-> +	depends on !(ARC || ARM || MIPS || SPARC || SUPERH)
->  	help
->  	  Direct Access (DAX) can be used on memory-backed block devices.
->  	  If the block device supports DAX and the filesystem supports DAX,
->
diff --git a/a/content_digest b/N1/content_digest
index e5a3079..752aba5 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -39,51 +39,6 @@
  "destination is the cow-to page so surly it is not yet mapped to user-space\n"
  "mapping.\n"
  "\n"
- "the from is pmem which is just there.\n"
- "\n"
- "From what I understand copy_user_page means:\n"
- "    On these ARCHs that each user-mapping has its own VM cache, please invalidate\n"
- "    the other VM caches.\n"
- "Like on arm64 (arch/arm64/mm/copypage.c):\n"
- "\tcopy_page(kto, kfrom);\n"
- "\t__flush_dcache_area(kto, PAGE_SIZE);\n"
- "\n"
- "So what I do not understand is why copy_user_page does not have a default\n"
- "implementation for those ARCHs that don't override it.\n"
- "\n"
- "But again I think the above copy_user_page use is not at all needed.\n"
- "\n"
- "And of course what do I know?\n"
- "\n"
- "Thanks\n"
- "Boaz\n"
- "\n"
- "> We already have a list of architectures that are known to be incompatible,\n"
- "> but the list is missing ARC and SH at the moment. Further, blackfin and\n"
- "> c6x also lack support for this function, but are already excluded because\n"
- "> they do not support MMU-based kernels.\n"
- "> \n"
- "> Signed-off-by: Arnd Bergmann <arnd@arndb.de>\n"
- "> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>\n"
- "> [Geert: s/SH/SUPERH/, as reported by Paul Bolle <pebolle@tiscali.nl>]\n"
- "> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>\n"
- "> ---\n"
- ">  fs/Kconfig | 2 +-\n"
- ">  1 file changed, 1 insertion(+), 1 deletion(-)\n"
- "> \n"
- "> diff --git a/fs/Kconfig b/fs/Kconfig\n"
- "> index 011f43365d7b1e53..53326a50a3ce3830 100644\n"
- "> --- a/fs/Kconfig\n"
- "> +++ b/fs/Kconfig\n"
- "> @@ -37,7 +37,7 @@ source \"fs/f2fs/Kconfig\"\n"
- ">  config FS_DAX\n"
- ">  \tbool \"Direct Access (DAX) support\"\n"
- ">  \tdepends on MMU\n"
- "> -\tdepends on !(ARM || MIPS || SPARC)\n"
- "> +\tdepends on !(ARC || ARM || MIPS || SPARC || SUPERH)\n"
- ">  \thelp\n"
- ">  \t  Direct Access (DAX) can be used on memory-backed block devices.\n"
- ">  \t  If the block device supports DAX and the filesystem supports DAX,\n"
- >
+ the from is pmem which is just there.
 
-46007a5959b512063d12b37098ce63d696b2f6ad14884888ef5b5ea1890bfcf3
+6b39e20cd4a1c2026ec1483c2f102c9b9296280103684793c802c33e7f189c63

diff --git a/a/1.txt b/N2/1.txt
index 2c9e33f..0eeced1 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -27,7 +27,7 @@ mapping.
 
 the from is pmem which is just there.
 
-From what I understand copy_user_page means:
+>From what I understand copy_user_page means:
     On these ARCHs that each user-mapping has its own VM cache, please invalidate
     the other VM caches.
 Like on arm64 (arch/arm64/mm/copypage.c):
diff --git a/a/content_digest b/N2/content_digest
index e5a3079..ede5ee5 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -41,7 +41,7 @@
  "\n"
  "the from is pmem which is just there.\n"
  "\n"
- "From what I understand copy_user_page means:\n"
+ ">From what I understand copy_user_page means:\n"
  "    On these ARCHs that each user-mapping has its own VM cache, please invalidate\n"
  "    the other VM caches.\n"
  "Like on arm64 (arch/arm64/mm/copypage.c):\n"
@@ -86,4 +86,4 @@
  ">  \t  If the block device supports DAX and the filesystem supports DAX,\n"
  >
 
-46007a5959b512063d12b37098ce63d696b2f6ad14884888ef5b5ea1890bfcf3
+c954266e3555bdf7f4abbbea698f973e1b9a91a1a2183cc87255c6e091ab4438

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.