From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 15/16] kvm: x86: set kdump virt_disable function on initialization Date: Thu, 06 Nov 2008 11:44:38 +0200 Message-ID: <4912BC86.8050607@redhat.com> References: <1225810364-8990-1-git-send-email-ehabkost@redhat.com> <1225810364-8990-16-git-send-email-ehabkost@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Andrew Morton , Eduardo Habkost , kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "Rafael J. Wysocki" , Haren Myneni , Simon Horman , Ingo Molnar , Andrey Borzenkov , mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, Vivek Goyal To: "Eric W. Biederman" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kexec-bounces-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org Errors-To: kexec-bounces+glkk-kexec=m.gmane.org-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: kvm.vger.kernel.org Eric W. Biederman wrote: >> >> + r = set_virt_disable_func(crash_hardware_disable); >> > > Can we make this say: > set_virt_disable_func(kvm_x86_ops->crash_hardware_disable); > > So we can avoid going through 2 levels of function pointers? > I find that a little scary in code that might be running > at the edge of stack overflow. > Actually, with scheduling disabled we can overflow the stack as much as we like. It will reduce the quality of the dump, but everything ought to work. -- error compiling committee.c: too many arguments to function