From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jan Kiszka <jan.kiszka@web.de>
Subject: arm: warning at virt/kvm/arm/vgic.c:1468
Date: Sun, 08 Feb 2015 08:48:09 +0100
Message-ID: <54D714B9.6090106@web.de>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="F2WBIBwIfXSGc4GgxmRjmoldLnvO3mH3I"
To: kvm <kvm@vger.kernel.org>, kvmarm <kvmarm@lists.cs.columbia.edu>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Christoffer Dall <christoffer.dall@linaro.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mout.web.de ([212.227.15.4]:52943 "EHLO mout.web.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1750812AbbBHHsP (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sun, 8 Feb 2015 02:48:15 -0500
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--F2WBIBwIfXSGc4GgxmRjmoldLnvO3mH3I
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: quoted-printable

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-r=
c7-00221-gfd7a168-dirty #13
[  762.022911] Hardware name: NVIDIA Tegra SoC (Flattened Device Tree)
[  762.022937] [<c0025d80>] (unwind_backtrace) from [<c00215d8>] (show_st=
ack+0x10/0x14)
[  762.022958] [<c00215d8>] (show_stack) from [<c065f494>] (dump_stack+0x=
98/0xd8)
[  762.022976] [<c065f494>] (dump_stack) from [<c0035f38>] (warn_slowpath=
_common+0x80/0xb0)
[  762.022991] [<c0035f38>] (warn_slowpath_common) from [<c0036004>] (war=
n_slowpath_null+0x1c/0x24)
[  762.023007] [<c0036004>] (warn_slowpath_null) from [<c001c3c4>] (kvm_v=
gic_sync_hwstate+0x314/0x344)
[  762.023024] [<c001c3c4>] (kvm_vgic_sync_hwstate) from [<c00147c0>] (kv=
m_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_io=
ctl+0x40c/0x600)
[  762.023076] [<c01098a4>] (do_vfs_ioctl) from [<c0109acc>] (SyS_ioctl+0=
x34/0x5c)
[  762.023091] [<c0109acc>] (SyS_ioctl) from [<c001e320>] (ret_fast_sysca=
ll+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


--F2WBIBwIfXSGc4GgxmRjmoldLnvO3mH3I
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlTXFLkACgkQitSsb3rl5xQhkQCfXGTf1yxBxzPxXyRjKlumvp9G
r4kAoKfevjcY4jo2qFtCEGfK6FjUQWPf
=be5f
-----END PGP SIGNATURE-----

--F2WBIBwIfXSGc4GgxmRjmoldLnvO3mH3I--