From: Laszlo Ersek <lersek@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Pekka Enberg <penberg@iki.fi>,
KVM devel mailing list <kvm@vger.kernel.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] KVM/QEMU on Raspberry Pi 3
Date: Thu, 2 Feb 2017 18:57:51 +0100 [thread overview]
Message-ID: <46bb8ce2-bc2f-fb4b-800d-a180c402082c@redhat.com> (raw)
In-Reply-To: <CAKv+Gu-k6ZS=+jd5eQ58_M44gzOCJzQhm212ASVr1espiB167A@mail.gmail.com>
On 02/02/17 18:48, Ard Biesheuvel wrote:
>>> ESR 0x02000000 FAR 0x1DE7EC7EDBADC0DE
>>>
>
>
> $ git grep -C5 -ni 0x1DE7EC7EDBADC0DE
> arch/arm64/kvm/sys_regs.h-105-static inline void reset_unknown(struct
> kvm_vcpu *vcpu,
> arch/arm64/kvm/sys_regs.h-106- const struct
> sys_reg_desc *r)
> arch/arm64/kvm/sys_regs.h-107-{
> arch/arm64/kvm/sys_regs.h-108- BUG_ON(!r->reg);
> arch/arm64/kvm/sys_regs.h-109- BUG_ON(r->reg >= NR_SYS_REGS);
> arch/arm64/kvm/sys_regs.h:110: vcpu_sys_reg(vcpu, r->reg) =
> 0x1de7ec7edbadc0deULL;
> arch/arm64/kvm/sys_regs.h-111-}
> arch/arm64/kvm/sys_regs.h-112-
>
> In other words (or rather, in words), KVM is triggering this exception
> in the guest deliberately, which I suspect has something to do with
> the lack of a GIC? Are you using these patches Peter mentions?
"detected bad code". Mind = blown.
next prev parent reply other threads:[~2017-02-02 17:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 14:44 [Qemu-devel] KVM/QEMU on Raspberry Pi 3 Pekka Enberg
2017-02-02 14:59 ` Marc Zyngier
2017-02-02 15:12 ` Christoffer Dall
2017-02-02 15:50 ` Laszlo Ersek
2017-02-02 15:52 ` Ard Biesheuvel
2017-02-02 16:27 ` Peter Maydell
2017-02-02 17:48 ` Ard Biesheuvel
2017-02-02 17:57 ` Laszlo Ersek [this message]
2017-02-02 19:24 ` Pekka Enberg
2017-02-03 9:27 ` Gerd Hoffmann
2017-02-03 9:31 ` Alexander Graf
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=46bb8ce2-bc2f-fb4b-800d-a180c402082c@redhat.com \
--to=lersek@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=penberg@iki.fi \
--cc=qemu-devel@nongnu.org \
/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).