From 21b35ab00badd4745e064a39e3ce0015139db973 Mon Sep 17 00:00:00 2001 From: Sanath Kumar Date: Thu, 6 Apr 2017 15:27:34 -0500 Subject: [PATCH] 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 Signed-off-by: Sanath Kumar Signed-off-by: Allen Pais --- arch/sparc/dax/dax_mm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/sparc/dax/dax_mm.c b/arch/sparc/dax/dax_mm.c index 5d451699690e..fd3bd5ace70d 100644 --- 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; } -- 2.50.1