From: Oleksandr Tyshchenko <oleksandr_tyshche...@epam.com>

If memremap_pages() succeeds the range is guaranteed to have proper page
table, there is no need for an additional virt_addr_valid() check.

Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshche...@epam.com>
---
Changes RFC -> V2:
   - new patch, instead of
     "[RFC PATCH 1/2] arm64: mm: Make virt_addr_valid to check for pfn_valid 
again"
---
 drivers/xen/unpopulated-alloc.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/xen/unpopulated-alloc.c b/drivers/xen/unpopulated-alloc.c
index 87e6b7d..a03dc5b 100644
--- a/drivers/xen/unpopulated-alloc.c
+++ b/drivers/xen/unpopulated-alloc.c
@@ -85,7 +85,6 @@ static int fill_list(unsigned int nr_pages)
        for (i = 0; i < alloc_pages; i++) {
                struct page *pg = virt_to_page(vaddr + PAGE_SIZE * i);
 
-               BUG_ON(!virt_addr_valid(vaddr + PAGE_SIZE * i));
                pg->zone_device_data = page_list;
                page_list = pg;
                list_count++;
-- 
2.7.4


Reply via email to