qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Benchmarking activities


From: Andreas Färber
Subject: Re: [Qemu-devel] Benchmarking activities
Date: Sat, 2 Jul 2011 17:46:34 +0200

Am 02.07.2011 um 10:32 schrieb Stefan Hajnoczi:

On Fri, Jul 1, 2011 at 8:32 PM, Blue Swirl <address@hidden> wrote:
2011/6/27 Ben Vogler <address@hidden>:
- Are there any inbuilt data tracing features? For example,
hardware signal tracing, register monitoring etc.

Tracing is quite new addition, so far it's only used for development
or debugging QEMU point of view I think.

I think you are referring to hardware model debugging and logging.
The QEMU "tracing" mechanism that Blue Swirl mentioned is a
DTrace/SystemTap style tool for observing QEMU internals and not what
you are looking for.

I believe Lluís (cc'ed) has worked on using/extending the trace framework to instrument guests.

QEMU has a built-in GDB server, so you can debug your code and inspect registers. The QEMU monitor is another way to inspect registers beyond those shown in GDB.

Andreas


reply via email to

[Prev in Thread] Current Thread [Next in Thread]