From: Richard Henderson <rth@twiddle.net>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-xtensa: raise an exception for invalid and reserved opcodes
Date: Tue, 25 Oct 2011 10:41:34 -0700 [thread overview]
Message-ID: <4EA6F4CE.8060304@twiddle.net> (raw)
In-Reply-To: <201110252124.58870.jcmvbkbc@gmail.com>
On 10/25/2011 10:24 AM, Max Filippov wrote:
> Do you mean that I have to end the TB on every instruction that will definitely raise an exception?
> Or on every instruction that potentially raises an exception?
> I didn't do any of the above anywhere.
Normally we do end the TB on every instruction that will definitely
raise an exception. There's little point to continue translation,
since we know for a fact that control will transfer out of the cpu loop.
r~
next prev parent reply other threads:[~2011-10-25 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 16:44 [Qemu-devel] [PATCH] target-xtensa: raise an exception for invalid and reserved opcodes Max Filippov
2011-10-25 16:51 ` Peter Maydell
2011-10-25 17:24 ` Max Filippov
2011-10-25 17:41 ` Richard Henderson [this message]
2011-10-25 19:24 ` [Qemu-devel] [PATCH v2] " Max Filippov
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=4EA6F4CE.8060304@twiddle.net \
--to=rth@twiddle.net \
--cc=jcmvbkbc@gmail.com \
--cc=peter.maydell@linaro.org \
--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).