Date: Thu, 15 Dec 2016 11:36:09 +0100
From: Olaf Hering <olaf@aepfle.de>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: kys@microsoft.com, gregkh@linuxfoundation.org,
        linux-kernel@vger.kernel.org, devel@linuxdriverproject.org
Subject: Re: move hyperv CHANNELMSG_UNLOAD from crashed kernel to kdump kernel
Message-ID: <20161215103609.GB6336@aepfle.de>
References: <20161207085110.GC1618@aepfle.de>
 <87r3594hef.fsf@vitty.brq.redhat.com>
 <20161215103402.GA6336@aepfle.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="/NkBOFFp2J2Af1nK"
Content-Disposition: inline
In-Reply-To: <20161215103402.GA6336@aepfle.de>
User-Agent: Mutt/1.7.2 (6888)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1162
Lines: 37


--/NkBOFFp2J2Af1nK
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Dec 15, Olaf Hering wrote:

> On Thu, Dec 15, Vitaly Kuznetsov wrote:
>=20
> > I see a number of minor but at least one major issue against such move:
> > At least for some Hyper-V versions (2012R2 for example)
> > CHANNELMSG_UNLOAD_RESPONSE is delivered to the CPU which initially sent=
=20
> > CHANNELMSG_REQUESTOFFERS and on kdump we may not have this CPU up as
> > we usually do kdump with nr_cpus=3D1 (and on the CPU which crashed).=20
>=20
> Since the kdump or kexec kernel will send the unload during boot I would
> expect the response to arrive where it was sent, independent from the
> number of cpus.

Wait, I just noticed that "REQUESTOFFERS" now. That might be a reason
why my suggestion will not work.

Olaf

--/NkBOFFp2J2Af1nK
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQSkRyP6Rn//f03pRUBdQqD6ppg2fgUCWFJyGQAKCRBdQqD6ppg2
fm8cAKDb/h96DOJqZ2iWEVrMN4FrMOdy4ACg7b1sqpPf73N9cUtPz36DZivjxPY=
=kNgp
-----END PGP SIGNATURE-----

--/NkBOFFp2J2Af1nK--