Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758349AbcLOPQ6 (ORCPT ); Thu, 15 Dec 2016 10:16:58 -0500 Received: from mo4-p00-ob.smtp.rzone.de ([81.169.146.160]:32143 "EHLO mo4-p00-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755300AbcLOPQ5 (ORCPT ); Thu, 15 Dec 2016 10:16:57 -0500 X-RZG-AUTH: :P2EQZWCpfu+qG7CngxMFH1J+yackYocTD1iAi8x+OWi5z/J1IL7CYRxLEwpkY2XtLzyRUcY= X-RZG-CLASS-ID: mo00 Date: Thu, 15 Dec 2016 16:16:46 +0100 From: Olaf Hering To: Vitaly Kuznetsov 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: <20161215151645.GE6336@aepfle.de> References: <20161207085110.GC1618@aepfle.de> <87r3594hef.fsf@vitty.brq.redhat.com> <20161215103402.GA6336@aepfle.de> <87mvfx4g4y.fsf@vitty.brq.redhat.com> <20161215125139.GC6336@aepfle.de> <87bmwd490b.fsf@vitty.brq.redhat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="G6nVm6DDWH/FONJq" Content-Disposition: inline In-Reply-To: <87bmwd490b.fsf@vitty.brq.redhat.com> User-Agent: Mutt/1.7.2 (6888) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 880 Lines: 29 --G6nVm6DDWH/FONJq Content-Type: text/plain; charset=utf-8 Content-Disposition: inline On Thu, Dec 15, Vitaly Kuznetsov wrote: > -> K. Y., but these words were written before I implemented > vmbus_wait_for_unload(), to me they just explain how we read messages. Another question for KY: In my testing, while busy-looping in vmbus_wait_for_unload, I see a few "message_type==1, hdr->msgtype==2" in the hv_context.synic_message_page of the cpu which will deliver CHANNELMSG_UNLOAD_RESPONSE. These values are not listed in their enum lists. Any idea what these values mean? Olaf --G6nVm6DDWH/FONJq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQSkRyP6Rn//f03pRUBdQqD6ppg2fgUCWFKz2gAKCRBdQqD6ppg2 fuodAKDWQspxP5xuLMAzcuXhHrN3NcsnYACbB9w3KY4h3EvElCxsE3Vrs1OyIic= =d0qu -----END PGP SIGNATURE----- --G6nVm6DDWH/FONJq--