[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1435226286-24842-1-git-send-email-vkuznets@redhat.com>
Date: Thu, 25 Jun 2015 11:58:01 +0200
From: Vitaly Kuznetsov <vkuznets@...hat.com>
To: devel@...uxdriverproject.org
Cc: linux-kernel@...r.kernel.org, kexec@...ts.infradead.org,
Eric Biederman <ebiederm@...ssion.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Haiyang Zhang <haiyangz@...rosoft.com>,
"K. Y. Srinivasan" <kys@...rosoft.com>,
Olaf Hering <olaf@...fle.de>,
Greg KH <gregkh@...uxfoundation.org>
Subject: [PATCH v3 0/5] Drivers: hv: add kexec support (and fix kdump)
Changes since v2:
- Get rid of #ifdefs in mshyperv.c [Olaf Hering, Greg KH]
PATCH 2/5 is added to support the change.
- Fix (also broken) kdump [K. Y. Srinivasan]
PATCH 5/5 added.
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 3/5] for the detailed description). Kdump also requires some
mandatory cleanup [PATCH 5/5]
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 (5):
Drivers: hv: vmbus: remove hv_synic_free_cpu() call from
hv_synic_cleanup()
kexec: define kexec_in_progress in !CONFIG_KEXEC case
Drivers: hv: vmbus: add special kexec handler
Drivers: hv: don't do hypercalls when hypercall_page is NULL
Drivers: hv: vmbus: add special crash handler
arch/x86/include/asm/mshyperv.h | 4 ++++
arch/x86/kernel/cpu/mshyperv.c | 46 +++++++++++++++++++++++++++++++++++++++++
drivers/hv/hv.c | 15 +++++++-------
drivers/hv/vmbus_drv.c | 29 ++++++++++++++++++++++++++
include/linux/kexec.h | 1 +
5 files changed, 88 insertions(+), 7 deletions(-)
--
2.4.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists