From: KY Srinivasan <kys@microsoft.com>
To: Olaf Hering <olaf@aepfle.de>,
"vkuznets@redhat.com" <vkuznets@redhat.com>
Cc: "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 16:10:46 +0000 [thread overview]
Message-ID: <DM5PR03MB2490056E887D6B844283BB98A0850@DM5PR03MB2490.namprd03.prod.outlook.com> (raw)
In-Reply-To: <7CEFFEF3-911A-4D37-AC37-DF8C6A3395BF@aepfle.de>
> -----Original Message-----
> From: Olaf Hering [mailto:olaf@aepfle.de]
> Sent: Wednesday, December 7, 2016 7:47 AM
> To: KY Srinivasan <kys@microsoft.com>; vkuznets@redhat.com
> Cc: gregkh@linuxfoundation.org; linux-kernel@vger.kernel.org;
> devel@linuxdriverproject.org
> Subject: RE: move hyperv CHANNELMSG_UNLOAD from crashed kernel to
> kdump kernel
>
> Am 7. Dezember 2016 16:04:29 MEZ, schrieb KY Srinivasan
> <kys@microsoft.com>:
>
> >Yes; I had played with this approach a while ago. The issue is that the
> >host knows about a
> >bunch of in memory state that will be different in the kexec kernel.
> >For instance if we did all
> >the cleanup as part of the boot sequence, we will need access to all
> >the interrupt/messaging
> >infrastructure that was set up in the previous kernel.
>
>
> Where is that stored? Perhaps it should be put into one place, so that the
> new kernel can find and use it.
All the state required to handle interrupts is needed as well as the state needed
to issue unload. Look at vmbus_isr() for the needed interrupt handling state. The entire
code path from the isr routine will have to be executed. Is there a mechanism for stashing away state
that can be retrieved in the context of the execed kernel.
K. Y
>
> Olaf
next prev parent reply other threads:[~2016-12-07 16:10 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 [this message]
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=DM5PR03MB2490056E887D6B844283BB98A0850@DM5PR03MB2490.namprd03.prod.outlook.com \
--to=kys@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--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).