From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757687AbcLONvZ (ORCPT ); Thu, 15 Dec 2016 08:51:25 -0500 Received: from mo4-p00-ob.smtp.rzone.de ([81.169.146.216]:26883 "EHLO mo4-p00-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752673AbcLONvY (ORCPT ); Thu, 15 Dec 2016 08:51:24 -0500 X-RZG-AUTH: :P2EQZWCpfu+qG7CngxMFH1J+yackYocTD1iAi8x+OWi5z/J1IL7CYRxLEwpkY2XtLzyRUcY= X-RZG-CLASS-ID: mo00 Date: Thu, 15 Dec 2016 14:51:12 +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: <20161215135111.GD6336@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="XvKFcGCOAo53UbWW" 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 --XvKFcGCOAo53UbWW Content-Type: text/plain; charset=utf-8 Content-Disposition: inline On Thu, Dec 15, Vitaly Kuznetsov wrote: > vmbus_wait_for_unload() may be receiving a message (not necessarily the > CHANNELMSG_UNLOAD_RESPONSE, we may see some other message) on the same > CPU it runs and in this case wrmsrl() makes sense. In other cases it > does nothing (neither good nor bad). If that other cpu has interrupts disabled it may not process a pending msg (the response may be stuck in the host queue?), and the loop can not kick the other cpus queue if a wrmsrl is just valid for the current cpu. If thats true, the response will not arrive in the loop. Olaf --XvKFcGCOAo53UbWW Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQSkRyP6Rn//f03pRUBdQqD6ppg2fgUCWFKfywAKCRBdQqD6ppg2 fukLAKCVuWwUNNsT3joxYZf9/R4JpYYauQCgmzXeF2qKtYSwFX7rUOxHGcZwkOw= =SzYI -----END PGP SIGNATURE----- --XvKFcGCOAo53UbWW--