From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1838277] Re: qemu-system-aarch64: regression in 3.1: breakpoint instructions always routed to EL_D even when current EL is higher
Date: Tue, 30 Jul 2019 15:00:09 -0000 [thread overview]
Message-ID: <156449881062.20461.4065179426121337713.launchpad@chaenomeles.canonical.com> (raw)
In-Reply-To: 156441235921.17753.6613889826588806043.malonedeb@gac.canonical.com
** Changed in: qemu
Status: New => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1838277
Title:
qemu-system-aarch64: regression in 3.1: breakpoint instructions always
routed to EL_D even when current EL is higher
Status in QEMU:
In Progress
Bug description:
Affects 3.1.0 (latest stable release) and latest commit
(893dc8300c80e3dc32f31e968cf7aa0904da50c3) but did *not* affect 2.11
(qemu from bionic ubuntu LTS).
With the following code and shell commands:
test.s:
.text
mov x0, #0x60000000
msr vbar_el2, x0
dsb sy
isb sy
$ aarch64-none-elf-as test.s -o test.o
$ aarch64-none-elf-objcopy -S -O binary test.o test.bin
$ qemu-system-aarch64 -nographic -machine virt,virtualization=on -cpu cortex-a57 -kernel test.bin -s -S
vbar_el2 is still 0 after the code, instead of being the expected
0x60000000. (see screenshot).
This regression doesn't seem to happen for vbar_el1 &
virtualization=off.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1838277/+subscriptions
next prev parent reply other threads:[~2019-07-30 15:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 14:59 [Qemu-devel] [Bug 1838277] [NEW] qemu-system-aarch64: regression: msr vbar_el2, xN not working in EL2 Elouan Appéré
2019-07-29 15:23 ` [Qemu-devel] [Bug 1838277] " Elouan Appéré
2019-07-29 15:39 ` Alex Bennée
2019-07-29 15:40 ` Peter Maydell
2019-07-30 9:54 ` Elouan Appéré
2019-07-30 10:24 ` [Qemu-devel] [Bug 1838277] Re: qemu-system-aarch64: regression: TCG sometimes using wrong values for VBAR_EL2 despite it being correctly reported to GDB Peter Maydell
2019-07-30 10:26 ` Peter Maydell
2019-07-30 11:19 ` Elouan Appéré
2019-07-30 11:27 ` Elouan Appéré
2019-07-30 11:31 ` Peter Maydell
2019-07-30 11:49 ` Elouan Appéré
2019-07-30 11:57 ` Elouan Appéré
2019-07-30 12:04 ` Elouan Appéré
2019-07-30 12:17 ` Peter Maydell
2019-07-30 12:26 ` Peter Maydell
2019-07-30 12:26 ` Elouan Appéré
2019-07-30 12:29 ` Elouan Appéré
2019-07-30 12:38 ` Peter Maydell
2019-07-30 12:51 ` Elouan Appéré
2019-07-30 13:15 ` [Qemu-devel] [Bug 1838277] Re: qemu-system-aarch64: regression in 3.1: breakpoint instructions routed to EL1 from EL2 when ELD is EL1 Elouan Appéré
2019-07-30 13:28 ` [Qemu-devel] [Bug 1838277] Re: qemu-system-aarch64: regression in 3.1: breakpoint instructions always routed to EL_D even when current EL is higher Peter Maydell
2019-07-30 15:00 ` Peter Maydell [this message]
2019-07-31 9:37 ` Elouan Appéré
2019-08-02 17:54 ` Peter Maydell
2019-08-16 4:46 ` Thomas Huth
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=156449881062.20461.4065179426121337713.launchpad@chaenomeles.canonical.com \
--to=peter.maydell@linaro.org \
--cc=1838277@bugs.launchpad.net \
--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).