On Thu, Oct 21, 2010 at 07:20:27AM +0200, Christoph Hellwig wrote:
On Tue, Oct 19, 2010 at 03:29:51PM +0100, Richard W.M. Jones wrote:
On Tue, Oct 19, 2010 at 03:59:36PM +0200, Jan Kiszka wrote:
Once we have -trace events=..., defining the list of active
tracepoints before starting qemu
On Thu, Oct 21, 2010 at 6:20 AM, Christoph Hellwig h...@lst.de wrote:
On Tue, Oct 19, 2010 at 03:29:51PM +0100, Richard W.M. Jones wrote:
On Tue, Oct 19, 2010 at 03:59:36PM +0200, Jan Kiszka wrote:
Once we have -trace events=..., defining the list of active
tracepoints before starting qemu
On Tue, Oct 19, 2010 at 03:29:51PM +0100, Richard W.M. Jones wrote:
On Tue, Oct 19, 2010 at 03:59:36PM +0200, Jan Kiszka wrote:
Once we have -trace events=..., defining the list of active
tracepoints before starting qemu will be trivial (e.g. via a config
file). Of course, this requires
On Tue, Oct 19, 2010 at 03:29:51PM +0100, Richard W.M. Jones wrote:
On Tue, Oct 19, 2010 at 03:59:36PM +0200, Jan Kiszka wrote:
Once we have -trace events=..., defining the list of active
tracepoints before starting qemu will be trivial (e.g. via a config
file). Of course, this requires
On Tue, Oct 19, 2010 at 03:59:36PM +0200, Jan Kiszka wrote:
Once we have -trace events=..., defining the list of active
tracepoints before starting qemu will be trivial (e.g. via a config
file). Of course, this requires that all tracepoints are built-in...
Sorry that I've not been following
On Tue, Oct 19, 2010 at 03:29:51PM +0100, Richard W.M. Jones wrote:
On Tue, Oct 19, 2010 at 03:59:36PM +0200, Jan Kiszka wrote:
Once we have -trace events=..., defining the list of active
tracepoints before starting qemu will be trivial (e.g. via a config
file). Of course, this requires
