Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755560AbYKDOzq (ORCPT ); Tue, 4 Nov 2008 09:55:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753903AbYKDOxp (ORCPT ); Tue, 4 Nov 2008 09:53:45 -0500 Received: from mx2.redhat.com ([66.187.237.31]:60551 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753579AbYKDOxm (ORCPT ); Tue, 4 Nov 2008 09:53:42 -0500 From: Eduardo Habkost To: Avi Kivity , Ingo Molnar Cc: "Eric W. Biederman" , Simon Horman , Andrew Morton , Vivek Goyal , Haren Myneni , Andrey Borzenkov , mingo@redhat.com, "Rafael J. Wysocki" , kexec@lists.infradead.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Eduardo Habkost Subject: [PATCH 00/14] x86: disable virt on kdump and emergency_restart Date: Tue, 4 Nov 2008 12:52:28 -0200 Message-Id: <1225810364-8990-1-git-send-email-ehabkost@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1043 Lines: 31 Hi, This is a new version of the series to disabling virtualization on kdump, now extended to do the same tricks on emergency_restart() if needed. This series is against linux-next-20081103. Patches 01-07 simply move the non-kdump-specific parts of nmi_shootdown_cpus() to reboot.c, so it can be used by emergency_restart(). They should be a no-op in relation to existing code. Patches 08 adds the virt_disable function registering interface, like the previous series. Patch 09 hooks emergency_virt_disable() into kdump crash_shutdown code. Patch 10 hooks emergency_virt_disable() into emergency_restart() using nmi_shootdown_cpus(). Patches 11-15 change KVM so that it registers a virt_disable function when loading. Finally, patch 16 restore the previous reboot=kbd default. -- Eduardo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/