From: Eduardo Habkost <ehabkost@redhat.com>
To: Glauber Costa <glommer@gmail.com>
Cc: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 0/2] kvmtrace: Allow user to clean up stale trace setup
Date: Wed, 22 Oct 2008 15:54:54 -0200 [thread overview]
Message-ID: <20081022175454.GM27959@blackpad> (raw)
In-Reply-To: <5d6222a80810221042n44684c1fpdd5ea3f8cadb88db@mail.gmail.com>
On Wed, Oct 22, 2008 at 03:42:27PM -0200, Glauber Costa wrote:
> On Wed, Oct 22, 2008 at 3:35 PM, Eduardo Habkost <ehabkost@redhat.com> 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
next prev parent reply other threads:[~2008-10-22 17:55 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 [this message]
2008-10-22 18:05 ` Glauber Costa
2008-10-22 18:24 ` Eduardo Habkost
2008-10-26 14:15 ` Avi Kivity
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=20081022175454.GM27959@blackpad \
--to=ehabkost@redhat.com \
--cc=avi@redhat.com \
--cc=glommer@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox