From: "Emilio G. Cota" <cota@braap.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org, peter.maydell@linaro.org, alex.bennee@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2 0/3] target/arm: Reduce overhead of cpu_get_tb_cpu_state
Date: Thu, 21 Feb 2019 16:21:30 -0500 [thread overview]
Message-ID: <20190221212130.GA6971@flamenco> (raw)
In-Reply-To: <20190219233421.388-1-richard.henderson@linaro.org>
On Tue, Feb 19, 2019 at 15:34:18 -0800, Richard Henderson wrote:
> Changes since v1:
> * Apparently I had started a last-minute API change, and failed to
> covert all of the users, and also failed to re-test afterward.
> * Retain assertions for --enable-debug-tcg.
This brings my arm-softmmu bootup+shutdown test to an early death:
[...]
VFS: Mounted root (ext4 filesystem) readonly on device 254:1.
devtmpfs: mounted
Freeing unused kernel memory: 300K (80669000 - 806b4000)
BUG: unsupported FP instruction in kernel mode
Internal error: Oops - undefined instruction: 0 [#1] SMP ARM
Modules linked in:
CPU: 0 PID: 1 Comm: init Not tainted 4.5.0-ajb #10
Hardware name: Generic DT based system
task: eec58000 ti: eec52000 task.ti: eec52000
PC is at vfp_reload_hw+0xc/0x44
LR is at __und_usr_fault_32+0x0/0x8
pc : [<8000ab94>] lr : [<800136c0>] psr: 000c0013
sp : eec53fb0 ip : 7eb88918 fp : 00000000
r10: eec520f8 r9 : 8001371c r8 : 00000b00
r7 : 00000001 r6 : eec5204c r5 : 40000000 r4 : 00000000
r3 : 806e1058 r2 : 76fc1362 r1 : 40000000 r0 : ecac8b10
Flags: nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
Control: 30c5387d Table: ae4048c0 DAC: fffffffd
Process init (pid: 1, stack limit = 0xeec52210)
Stack: (0xeec53fb0 to 0xeec54000)
3fa0: 7eb888f0 00000000 003fb0d6 fffffd90
3fc0: 7eb888e0 76fd8050 00000000 7eb88ab0 00000000 0001223c 76fd8958 7eb88a90
3fe0: 7eb88918 7eb888c0 76fbb187 76fc1362 600c0030 ffffffff 00000000 00000000
[<8000ab94>] (vfp_reload_hw) from [<800136c0>] (__und_usr_fault_32+0x0/0x8)
Code: 0a000010 e58ab110 eee85a10 e783a10b (ecba0b20)
---[ end trace 26acd422f5b3785f ]---
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Thanks,
Emilio
next prev parent reply other threads:[~2019-02-21 21:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 23:34 [Qemu-devel] [PATCH v2 0/3] target/arm: Reduce overhead of cpu_get_tb_cpu_state Richard Henderson
2019-02-19 23:34 ` [Qemu-devel] [PATCH v2 1/3] target/arm: Split out recompute_hflags et al Richard Henderson
2019-02-19 23:34 ` [Qemu-devel] [PATCH v2 2/3] target/arm: Rebuild hflags at el changes and MSR writes Richard Henderson
2019-02-20 10:31 ` Alex Bennée
2019-02-19 23:34 ` [Qemu-devel] [PATCH v2 3/3] target/arm: Rely on hflags correct in cpu_get_tb_cpu_state Richard Henderson
2019-02-20 10:33 ` Alex Bennée
2019-02-20 0:03 ` [Qemu-devel] [PATCH v2 0/3] target/arm: Reduce overhead of cpu_get_tb_cpu_state no-reply
2019-02-20 0:07 ` no-reply
2019-02-21 21:21 ` Emilio G. Cota [this message]
2019-02-21 22:36 ` Alex Bennée
2019-02-21 22:59 ` Emilio G. Cota
2019-02-22 0:14 ` Richard Henderson
2019-02-27 15:28 ` no-reply
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=20190221212130.GA6971@flamenco \
--to=cota@braap.org \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).