From: "Alex Bennée" <alex.bennee@linaro.org>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Jan Kiszka <jan.kiszka@web.de>,
kvmarm <kvmarm@lists.cs.columbia.edu>, kvm <kvm@vger.kernel.org>
Subject: Re: arm: warning at virt/kvm/arm/vgic.c:1468
Date: Fri, 13 Feb 2015 06:53:28 +0000 [thread overview]
Message-ID: <87iof6s3o7.fsf@linaro.org> (raw)
In-Reply-To: <87k2zms4ub.fsf@linaro.org>
Alex Bennée <alex.bennee@linaro.org> writes:
> Christoffer Dall <christoffer.dall@linaro.org> writes:
<snip>
>> On Sun, Feb 08, 2015 at 08:48:09AM +0100, Jan Kiszka wrote:
<snip>
>>> 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.
>>
>> 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.
--
Alex Bennée
next prev parent reply other threads:[~2015-02-13 6:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 7:48 arm: warning at virt/kvm/arm/vgic.c:1468 Jan Kiszka
2015-02-13 4:46 ` 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 [this message]
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=87iof6s3o7.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=jan.kiszka@web.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).