120 		 * limitations on hot-add, the guest can specify
336  * Hot add request message. Message sent from the host to the guest.
338  * mem_range: Memory range to hot add.
348  * Hot add response message.
349  * This message is sent by the guest to report the status of a hot add request.
351  * assume all further hot add requests will fail, since this indicates that
354  * Hot adds may also fail due to low resources; in this case, the guest must
355  * not complete this message until the hot add can succeed, and the host must
356  * not send a new hot add request until the response is sent.
357  * If VSC fails to hot add memory DYNMEM_NUMBER_OF_UNSUCCESSFUL_HOTADD_ATTEMPTS
361  * page_count: number of pages that were successfully hot added.
412  * State to manage hot adding memory into the guest.
414  * that the host has asked us to hot add. The range
416  * currently hot added. We hot add in chunks equal to the
520 	 * State to execute the "hot-add" operation.
525 	 * This state tracks if the host has specified a hot-add
531 	 * State to synchronize hot-add.
535 	 * This thread handles hot-add
549 	 * A list of hot-add regions.
739 				 * precludes hot adding memory. Stop all further  in hv_mem_hot_add()
740 				 * memory hot-add.  in hv_mem_hot_add()
792 		 * "hot add block", move on.  in pfn_covered()
817 		 * If the current hot add-request extends beyond  in pfn_covered()
844 	pr_debug("Hot adding %lu pages starting at pfn 0x%lx.\n", pg_count,  in handle_pg_range()
851 		 * "hot add block", move on.  in handle_pg_range()
861 			 * in an already hot added region. Bring  in handle_pg_range()
885 			 * We have some residual hot add range  in handle_pg_range()
886 			 * that needs to be hot added; hot add  in handle_pg_range()
887 			 * it now. Hot add a multiple of  in handle_pg_range()
934 	 * If the host has specified a hot-add range; deal with it first.  in process_hot_add()
988 		 * The host has not specified the hot-add region.  in hot_add_req()
989 		 * Based on the hot-add page range being specified,  in hot_add_req()
990 		 * compute a hot-add region that can cover the pages  in hot_add_req()
991 		 * that need to be hot-added while ensuring the alignment  in hot_add_req()
992 		 * and size requirements of Linux as it relates to hot-add.  in hot_add_req()
1008 	 * 1. If all or some pages hot-added: Guest should return success.  in hot_add_req()
1010 	 * 2. If no pages could be hot-added:  in hot_add_req()
1013 	 * will not attempt any further hot-add operations. This  in hot_add_req()
1018 	 * hot-add operation after some delay.  in hot_add_req()
1029 			pr_err("Memory hot add failed\n");  in hot_add_req()
1031 			pr_info("Ignore hot-add request!\n");  in hot_add_req()
1530 				pr_warn("Currently hot-adding\n");  in balloon_onchannelcallback()
1535 				 * This is a normal hot-add request specifying  in balloon_onchannelcallback()
1536 				 * hot-add memory.  in balloon_onchannelcallback()
1544 				 * Host is specifying that we first hot-add  in balloon_onchannelcallback()
1698 	 * Disable hot add on ARM64, because we currently rely on  in hot_add_enabled()
1699 	 * memory_add_physaddr_to_nid() to get a node id of a hot add range,  in hot_add_enabled()
1705 		pr_info("Memory hot add disabled on ARM64\n");  in hot_add_enabled()
1781 	 * to fail the host's hot-add and balloon up/down requests, if any.  in balloon_connect_vsp()
1787 	 * Specify our alignment requirements for memory hot-add. The value is  in balloon_connect_vsp()
1877 			sname = "Hot Add";  in hv_balloon_debug_show()
1944 	 * Hot-add must operate in chunks that are of size equal to the  in balloon_probe()
1955 	 * hot add requests from Hyper-V, and the chunk size is used only to  in balloon_probe()