From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: KVM host kernel hang
Date: Wed, 07 Jan 2009 15:53:41 +0200 [thread overview]
Message-ID: <4964B3E5.7010400@redhat.com> (raw)
In-Reply-To: <4964B0F5.1030500@suse.de>
Alexander Graf wrote:
> Avi Kivity wrote:
>
>> 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.
>>
>
> I just added some debug #define's to show me where exactly things break.
>
>
> Jan 7 14:34:46 linux-dp8n kernel: 2149: Grabbing lock {
> Jan 7 14:34:46 linux-dp8n kernel: 1908: Grabbing lock {
>
> 2145 mmio:
> 2146 /*
> 2147 * Is this MMIO handled locally?
> 2148 */
> 2149 mutex_lock(&vcpu->kvm->lock);
> 2150 mmio_dev = vcpu_find_mmio_dev(vcpu, gpa, bytes, 0);
> 2151 if (mmio_dev) {
> 2152 kvm_iodevice_read(mmio_dev, gpa, bytes, val);
> 2153 mutex_unlock(&vcpu->kvm->lock);
> 2154 return X86EMUL_CONTINUE;
> 2155 }
> 2156 mutex_unlock(&vcpu->kvm->lock);
>
>
The lock was lost here. But how?
> 1901 case KVM_IRQ_LINE: {
> 1902 struct kvm_irq_level irq_event;
> 1903
> 1904 r = -EFAULT;
> 1905 if (copy_from_user(&irq_event, argp, sizeof
> irq_event))
> 1906 goto out;
> 1907 if (irqchip_in_kernel(kvm)) {
> 1908 mutex_lock(&kvm->lock);
> 1909 kvm_set_irq(kvm,
> KVM_USERSPACE_IRQ_SOURCE_ID,
> 1910 irq_event.irq, irq_event.level);
> 1911 mutex_unlock(&kvm->lock);
> 1912 r = 0;
> 1913 }
> 1914 break;
> 1915 }
>
>
This is your hung iothread trying to inject an interrupt. It's waiting
for the lost lock.
I suggest enabling all the lock debug magic you can find in kconfig.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-01-07 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 8:35 KVM host kernel hang Alexander Graf
2009-01-07 10:15 ` Avi Kivity
2009-01-07 13:02 ` Alexander Graf
2009-01-07 13:12 ` Avi Kivity
2009-01-07 13:41 ` Alexander Graf
2009-01-07 13:53 ` Avi Kivity [this message]
2009-01-07 19:06 ` Alexander Graf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4964B3E5.7010400@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox