From: Thomas Huth <thuth@redhat.com>
To: "Emilio G. Cota" <cota@braap.org>, qemu-devel@nongnu.org
Cc: "Lluís Vilanova" <vilanova@ac.upc.edu>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [RFC 0/6] initial plugin support
Date: Tue, 26 Sep 2017 06:22:31 +0200 [thread overview]
Message-ID: <c9b8e5af-3ccb-5747-78b4-de8e11e5e081@redhat.com> (raw)
In-Reply-To: <1504729728-23279-1-git-send-email-cota@braap.org>
On 06.09.2017 22:28, Emilio G. Cota wrote:
> Related threads:
> [PATCH 00/13] instrument: Add basic event instrumentation
> Date: Mon, 24 Jul 2017 20:02:24 +0300
> https://lists.gnu.org/archive/html/qemu-devel/2017-07/msg07419.html
> and
> [PATCH v4 00/20] instrument: Add basic event instrumentation
> Date: Wed, 6 Sep 2017 20:22:41 +0300
> https://lists.gnu.org/archive/html/qemu-devel/2017-07/msg07419.html
>
> This set does something similar to the instrumentation patches by Lluis,
> but with a different implementation (and for now less events).
>
> My focus has been on working on the skeleton of a (pseudo) stable API,
> as Stefan requested. Of course more events would have to be added, but
> before spending more time on this I'd like to get some feedback on the
> core of the design. Patch 2 has all the details.
Sorry for my ignorance, but if you send a patch series like this, could
you please elaborate a little bit more on the topic what this all is
about? In this cover letter, you basically give only some pointers about
other patch series and point the reader to patch 2, but also patch 2
does not really have a proper *description* of what this is really all
about. Sure, it's about plugins, but what kind of plugins? Audio? Video?
CPU? Everything? If you send RFC, you should properly describe your
vision first, and maybe give some examples, before you jump into the
details.
Thanks,
Thomas
next prev parent reply other threads:[~2017-09-26 4:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 20:28 [Qemu-devel] [RFC 0/6] initial plugin support Emilio G. Cota
2017-09-06 20:28 ` [Qemu-devel] [RFC 1/6] tcg: keep a pointer to the current TB in TCGContext Emilio G. Cota
2017-09-06 20:28 ` [Qemu-devel] [RFC 2/6] plugin: add initial plugin support Emilio G. Cota
2017-09-06 20:41 ` Emilio G. Cota
2017-09-26 4:27 ` Thomas Huth
2017-09-06 20:28 ` [Qemu-devel] [RFC 3/6] configure: add --enable-plugins Emilio G. Cota
2017-09-06 20:28 ` [Qemu-devel] [RFC 4/6] Makefile: install qemu-api.h as include/qemu-plugin.h Emilio G. Cota
2017-09-06 20:28 ` [Qemu-devel] [RFC 5/6] vl: support -plugin option Emilio G. Cota
2017-09-06 20:28 ` [Qemu-devel] [RFC 6/6] linux-user: " Emilio G. Cota
2017-09-14 14:33 ` [Qemu-devel] [RFC 0/6] initial plugin support Peter Maydell
2017-09-18 14:59 ` Stefan Hajnoczi
2017-09-18 15:05 ` Peter Maydell
2017-09-19 9:51 ` Stefan Hajnoczi
2017-09-25 18:12 ` Lluís Vilanova
2017-09-26 4:22 ` Thomas Huth [this message]
2017-09-26 9:32 ` Stefan Hajnoczi
2017-09-26 16:15 ` Emilio G. Cota
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=c9b8e5af-3ccb-5747-78b4-de8e11e5e081@redhat.com \
--to=thuth@redhat.com \
--cc=cota@braap.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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).