From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>,
kvm <kvm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [kvm.git & 2.6.37-rc1] KVM deadlock with CONFIG_PREEMPT host
Date: Tue, 09 Nov 2010 12:38:19 +0200 [thread overview]
Message-ID: <4CD9249B.2090803@redhat.com> (raw)
In-Reply-To: <4CD7D0B2.80600@siemens.com>
On 11/08/2010 12:28 PM, Jan Kiszka wrote:
> Am 08.11.2010 10:18, Markus Trippelsdorf wrote:
> > On Mon, Nov 08, 2010 at 10:04:00AM +0100, Jan Kiszka wrote:
> >> Hi,
> >>
> >> I'm seeing lock-ups of the QEMU process on kvm.git as well as current
> >> upstream kernels. This is a backtrace of the hanging VCPU thread:
> >>
> >> [<ffffffff810a27bc>] __stop_cpus+0x184/0x1a7
> >> [<ffffffff810a286f>] try_stop_cpus+0x40/0x59
> >> [<ffffffff8103a30c>] synchronize_sched_expedited+0x84/0x9d
> >> [<ffffffff810715a3>] __synchronize_srcu+0x33/0x72
> >> [<ffffffff810715f7>] synchronize_srcu_expedited+0x15/0x17
> >> [<ffffffffa06602ae>] __kvm_set_memory_region+0x6a3/0x782 [kvm]
> >> [<ffffffffa06603c4>] kvm_set_memory_region+0x37/0x50 [kvm]
> >> [<ffffffffa0661c30>] kvm_vm_ioctl_set_memory_region+0x18/0x1a [kvm]
> >> [<ffffffffa0661e5f>] kvm_vm_ioctl+0x22d/0x3b1 [kvm]
> >> [<ffffffff81143c26>] do_vfs_ioctl+0x5a1/0x5e2
> >> [<ffffffff81143cbd>] sys_ioctl+0x56/0x79
> >> [<ffffffff81002df2>] system_call_fastpath+0x16/0x1b
> >> [<ffffffffffffffff>] 0xffffffffffffffff
> >>
> >> This issue disappears when disabling CONFIG_PREEMPT on the host.
> >> According to some rough bisecting, it was imported into kvm.git with
> >> merge 146d3bb06b. Given that RCU is involved, I also tried
> >> force-enabling non-preemptible CONFIG_TREE_RCU again, but that made no
> >> difference as long as PREEMPT is on.
> >>
> >> Can anyone confirm this or does someone have an idea what goes wrong? Of
> >> course, .config will be provided if required.
> >
> > This patch should help (,it fixes the problem in my case):
> > http://article.gmane.org/gmane.linux.kernel/1058018
>
> Yeah, that works here as well.
>
> Would be a nice-to-have in kvm.git until it's pull via the next upstream
> merge. At least for me this bug triggers at every VM boot.
>
I just did so. Testing with CONFIG_PREEMPT is important.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-11-09 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 9:04 [kvm.git & 2.6.37-rc1] KVM deadlock with CONFIG_PREEMPT host Jan Kiszka
2010-11-08 9:18 ` Markus Trippelsdorf
2010-11-08 10:28 ` Jan Kiszka
2010-11-09 10:38 ` Avi Kivity [this message]
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=4CD9249B.2090803@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=mtosatti@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
/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