From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex =?utf-8?Q?Benn=C3=A9e?= Subject: Re: arm: warning at virt/kvm/arm/vgic.c:1468 Date: Fri, 13 Feb 2015 06:53:28 +0000 Message-ID: <87iof6s3o7.fsf@linaro.org> References: <54D714B9.6090106@web.de> <20150213044613.GA47577@lvm> <87k2zms4ub.fsf@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Marc Zyngier , Jan Kiszka , kvmarm , kvm To: Christoffer Dall Return-path: Received: from static.88-198-71-155.clients.your-server.de ([88.198.71.155]:37282 "EHLO socrates.bennee.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751789AbbBMGw5 (ORCPT ); Fri, 13 Feb 2015 01:52:57 -0500 In-reply-to: <87k2zms4ub.fsf@linaro.org> Sender: kvm-owner@vger.kernel.org List-ID: Alex Benn=C3=A9e writes: > Christoffer Dall writes: >> On Sun, Feb 08, 2015 at 08:48:09AM +0100, Jan Kiszka wrote: >>> BTW, KVM tracing support on ARM seems like it requires some care. E= =2Eg.: >>> kvm_exit does not report an exit reason. The in-kernel vgic also se= ems >>> to lack instrumentation. Unfortunate. Tracing is usually the first = stop >>> when KVM is stuck on a guest. >> >> I know, the exit reason is on my todo list, and Alex B is sitting on >> trace patches for the gic. Coming soon to a git repo near your. > > For the impatient the raw patches are in: > > git.linaro.org/people/alex.bennee/linux.git > migration/v3.19-rc7-improve-tracing OK try tracing/kvm-exit-entry for something cleaner. --=20 Alex Benn=C3=A9e