From: Olaf Hering <olaf@aepfle.de>
To: KY Srinivasan <kys@microsoft.com>
Cc: "vkuznets@redhat.com" <vkuznets@redhat.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: Re: move hyperv CHANNELMSG_UNLOAD from crashed kernel to kdump kernel
Date: Wed, 7 Dec 2016 17:39:53 +0100 [thread overview]
Message-ID: <20161207163953.GE1618@aepfle.de> (raw)
In-Reply-To: <DM5PR03MB2490DBBD4DA3FE3275898F3FA0850@DM5PR03MB2490.namprd03.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
On Wed, Dec 07, KY Srinivasan wrote:
> May be a better solution might be to have a new mechanism to indicate
> to the host that all state of the previous incarnation of the kernel
> needs to be cleaned up. This will be close to what we have on
> hardware.
That would be cool, but until this appears and until its deployed in
Azure and elsewhere I will likely lose the remaining hairs.
Olaf
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2016-12-07 16:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 8:51 move hyperv CHANNELMSG_UNLOAD from crashed kernel to kdump kernel Olaf Hering
2016-12-07 15:04 ` 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 [this message]
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=20161207163953.GE1618@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).