From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx2.redhat.com ([66.187.237.31]) by bombadil.infradead.org with esmtp (Exim 4.68 #1 (Red Hat Linux)) id 1Ky1V9-0005kJ-IE for kexec@lists.infradead.org; Thu, 06 Nov 2008 09:50:07 +0000 Message-ID: <4912BDC5.3000508@redhat.com> Date: Thu, 06 Nov 2008 11:49:57 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [PATCH 00/14] x86: disable virt on kdump and emergency_restart References: <1225810364-8990-1-git-send-email-ehabkost@redhat.com> <49107E2C.8090803@redhat.com> <20081105163306.GA30018@elte.hu> In-Reply-To: <20081105163306.GA30018@elte.hu> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: kexec-bounces@lists.infradead.org Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Ingo Molnar Cc: Andrew Morton , Eduardo Habkost , kvm@vger.kernel.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, "Rafael J. Wysocki" , Haren Myneni , Simon Horman , "Eric W. Biederman" , Andrey Borzenkov , mingo@redhat.com, Vivek Goyal Ingo Molnar wrote: > general ack for the x86 bits, but i'm not sure whether we should be > pushing this upstream so late in the cycle. If we do it in the next > cycle then it's best we do it in the x86 tree, the KVM impact seems > much smaller than the general x86 impact. > It certainly doesn't fall under the recent regression rule, and there's a simple workaround (rmmod -r kvm) so I agree it's best to defer for the next cycle. -- error compiling committee.c: too many arguments to function _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec