From: Sergey Fedorov <serge.fdrv@gmail.com>
To: Richard Henderson <rth@twiddle.net>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Eduardo Habkost <ehabkost@redhat.com>,
Anthony Green <green@moxielogic.com>,
Alexander Graf <agraf@suse.de>, Max Filippov <jcmvbkbc@gmail.com>,
Michael Walle <michael@walle.cc>,
qemu-arm@nongnu.org, qemu-ppc@nongnu.org,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
Leon Alrae <leon.alrae@imgtec.com>,
Aurelien Jarno <aurelien@aurel32.net>, Jia Liu <proljc@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] target-*: Get rid of "PC advancement" trick
Date: Thu, 17 Dec 2015 00:13:10 +0300 [thread overview]
Message-ID: <5671D3E6.2070808@gmail.com> (raw)
In-Reply-To: <56719970.9000106@twiddle.net>
On 12/16/15 20:03, Richard Henderson wrote:
> On 12/15/2015 01:02 PM, Sergey Fedorov wrote:
>>> For that, I think it might be interesting to arrange for non-empty
>>> TBs to
>>> exit prior to recognizing a breakpoint. So that a breakpoint TB is
>>> always
>>> just the one operation. Except for the fact that "generate an
>>> exception" has
>>> traditionally been a target-specific helper, we could almost make
>>> the entire
>>> breakpoint generation be done in common code.
>>>
>>> I'd think something like a generic "must we end the TB now"
>>> predicate would
>>> be the proper hook. It would contain all of the usual stuff:
>>> tcg_op_buf_full
>>> and checks for singlestep, but then add "is there a breakpoint at
>>> the next pc".
>>
>> This could be a next step :)
>
> Or perhaps a first step, since the patch you posted doesn't seem to me
> to be an improvement at all, merely a rearrangement of code.
I should give it a thought. The main motivation of this patch was to
simply suppress useless disas log and the instruction length mismatch
disas warning in case of an empty TB. The original reason was that there
is a place in ARM translation with "PC advancement" tick missed.
Thanks,
Sergey
prev parent reply other threads:[~2015-12-16 21:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 18:47 [Qemu-devel] [PATCH] target-*: Get rid of "PC advancement" trick Sergey Fedorov
2015-12-11 23:39 ` Richard Henderson
2015-12-12 20:02 ` Sergey Fedorov
2015-12-14 16:19 ` Richard Henderson
2015-12-15 21:02 ` Sergey Fedorov
2015-12-16 17:03 ` Richard Henderson
2015-12-16 21:13 ` Sergey Fedorov [this message]
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=5671D3E6.2070808@gmail.com \
--to=serge.fdrv@gmail.com \
--cc=agraf@suse.de \
--cc=aurelien@aurel32.net \
--cc=edgar.iglesias@gmail.com \
--cc=ehabkost@redhat.com \
--cc=green@moxielogic.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=jcmvbkbc@gmail.com \
--cc=leon.alrae@imgtec.com \
--cc=michael@walle.cc \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=proljc@gmail.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rth@twiddle.net \
/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).