From: Max Filippov <jcmvbkbc@gmail.com>
To: qemu-devel@nongnu.org
Cc: "Richard Henderson" <richard.henderson@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Max Filippov" <jcmvbkbc@gmail.com>
Subject: [PATCH 2/2] tests/tcg/xtensa: add icount/ibreak priority test
Date: Thu, 30 Nov 2023 09:19:20 -0800 [thread overview]
Message-ID: <20231130171920.3798954-3-jcmvbkbc@gmail.com> (raw)
In-Reply-To: <20231130171920.3798954-1-jcmvbkbc@gmail.com>
When icount and ibreak exceptions are due to happen on the same address
icount has higher precedence.
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
---
tests/tcg/xtensa/test_break.S | 25 ++++++++++++++++++++++++-
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git a/tests/tcg/xtensa/test_break.S b/tests/tcg/xtensa/test_break.S
index 3aa18b5cec3f..4c618feb5b10 100644
--- a/tests/tcg/xtensa/test_break.S
+++ b/tests/tcg/xtensa/test_break.S
@@ -129,7 +129,7 @@ test ibreak_remove
4:
test_end
-test ibreak_priority
+test ibreak_break_priority
set_vector debug_vector, 2f
rsil a2, debug_level - 1
movi a2, 1f
@@ -145,6 +145,29 @@ test ibreak_priority
movi a3, 0x2
assert eq, a2, a3
test_end
+
+test ibreak_icount_priority
+ set_vector debug_vector, 2f
+ rsil a2, debug_level - 1
+ movi a2, 1f
+ wsr a2, ibreaka0
+ movi a2, 1
+ wsr a2, ibreakenable
+ movi a2, -2
+ wsr a2, icount
+ movi a2, 1
+ wsr a2, icountlevel
+ isync
+ rsil a2, 0
+ nop
+1:
+ break 0, 0
+ test_fail
+2:
+ rsr a2, debugcause
+ movi a3, 0x1
+ assert eq, a2, a3
+test_end
#endif
test icount
--
2.39.2
next prev parent reply other threads:[~2023-11-30 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 17:19 [PATCH 0/2] target/xtensa: use generic instruction breakpoint infrastructure Max Filippov
2023-11-30 17:19 ` [PATCH 1/2] " Max Filippov
2023-11-30 18:12 ` Richard Henderson
2023-11-30 17:19 ` Max Filippov [this message]
2023-11-30 18:20 ` [PATCH 2/2] tests/tcg/xtensa: add icount/ibreak priority test Richard Henderson
2024-01-08 16:46 ` [PATCH 0/2] target/xtensa: use generic instruction breakpoint infrastructure Philippe Mathieu-Daudé
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=20231130171920.3798954-3-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=philmd@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).