From: Jan Kiszka <jan.kiszka@web.de>
To: kvm <kvm@vger.kernel.org>, kvmarm <kvmarm@lists.cs.columbia.edu>,
Marc Zyngier <marc.zyngier@arm.com>,
Christoffer Dall <christoffer.dall@linaro.org>
Subject: arm: warning at virt/kvm/arm/vgic.c:1468
Date: Sun, 08 Feb 2015 08:48:09 +0100 [thread overview]
Message-ID: <54D714B9.6090106@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]
Hi,
after fixing the VM_BUG_ON, my QEMU guest on the Jetson TK1 generally
refuses to boot. Once in a while it does, but quickly gets stuck again.
In one case I found this in the kernel log (never happened again so
far):
[ 762.022874] WARNING: CPU: 1 PID: 972 at ../arch/arm/kvm/../../../virt/kvm/arm/vgic.c:1468 kvm_vgic_sync_hwstate+0x314/0x344()
[ 762.022884] Modules linked in:
[ 762.022902] CPU: 1 PID: 972 Comm: qemu-system-arm Not tainted 3.19.0-rc7-00221-gfd7a168-dirty #13
[ 762.022911] Hardware name: NVIDIA Tegra SoC (Flattened Device Tree)
[ 762.022937] [<c0025d80>] (unwind_backtrace) from [<c00215d8>] (show_stack+0x10/0x14)
[ 762.022958] [<c00215d8>] (show_stack) from [<c065f494>] (dump_stack+0x98/0xd8)
[ 762.022976] [<c065f494>] (dump_stack) from [<c0035f38>] (warn_slowpath_common+0x80/0xb0)
[ 762.022991] [<c0035f38>] (warn_slowpath_common) from [<c0036004>] (warn_slowpath_null+0x1c/0x24)
[ 762.023007] [<c0036004>] (warn_slowpath_null) from [<c001c3c4>] (kvm_vgic_sync_hwstate+0x314/0x344)
[ 762.023024] [<c001c3c4>] (kvm_vgic_sync_hwstate) from [<c00147c0>] (kvm_arch_vcpu_ioctl_run+0x210/0x400)
[ 762.023041] [<c00147c0>] (kvm_arch_vcpu_ioctl_run) from [<c001063c>] (kvm_vcpu_ioctl+0x2e4/0x6ec)
[ 762.023059] [<c001063c>] (kvm_vcpu_ioctl) from [<c01098a4>] (do_vfs_ioctl+0x40c/0x600)
[ 762.023076] [<c01098a4>] (do_vfs_ioctl) from [<c0109acc>] (SyS_ioctl+0x34/0x5c)
[ 762.023091] [<c0109acc>] (SyS_ioctl) from [<c001e320>] (ret_fast_syscall+0x0/0x34)
BTW, KVM tracing support on ARM seems like it requires some care. E.g.:
kvm_exit does not report an exit reason. The in-kernel vgic also seems
to lack instrumentation. Unfortunate. Tracing is usually the first stop
when KVM is stuck on a guest.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2015-02-08 7:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 7:48 Jan Kiszka [this message]
2015-02-13 4:46 ` arm: warning at virt/kvm/arm/vgic.c:1468 Christoffer Dall
2015-02-13 6:21 ` Jan Kiszka
2015-02-13 6:31 ` Christoffer Dall
2015-02-13 6:28 ` Alex Bennée
2015-02-13 6:53 ` Alex Bennée
2015-02-15 8:53 ` Jan Kiszka
2015-02-15 13:37 ` Marc Zyngier
2015-02-15 14:40 ` Jan Kiszka
2015-02-15 14:59 ` Marc Zyngier
2015-02-15 15:07 ` Jan Kiszka
2015-02-15 15:30 ` Marc Zyngier
2015-02-15 15:35 ` Jan Kiszka
2015-02-15 15:59 ` Christoffer Dall
2015-02-15 16:10 ` Jan Kiszka
2015-02-15 18:01 ` Jan Kiszka
2015-02-15 19:03 ` Jan Kiszka
2015-02-16 8:57 ` Marc Zyngier
2015-02-16 9:00 ` Jan Kiszka
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=54D714B9.6090106@web.de \
--to=jan.kiszka@web.de \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.