From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55569) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ehdgH-00040V-E2 for qemu-devel@nongnu.org; Fri, 02 Feb 2018 10:59:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ehdfD-0002b7-F9 for qemu-devel@nongnu.org; Fri, 02 Feb 2018 10:55:13 -0500 Received: from mail-ot0-x230.google.com ([2607:f8b0:4003:c0f::230]:35406) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ehdfC-0002aU-QL for qemu-devel@nongnu.org; Fri, 02 Feb 2018 10:54:07 -0500 Received: by mail-ot0-x230.google.com with SMTP id a2so9324004otf.2 for ; Fri, 02 Feb 2018 07:54:06 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20180202100843.GD13090@stefanha-x1.localdomain> References: <20180202100843.GD13090@stefanha-x1.localdomain> From: Peter Maydell Date: Fri, 2 Feb 2018 15:53:45 +0000 Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] Qemu Trace List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Nesrine Zouari , QEMU Developers , =?UTF-8?Q?Llu=C3=ADs_Vilanova?= On 2 February 2018 at 10:08, Stefan Hajnoczi wrote: > On Thu, Feb 01, 2018 at 04:30:10PM +0100, Nesrine Zouari wrote: >> I am a computer engineering student and I am actually working on my >> graduation project at Lauterbach company. The project is about Qemu Trac= e >> and as a future I would like to contribute this work to the main line. >> >> My project is divided into two parts: >> >> 1/ Collecting the Guest trace data : The trace solution should be able t= o >> provide: >> >> a/ Instruction flow Trace >> >> b/ Memory read/write access >> >> c/ Time Stamps. >> >> d/ For tracing rich operating systems that are using MMU, we >> additionally need to trace the task switches. > > Llu=C3=ACs has done the most instrumentation work in qemu.git and can exp= lain > the current status. I think at the moment the status is that we're still discussing what the trace plugin API should be... there are some mailing list threads on the subject from I think last year some time. thanks -- PMM