From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2 0/5] arm64: kvm: reset hyp context for kexec
Date: Mon, 30 Mar 2015 08:16:13 +0100 [thread overview]
Message-ID: <20150330081613.60ff7dc0@arm.com> (raw)
In-Reply-To: <5518A969.3090707@linaro.org>
On Mon, 30 Mar 2015 02:39:53 +0100
AKASHI Takahiro <takahiro.akashi@linaro.org> wrote:
> On 03/28/2015 02:40 AM, Kyle McMartin wrote:
> > On Fri, Mar 27, 2015 at 03:37:04PM +0000, Marc Zyngier wrote:
> >>> [ 236.260863] Kernel panic - not syncing: HYP panic:
> >>> [ 236.260863] PS:600003c9 PC:000003ffffff0830 ESR:0000000096000006
> >>
> >> It would be interesting if you could find out what you have at offset
> >> 0x830 of hyp-init.o (the stack trace is for EL1, and is not going to
> >> help much).
> >>
> >
> > Given the alignment, i'm going to assume i'm looking at the right thing:
> >
> > 0000000000000820 <__kvm_hyp_reset>:
> > 820: d51c2000 msr ttbr0_el2, x0
> > 824: d5033fdf isb
> > 828: d50c871f tlbi alle2
> > 82c: d5033f9f dsb sy
> > 830: 10000060 adr x0, 83c <__kvm_hyp_reset+0x1c>
> > 834: b3403c01 bfxil x1, x0, #0, #16
> > 838: d61f0020 br x1
> > 83c: d53c1000 mrs x0, sctlr_el2
> >
> > but it seems fairly implausible to be trapping on ADR x0, 1f...
>
>
> I've never seen this panic on fast model...
>
> ESR shows that
> - Exception class: Data abort taken without a change in Exception level
> - Data fault status code: Translation fault at EL2
>
> and FAR seems not to be a proper address.
... which is consistent with what we're seeing here (data fault on
something that doesn't generate a load/store). I'm pretty sure the
page tables are screwed.
Have you tested it with 64k pages?
Thanks,
M.
--
Jazz is not dead. It just smells funny.
next prev parent reply other threads:[~2015-03-30 7:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 8:25 [RFC v2 0/5] arm64: kvm: reset hyp context for kexec AKASHI Takahiro
2015-03-26 8:25 ` [RFC v2 1/5] arm64: kvm: add a cpu tear-down function AKASHI Takahiro
2015-03-26 8:25 ` [RFC v2 2/5] arm64: kvm: allow EL2 context to be reset on shutdown AKASHI Takahiro
2015-03-26 8:25 ` [RFC v2 3/5] arm64: kvm: add cpu reset hook for cpu hotplug AKASHI Takahiro
2015-03-26 8:25 ` [RFC v2 4/5] arm64: kvm: add cpu reset at module exit AKASHI Takahiro
2015-03-26 8:25 ` [RFC v2 5/5] arm: kvm: add stub implementation for kvm_cpu_reset() AKASHI Takahiro
2015-03-27 15:31 ` [RFC v2 0/5] arm64: kvm: reset hyp context for kexec Kyle McMartin
2015-03-27 15:37 ` Marc Zyngier
2015-03-27 17:40 ` Kyle McMartin
2015-03-27 17:50 ` Marc Zyngier
2015-03-30 1:39 ` AKASHI Takahiro
2015-03-30 7:16 ` Marc Zyngier [this message]
2015-03-30 8:54 ` AKASHI Takahiro
2015-03-31 6:04 ` AKASHI Takahiro
2015-03-31 7:31 ` Marc Zyngier
2015-04-01 5:06 ` AKASHI Takahiro
2015-04-01 9:05 ` Marc Zyngier
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=20150330081613.60ff7dc0@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).