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, x86@kernel.org,
	"K. Y. Srinivasan" <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Stephen Hemminger <sthemmin@microsoft.com>
Subject: [PATCH 0/2] Drivers: hv: fix kexec/kdump after the recent changes
Date: Wed, 25 Jan 2017 14:17:53 +0100	[thread overview]
Message-ID: <20170125131755.21652-1-vkuznets@redhat.com> (raw)

'Restructure architecture specific code' series (now merged in char-misc)
introduced a regression wrt kexec/kdump. Hypercall and TSC pages setup was
moved out to the architecture specific code and the cleanup was dropped. We,
however, still need this cleanup: in kexec case the new kernel may try
using these pages as normal memory and will certainly crash. Restore the
minimal cleanup moving it to the architecture specific code.

Commit ids I mention in 'Fixes:' tags are from char-misc-next.

Vitaly Kuznetsov (2):
  Drivers: hv: restore hypervcall page cleanup before kexec
  Drivers: hv: restore TSC page cleanup before kexec

 arch/x86/hyperv/hv_init.c       | 20 ++++++++++++++++++++
 arch/x86/include/asm/mshyperv.h |  1 +
 drivers/hv/hv.c                 | 10 ----------
 drivers/hv/hyperv_vmbus.h       |  2 --
 drivers/hv/vmbus_drv.c          | 10 +++-------
 5 files changed, 24 insertions(+), 19 deletions(-)

-- 
2.9.3

             reply	other threads:[~2017-01-25 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 13:17 Vitaly Kuznetsov [this message]
2017-01-25 13:17 ` [PATCH 1/2] Drivers: hv: restore hypervcall page cleanup before kexec Vitaly Kuznetsov
2017-01-25 13:17 ` [PATCH 2/2] Drivers: hv: restore TSC " 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=20170125131755.21652-1-vkuznets@redhat.com \
    --to=vkuznets@redhat.com \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sthemmin@microsoft.com \
    --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®