From: Stefan Hajnoczi <stefanha@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Stefan Hajnoczi" <stefanha@gmail.com>,
"Lluís Vilanova" <vilanova@ac.upc.edu>,
"Alessandro Di Federico" <ale+qemu@clearmind.me>,
"Daniel P. Berrange" <berrange@redhat.com>,
"Emilio G. Cota" <cota@braap.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 00/13] instrument: Add basic event instrumentation
Date: Wed, 2 Aug 2017 12:04:00 +0100 [thread overview]
Message-ID: <20170802110400.GI5531@stefanha-x1.localdomain> (raw)
In-Reply-To: <CAFEAcA9KKqyiNfsfjSDVhhE7hMMsAZ==TuSjgtqb6pB=fVF+_w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2098 bytes --]
On Tue, Aug 01, 2017 at 02:54:29PM +0100, Peter Maydell wrote:
> On 1 August 2017 at 14:48, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> > Thanks for sharing the requirements. A stable API is necessary for
> > providing these features.
> >
> > We're essentially talking about libqemu. That means QEMU in library
> > form with an API for JIT engine, reverse engineering, instrumentation,
> > etc tasks.
>
> > Maintaining libqemu will take ongoing effort and no one has committed.
> > The last discussion about libqemu was here:
> > https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg04847.html
>
> That thread seems to be focused on trying to extract TCG
> from the rest of QEMU, which definitely isn't a requirement
> for instrumentation, and I would suggest is something
> of a distraction from it.
You are right, it's a different use case. I just wanted to reference
previous discussion about libqemu. There have been more in the past for
different use cases.
> I want to be able to say "just
> instrument this setup that QEMU already provides as a
> board model", not have to write a driver that duplicates
> all the work vl.c and our board models do for us today,
Calling qemu_init(argc, argv) and qemu_run() isn't too onerous. For the
price of that you get an environment where we can offer stable APIs.
> and I don't need the TCG engine to be a library to do that...
You do need TCG APIs if you want TCG-level instrumentation, tuning
options, callbacks, etc.
> I agree that we want to provide something that is at least
> closer to a stable API than "just expose trace events",
> though.
libqemu has at least three parts:
1. VM API (i.e. qemu_init(argc, argv), qemu_run(), qemu_vcpu_get_reg32())
2. TCG engine
3. Device models
Like I said in my email, start with what matters for the instrumentation
use case (VM API at a minimum to control guest execution). Other people
can flesh out the other parts later, as needed.
Other attempts to provide a stable API will be essentially the same
thing as libqemu.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-08-02 11:04 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 17:02 [Qemu-devel] [PATCH 00/13] instrument: Add basic event instrumentation Lluís Vilanova
2017-07-24 17:06 ` [Qemu-devel] [PATCH 01/13] instrument: Add documentation Lluís Vilanova
2017-07-24 17:10 ` [Qemu-devel] [PATCH 02/13] instrument: [none] Add null instrumentation mode Lluís Vilanova
2017-07-24 17:14 ` [Qemu-devel] [PATCH 03/13] instrument: [dynamic] Add dynamic " Lluís Vilanova
2017-07-24 17:18 ` [Qemu-devel] [PATCH 04/13] instrument: Allow adding the "instrument" property without modifying event files Lluís Vilanova
2017-07-24 17:22 ` [Qemu-devel] [PATCH 05/13] instrument: [dynamic] Add default public per-event functions Lluís Vilanova
2017-07-24 17:26 ` [Qemu-devel] [PATCH 06/13] instrument: Add event control interface Lluís Vilanova
2017-07-24 17:30 ` [Qemu-devel] [PATCH 07/13] instrument: Add generic command line library loader Lluís Vilanova
2017-07-24 17:34 ` [Qemu-devel] [PATCH 08/13] instrument: [linux-user] Add " Lluís Vilanova
2017-07-24 17:38 ` [Qemu-devel] [PATCH 09/13] instrument: [bsd-user] " Lluís Vilanova
2017-07-24 17:42 ` [Qemu-devel] [PATCH 10/13] instrument: [softmmu] " Lluís Vilanova
2017-07-24 17:46 ` [Qemu-devel] [PATCH 11/13] instrument: [qapi] Add " Lluís Vilanova
2017-07-24 18:03 ` Eric Blake
2017-07-25 8:24 ` Lluís Vilanova
2017-07-25 11:30 ` Eric Blake
2017-07-25 11:51 ` Lluís Vilanova
2017-07-24 17:50 ` [Qemu-devel] [PATCH 12/13] instrument: [hmp] " Lluís Vilanova
2017-07-24 17:54 ` [Qemu-devel] [PATCH 13/13] trace: Rename C++-specific names in event arguments Lluís Vilanova
2017-07-25 13:19 ` [Qemu-devel] [PATCH 00/13] instrument: Add basic event instrumentation Stefan Hajnoczi
2017-07-25 13:30 ` Peter Maydell
2017-07-25 15:11 ` Lluís Vilanova
2017-07-26 11:22 ` Stefan Hajnoczi
2017-07-26 12:44 ` Lluís Vilanova
2017-07-27 10:32 ` Stefan Hajnoczi
2017-07-27 10:40 ` Peter Maydell
2017-07-28 13:42 ` Stefan Hajnoczi
2017-07-28 16:21 ` Lluís Vilanova
2017-08-02 11:04 ` Stefan Hajnoczi
2017-07-26 11:26 ` Stefan Hajnoczi
2017-07-26 11:49 ` Peter Maydell
2017-07-26 12:26 ` Lluís Vilanova
2017-07-27 10:43 ` Daniel P. Berrange
2017-07-27 10:54 ` Peter Maydell
2017-07-27 14:58 ` Lluís Vilanova
2017-07-27 15:21 ` Daniel P. Berrange
2017-07-27 15:33 ` Peter Maydell
2017-07-27 15:45 ` Daniel P. Berrange
2017-07-28 13:34 ` Stefan Hajnoczi
2017-07-28 13:41 ` Peter Maydell
2017-07-28 14:06 ` Daniel P. Berrange
2017-07-28 16:05 ` Lluís Vilanova
2017-08-01 13:48 ` Stefan Hajnoczi
2017-08-01 13:54 ` Peter Maydell
2017-08-02 11:04 ` Stefan Hajnoczi [this message]
2017-08-02 11:10 ` Peter Maydell
2017-08-02 14:49 ` Stefan Hajnoczi
2017-08-02 15:19 ` Lluís Vilanova
2017-08-03 11:54 ` Stefan Hajnoczi
2017-08-26 0:14 ` Emilio G. Cota
2017-08-26 0:02 ` Emilio G. Cota
2017-08-29 9:19 ` Peter Maydell
2017-07-28 13:52 ` Daniel P. Berrange
2017-07-28 16:14 ` Lluís Vilanova
2017-08-01 13:13 ` Stefan Hajnoczi
2017-07-28 15:10 ` Lluís Vilanova
2017-07-27 19:55 ` Lluís Vilanova
2017-07-25 14:47 ` Lluís Vilanova
2017-07-26 11:29 ` Stefan Hajnoczi
2017-07-26 12:31 ` Lluís Vilanova
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=20170802110400.GI5531@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=ale+qemu@clearmind.me \
--cc=berrange@redhat.com \
--cc=cota@braap.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).