From: Max Filippov <jcmvbkbc@gmail.com>
To: Sergey Fedorov <serge.fdrv@gmail.com>
Cc: "Richard Henderson" <rth@twiddle.net>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] "tcg: Clean up direct block chaining safety checks" breaks target-xtensa mmu test
Date: Sun, 15 May 2016 21:58:24 +0300 [thread overview]
Message-ID: <20160515185824.GA24189@octofox.metropolis> (raw)
Hi Sergey,
I've noticed that the commit 5b053a4a28278 (tcg: Clean up direct block
chaining safety checks) has broken tearget-xtensa test cross_page_tb
from the tests/tcg/xtensa/test_mmu.S. The test runs a TB that spans two
adjacent pages, then unmaps the second page and runs it again. It
expects an instruction fetch exception on the second run, but with the
said commit doesn't get it. Reverting that commit fixes the test.
Any suggestions?
--
Thanks.
-- Max
next reply other threads:[~2016-05-15 18:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-15 18:58 Max Filippov [this message]
2016-05-15 19:38 ` [Qemu-devel] "tcg: Clean up direct block chaining safety checks" breaks target-xtensa mmu test Sergey Fedorov
2016-05-15 19:53 ` Max Filippov
2016-05-15 19:56 ` Sergey Fedorov
2016-05-15 20:54 ` Sergey Fedorov
2016-05-16 14:36 ` Sergey Fedorov
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=20160515185824.GA24189@octofox.metropolis \
--to=jcmvbkbc@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=serge.fdrv@gmail.com \
/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).