From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: KVM host kernel hang
Date: Wed, 07 Jan 2009 15:12:06 +0200
Message-ID: <4964AA26.2070406@redhat.com>
References: <4964693A.3010107@suse.de> <496480B8.3070608@redhat.com> <6504B602-6B3F-4095-A86D-9246423015E0@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Joerg Roedel <joerg.roedel@amd.com>
To: Alexander Graf <agraf@suse.de>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx2.redhat.com ([66.187.237.31]:41258 "EHLO mx2.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751836AbZAGNML (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 7 Jan 2009 08:12:11 -0500
In-Reply-To: <6504B602-6B3F-4095-A86D-9246423015E0@suse.de>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Alexander Graf wrote:
>
> I have CONFIG_LOCKDEP_SUPPORT=y. How do I make it detect that it's 
> actually locking itself up?
> Btw: The issue seems to be easily reproducible :-)

Perhaps CONFIG_PROVE_LOCKING and CONFIG_LOCKDEP.  _SUPPORT just 
indicates the arch can do it if you want, IIUC.

-- 
error compiling committee.c: too many arguments to function