From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933310AbbFCPNP (ORCPT ); Wed, 3 Jun 2015 11:13:15 -0400 Received: from mx1.redhat.com ([209.132.183.28]:50058 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964837AbbFCPNJ (ORCPT ); Wed, 3 Jun 2015 11:13:09 -0400 From: Vitaly Kuznetsov To: devel@linuxdriverproject.org Cc: "K. Y. Srinivasan" , Haiyang Zhang , linux-kernel@vger.kernel.org, Dexuan Cui , Ingo Molnar , "H. Peter Anvin" , Thomas Gleixner , x86@kernel.org Subject: [PATCH v2 0/3] Drivers: hv: add kexec support Date: Wed, 3 Jun 2015 17:13:02 +0200 Message-Id: <1433344385-26944-1-git-send-email-vkuznets@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Changes since v1: - rebased on top of current Greg's char-misc-next tree. To make general-purpose kexec (not just kdump) possible for Hyper-V guests we need to perform some additional cleanup before starting new kernel (see [PATCH 2/3] for the detailed description). Know limitations: kexec with balloned out memory is not possible as the newly loaded kernel doesn't know about this memory and there is no way to ask the host to bring all the memory back on cleanup (or at least I'm not aware of such a way). Kexec with hotplugged memory leads to reboot (not exactly sure why). Vitaly Kuznetsov (3): Drivers: hv: vmbus: remove hv_synic_free_cpu() call from hv_synic_cleanup() Drivers: hv: vmbus: add special kexec handler Drivers: hv: don't do hypercalls when hypercall_page is NULL arch/x86/include/asm/mshyperv.h | 2 ++ arch/x86/kernel/cpu/mshyperv.c | 30 ++++++++++++++++++++++++++++++ drivers/hv/hv.c | 15 ++++++++------- drivers/hv/vmbus_drv.c | 15 +++++++++++++++ 4 files changed, 55 insertions(+), 7 deletions(-) -- 1.9.3