From: Jan Kiszka <jan.kiszka@web.de>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Christoffer Dall" <christoffer.dall@linaro.org>,
kvmarm <kvmarm@lists.cs.columbia.edu>, kvm <kvm@vger.kernel.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Wei Huang" <wei@redhat.com>
Subject: Re: arm: warning at virt/kvm/arm/vgic.c:1468
Date: Sun, 15 Feb 2015 15:40:40 +0100 [thread overview]
Message-ID: <54E0AFE8.20202@web.de> (raw)
In-Reply-To: <87wq3je1o4.fsf@why.wild-wind.fr.eu.org>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
On 2015-02-15 14:37, Marc Zyngier wrote:
> On Sun, Feb 15 2015 at 8:53:30 am GMT, Jan Kiszka <jan.kiszka@web.de> wrote:
>> I'm now throwing trace_printk at my broken KVM. Already found out that I
>> get ARM_EXCEPTION_IRQ every few 10 µs. Not seeing any irq_* traces,
>> though. Weird.
>
> This very much looks like a screaming interrupt. At such a rate, no
> wonder your VM make much progress. Can you find out which interrupt is
> screaming like this? Looking at GICC_HPPIR should help, but you'll have
> to map the CPU interface in HYP before being able to access it there.
OK... let me figure this out. I had this suspect as well - the host gets
a VM exit for each injected guest IRQ?
BTW, I also tried with in-kernel GIC disabled (in the kernel config),
but I guess that's pointless. Linux seems to be stuck on a
non-functional architectural timer then, right?
>
> Do you have an form of power-management on this system?
Just killed every config that has PM for FREQ in its name, but that
makes no difference.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-02-15 14:40 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
2015-02-15 8:53 ` Jan Kiszka
2015-02-15 13:37 ` Marc Zyngier
2015-02-15 14:40 ` Jan Kiszka [this message]
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=54E0AFE8.20202@web.de \
--to=jan.kiszka@web.de \
--cc=alex.bennee@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.com \
--cc=wei@redhat.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).