Eduardo Habkost wrote:
If kvmtrace crashes or gets killed while collecting trace data, stale
trace setup information may be enabled on the kernel, and currently
there is no way to force the previous trace setup to be overwritten
or disabled.
The following two patches against kvm-userspace will add a new
command-line option to kvmtrace (-f), that will allow the user to forcibly
clean up an existing trace setup before enabling trace.
The long term plan is to drop kvmtrace in favor of the more generic
frameworks (which provide a common trace transport, IIRC). Can you
check if this has been merged (or if enough of it is in mainline)?
This is exactly the sort of issues that are best handled by a generic
implementation.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
