From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932239AbcARRSq (ORCPT ); Mon, 18 Jan 2016 12:18:46 -0500 Received: from mx1.redhat.com ([209.132.183.28]:38220 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932191AbcARRSm (ORCPT ); Mon, 18 Jan 2016 12:18:42 -0500 From: Vitaly Kuznetsov To: "K. Y. Srinivasan" Cc: Haiyang Zhang , devel@linuxdriverproject.org, linux-kernel@vger.kernel.org Subject: [PATCH 0/3] Drivers: hv: fix kdump (again) and more Date: Mon, 18 Jan 2016 18:18:36 +0100 Message-Id: <1453137519-20304-1-git-send-email-vkuznets@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Kdump on crash is reportedly broken for Hyper-V guests and I was able to find two reasons: 1) Inability to boot with nr_cpus=1 (PATCH 1) 2) Sleeping in interrupt context on crash (PATCH 2 and 3) Vitaly Kuznetsov (3): Drivers: hv: vmbus: avoid infinite loop in init_vp_index() Drivers: hv: vmbus: avoid scheduling in interrupt context in vmbus_initiate_unload() Drivers: hv: vmbus: don't manipulate with clocksources on crash drivers/hv/channel_mgmt.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++- drivers/hv/hv.c | 10 +++++++-- 2 files changed, 62 insertions(+), 3 deletions(-) -- 2.5.0