From: Peter Maydell <peter.maydell@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: plugin order of registration and order of callback
Date: Sun, 12 Jan 2020 20:35:41 +0000 [thread overview]
Message-ID: <CAFEAcA_zebKVd9FUHM9vhAkh_8_1aCUjh_2XTQuErz8X8gQVHA@mail.gmail.com> (raw)
In-Reply-To: <87eew7ik47.fsf@linaro.org>
On Fri, 10 Jan 2020 at 12:15, Alex Bennée <alex.bennee@linaro.org> wrote:
> With that in mind we should say instruction callbacks are always before
> the instruction executes. The reason being is some instructions can
> fault and exit the run loop so any instrumentation inserted afterwards
> will never execute.
I suppose in theory we could also have an "instruction retired
successfully" event (by analogy with the h/w perf events that
some architectures have), if it's generally useful; it sounds
like it wouldn't solve the problem here though.
thanks
-- PMM
prev parent reply other threads:[~2020-01-12 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 22:41 plugin order of registration and order of callback Robert Henry
2020-01-10 12:14 ` Alex Bennée
2020-01-12 20:35 ` Peter Maydell [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=CAFEAcA_zebKVd9FUHM9vhAkh_8_1aCUjh_2XTQuErz8X8gQVHA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@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).