From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752635AbcLGIvR (ORCPT ); Wed, 7 Dec 2016 03:51:17 -0500 Received: from mo4-p04-ob.smtp.rzone.de ([81.169.146.179]:17114 "EHLO mo4-p04-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751772AbcLGIvQ (ORCPT ); Wed, 7 Dec 2016 03:51:16 -0500 X-RZG-CLASS-ID: mo04 X-RZG-AUTH: :P2EQZWCpfu+qG7CngxMFH1J+zrwiavkK6tmQaLfoxNM57Q/BzQY4OEOycEc= Date: Wed, 7 Dec 2016 09:51:10 +0100 From: Olaf Hering 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 Message-ID: <20161207085110.GC1618@aepfle.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GPJrCs/72TxItFYR" Content-Disposition: inline User-Agent: Mutt/1.7.1 (6878) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --GPJrCs/72TxItFYR Content-Type: text/plain; charset=utf-8 Content-Disposition: inline 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 --GPJrCs/72TxItFYR Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQSkRyP6Rn//f03pRUBdQqD6ppg2fgUCWEfNeQAKCRBdQqD6ppg2 fqtkAJ92lBlWHA/8eB4QIXlOmb0GjDF41QCfUnBn4L+ploFNm0HaI6EfadpVrDA= =+NEw -----END PGP SIGNATURE----- --GPJrCs/72TxItFYR--