Re: [Qemu-devel] [PATCH 00/13] instrument: Add basic event instrumentation

From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
	"Stefan Hajnoczi" <stefanha@gmail.com>,
	"Emilio G. Cota" <cota@braap.org>,
	"Lluís Vilanova" <vilanova@ac.upc.edu>,
	"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 00/13] instrument: Add basic event instrumentation
Date: Fri, 28 Jul 2017 14:41:19 +0100	[thread overview]
Message-ID: <CAFEAcA9p38P2x3s4grvFPkGaH+JEmwqyAC9SsLWqqFL8k+Eiww@mail.gmail.com> (raw)
In-Reply-To: <20170728133430.GS12364@stefanha-x1.localdomain>

On 28 July 2017 at 14:34, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> Lluís/Peter: What are the requirements for instrumentation code
> interacting with the running QEMU instance?  simpletrace is
> asynchronous, meaning it does not wait for anyone handle the trace event
> before continuing execution, and is therefore not suitable for
> SystemTap-style scripts that can interact with the program while
> handling a trace event.

I think you'd probably want synchronous -- it's pretty helpful
to be able to say "register a trace event hook that doesn't
fire very often, and use that to get to the region of
execution that's of interest to you, then enable more hooks
to get more detail at that point". (For instance, "wait til
we've executed 5,000,000 instructions, then turn on the
tracing of all instruction execution, register modification
and memory accesses".)

thanks
-- PMM