sparc64: DAX request to mmap non 4MB memory should fail with a debug print

Orabug:25852910

When the dax flow control is disabled, dax_alloc_mem(...) only allows 4MB
allocation in the driver. Any other requests are reported as an error
with an error print to the kernel log. We now have a dax subpage
allocator in libdax which gets triggered when the driver reports the
above said failure. In other words it is a normal use case for the driver
to report this. So make this a debug print.

Reviewed-by: Shannon Nelson <shannon.nelson@oracle.com>
Signed-off-by: Sanath Kumar <sanath.s.kumar@oracle.com>
Signed-off-by: Allen Pais <allen.pais@oracle.com>

diff --git a/arch/sparc/dax/dax_mm.c b/arch/sparc/dax/dax_mm.c
index 5d451699690e0ad2527b8edaae3e5a40dba398a1..fd3bd5ace70d7a88efcac0355636fb4100bbc617 100644 (file)
--- a/arch/sparc/dax/dax_mm.c
+++ b/arch/sparc/dax/dax_mm.c
@@ -43,8 +43,8 @@ static int dax_alloc_ram(struct file *filp, struct vm_area_struct *vma)
        }
 
        if (dax_no_flow_ctl && len != DAX_SYN_LARGE_PAGE_SIZE) {
-               dax_err("unsupported length 0x%lx != 0x%lx virtual page size",
-                       len, DAX_SYN_LARGE_PAGE_SIZE);
+               dax_map_dbg("unsupported length 0x%lx != 0x%lx virtual page size",
+                           len, DAX_SYN_LARGE_PAGE_SIZE);
                goto done;
        }