From: Long Li <lon...@microsoft.com>

To prepare for removal of hv_alloc_* and hv_free* functions, use
kzalloc/kfree directly for panic reporting page.

Signed-off-by: Long Li <lon...@microsoft.com>
---
 drivers/hv/hv_common.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/hv/hv_common.c b/drivers/hv/hv_common.c
index a7d7494feaca..a5a6250b1a12 100644
--- a/drivers/hv/hv_common.c
+++ b/drivers/hv/hv_common.c
@@ -272,7 +272,7 @@ static void hv_kmsg_dump_unregister(void)
        atomic_notifier_chain_unregister(&panic_notifier_list,
                                         &hyperv_panic_report_block);
 
-       hv_free_hyperv_page(hv_panic_page);
+       kfree(hv_panic_page);
        hv_panic_page = NULL;
 }
 
@@ -280,7 +280,7 @@ static void hv_kmsg_dump_register(void)
 {
        int ret;
 
-       hv_panic_page = hv_alloc_hyperv_zeroed_page();
+       hv_panic_page = kzalloc(HV_HYP_PAGE_SIZE, GFP_KERNEL);
        if (!hv_panic_page) {
                pr_err("Hyper-V: panic message page memory allocation 
failed\n");
                return;
@@ -289,7 +289,7 @@ static void hv_kmsg_dump_register(void)
        ret = kmsg_dump_register(&hv_kmsg_dumper);
        if (ret) {
                pr_err("Hyper-V: kmsg dump register error 0x%x\n", ret);
-               hv_free_hyperv_page(hv_panic_page);
+               kfree(hv_panic_page);
                hv_panic_page = NULL;
        }
 }
-- 
2.34.1


Reply via email to