From: Avi Kivity <avi@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 0/2] kvmtrace: Allow user to clean up stale trace setup
Date: Sun, 26 Oct 2008 16:15:15 +0200 [thread overview]
Message-ID: <49047B73.9000900@redhat.com> (raw)
In-Reply-To: <1224696928-22187-1-git-send-email-ehabkost@redhat.com>
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
prev parent reply other threads:[~2008-10-26 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 17:35 [PATCH 0/2] kvmtrace: Allow user to clean up stale trace setup Eduardo Habkost
2008-10-22 17:35 ` [PATCH 1/2] Extract disable_trace() from cleanup_trace() Eduardo Habkost
2008-10-22 17:35 ` [PATCH 2/2] kvmtrace: Add -f option to clean up existing trace setup Eduardo Habkost
2008-10-22 17:42 ` [PATCH 0/2] kvmtrace: Allow user to clean up stale " Glauber Costa
2008-10-22 17:54 ` Eduardo Habkost
2008-10-22 18:05 ` Glauber Costa
2008-10-22 18:24 ` Eduardo Habkost
2008-10-26 14:15 ` Avi Kivity [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49047B73.9000900@redhat.com \
--to=avi@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.