linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: kys@microsoft.com, vkuznets@redhat.com
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	devel@linuxdriverproject.org
Subject: move hyperv CHANNELMSG_UNLOAD from crashed kernel to kdump kernel
Date: Wed, 7 Dec 2016 09:51:10 +0100	[thread overview]
Message-ID: <20161207085110.GC1618@aepfle.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 774 bytes --]

KY,

if a hyperv VM crashes alot of work must be done to prepare the
environment for the kdump kernel. This approach is different compared to
all the other VM types, or baremetal. Since the just crashed kernel is
per definition unreliable all that work should be done within the kdump
kernel because I think a reliable environment exists only there.

Was it ever considered to do the CHANNELMSG_UNLOAD /
CHANNELMSG_UNLOAD_RESPONSE work during boot, instead of doing it before
starting the kexec/kdump kernel?

What would it take to prepare the runtime environment during boot?
Does the newly booted kernel need any info from the previous kernel,
something that cant be determined during boot? If yes, how can such info
be passed from the old kernel to the new kernel?

Olaf

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

             reply	other threads:[~2016-12-07  8:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07  8:51 Olaf Hering [this message]
2016-12-07 15:04 ` move hyperv CHANNELMSG_UNLOAD from crashed kernel to kdump kernel KY Srinivasan
2016-12-07 15:46   ` Olaf Hering
2016-12-07 16:10     ` KY Srinivasan
2016-12-07 16:19       ` Olaf Hering
2016-12-07 16:24         ` KY Srinivasan
2016-12-07 16:39           ` Olaf Hering
2016-12-07 18:11             ` KY Srinivasan
2016-12-15 10:26 ` Vitaly Kuznetsov
2016-12-15 10:34   ` Olaf Hering
2016-12-15 10:36     ` Olaf Hering
2016-12-15 10:54       ` Vitaly Kuznetsov
2016-12-15 10:54     ` Vitaly Kuznetsov
2016-12-15 12:51       ` Olaf Hering
2016-12-15 13:28         ` Vitaly Kuznetsov
2016-12-15 13:51           ` Olaf Hering
2016-12-15 14:32             ` Vitaly Kuznetsov
2016-12-16  0:51               ` KY Srinivasan
2016-12-15 15:16           ` Olaf Hering

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=20161207085110.GC1618@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vkuznets@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).