mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: devel@linuxdriverproject.org
Cc: linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
	Eric Biederman <ebiederm@xmission.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	"K. Y. Srinivasan" <kys@microsoft.com>,
	Olaf Hering <olaf@aepfle.de>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: [PATCH v3 0/5] Drivers: hv: add kexec support (and fix kdump)
Date: Thu, 25 Jun 2015 11:58:01 +0200	[thread overview]
Message-ID: <1435226286-24842-1-git-send-email-vkuznets@redhat.com> (raw)

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


             reply	other threads:[~2015-06-25  9:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25  9:58 Vitaly Kuznetsov [this message]
2015-06-25  9:58 ` [PATCH v3 1/5] Drivers: hv: vmbus: remove hv_synic_free_cpu() call from hv_synic_cleanup() Vitaly Kuznetsov
2015-06-25  9:58 ` [PATCH v3 2/5] kexec: define kexec_in_progress in !CONFIG_KEXEC case Vitaly Kuznetsov
2015-06-25  9:58 ` [PATCH v3 3/5] Drivers: hv: vmbus: add special kexec handler Vitaly Kuznetsov
2015-06-25  9:58 ` [PATCH v3 4/5] Drivers: hv: don't do hypercalls when hypercall_page is NULL Vitaly Kuznetsov
2015-06-25  9:58 ` [PATCH v3 5/5] Drivers: hv: vmbus: add special crash handler Vitaly Kuznetsov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1435226286-24842-1-git-send-email-vkuznets@redhat.com \
    --to=vkuznets@redhat.com \
    --cc=devel@linuxdriverproject.org \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=haiyangz@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=kexec@lists.infradead.org \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=olaf@aepfle.de \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®