From: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
To: "Lluís Vilanova" <vilanova@ac.upc.edu>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
kbastian@mail.upb.de, QEMU Developers <qemu-devel@nongnu.org>,
Peer Adelt <peer.adelt@c-lab.de>
Subject: Re: [Qemu-devel] [RFC PATCH 0/3] (Resend) TranslationBlock annotation mechanism
Date: Thu, 28 Jan 2016 14:40:55 +0100 [thread overview]
Message-ID: <56AA1A67.7030609@mail.uni-paderborn.de> (raw)
In-Reply-To: <87egd2kg4m.fsf@fimbulvetr.bsc.es>
Hi Lluis,
On 01/27/2016 07:54 PM, Lluís Vilanova wrote:
> There is this modified version I wrote [1], which precisely provides a plugin
> infrastructure to attach callbacks into guest code events (a binary
> instrumentation framework based on QEMU). At the time, the discussion resolved
> that a full code instrumentation interface for plugins was too much code that
> regular QEMU users & developers would not care about, easily leading to bitrot.
>
This is too bad but looking at the discussion back then the
argumentation is reasonable since an instrumentation API would and
should touch everything in QEMU.
> Instead, the list resolved (AFAIU) that it would be better to mainstream support
> for guest code events, and make instrumentation an unofficial extension. I've
> been (slowly) working to separate both pieces, making instrumentation a QEMU
> patch that can be easily maintained out of tree.
>
> The last patch series I sent sets the final stone on the core infrastructure for
> the mainline part, just missing the patches I have queued to start adding guest
> code trace events.
Can you give me the name of the series.
>
> So, I'd say that such support is on the list of current developments (at least
> mine, specially now that I have a bit more time for it). But getting the core
> infrastructure mainlined takes some time to ensure it makes sense and can be
> easily maintained and be generally usefull to vanilla QEMU.
>
For us such a API would make a lot of sense and there is no benefit for
us to do our own API. Would it make sense for you if we helped you?
Cheers,
Bastian
next prev parent reply other threads:[~2016-01-28 13:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 10:55 [Qemu-devel] [RFC PATCH 0/3] (Resend) TranslationBlock annotation mechanism Peer Adelt
2016-01-14 10:55 ` [Qemu-devel] [RFC PATCH 1/3] tb-annotation: Added annotation XML file parser Peer Adelt
2016-01-14 10:55 ` [Qemu-devel] [RFC PATCH 2/3] tb-annotation: Add control flow graph mapper Peer Adelt
2016-01-14 10:55 ` [Qemu-devel] [RFC PATCH 3/3] tb-annotation: Activate annotation extension Peer Adelt
2016-01-14 10:57 ` [Qemu-devel] [RFC PATCH 0/3] (Resend) TranslationBlock annotation mechanism Peer Adelt
2016-01-25 13:54 ` Peter Maydell
2016-01-26 11:02 ` Bastian Koppelmann
2016-01-27 18:54 ` Lluís Vilanova
2016-01-28 13:40 ` Bastian Koppelmann [this message]
2016-01-28 18:29 ` Lluís Vilanova
2016-02-01 22:33 ` Lluís Vilanova
2016-01-28 15:26 ` Frederic Konrad
2016-02-04 14:59 ` Bastian Koppelmann
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=56AA1A67.7030609@mail.uni-paderborn.de \
--to=kbastian@mail.uni-paderborn.de \
--cc=kbastian@mail.upb.de \
--cc=pbonzini@redhat.com \
--cc=peer.adelt@c-lab.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vilanova@ac.upc.edu \
/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).