On Wed, Oct 22, 2008 at 03:42:27PM -0200, Glauber Costa wrote: > On Wed, Oct 22, 2008 at 3:35 PM, Eduardo Habkost <[EMAIL PROTECTED]> 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. > > Why can't we simply disable potential stale setups everytime, before we start? > The option would then not be needed
Another kvmtrace instance may be already running. Do we want to kill its tracing setup without asking, by default? -- Eduardo -- 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
