From: "Emilio G. Cota" <cota@braap.org>
To: "Lluís Vilanova" <vilanova@ac.upc.edu>
Cc: qemu-devel@nongnu.org, stefanha@gmail.com,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] trace: Immediately apply per-vCPU state changes if a vCPU is being created
Date: Wed, 6 Sep 2017 18:24:48 -0400 [thread overview]
Message-ID: <20170906222448.GA21183@flamenco> (raw)
In-Reply-To: <150471163020.18882.9386672218918089445.stgit@frigg.lan>
On Wed, Sep 06, 2017 at 18:27:10 +0300, Lluís Vilanova wrote:
> Right now, function trace_event_set_vcpu_state_dynamic() asynchronously enables
> events in the case a vCPU is executing TCG code. If the vCPU is being created
> this makes some events like "guest_cpu_enter" to not be traced.
>
> Signed-off-by: Lluís Vilanova <vilanova@ac.upc.edu>
> ---
> trace/control-target.c | 19 ++++++++++++-------
> 1 file changed, 12 insertions(+), 7 deletions(-)
>
> diff --git a/trace/control-target.c b/trace/control-target.c
> index 4e36101997..0056da6a46 100644
> --- a/trace/control-target.c
> +++ b/trace/control-target.c
> @@ -88,13 +88,18 @@ void trace_event_set_vcpu_state_dynamic(CPUState *vcpu,
> clear_bit(vcpu_id, vcpu->trace_dstate_delayed);
> (*ev->dstate)--;
> }
> - /*
> - * Delay changes until next TB; we want all TBs to be built from a
> - * single set of dstate values to ensure consistency of generated
> - * tracing code.
> - */
> - async_run_on_cpu(vcpu, trace_event_synchronize_vcpu_state_dynamic,
> - RUN_ON_CPU_NULL);
> + if (vcpu->created) {
> + /*
> + * Delay changes until next TB; we want all TBs to be built from a
> + * single set of dstate values to ensure consistency of generated
> + * tracing code.
> + */
> + async_run_on_cpu(vcpu, trace_event_synchronize_vcpu_state_dynamic,
> + RUN_ON_CPU_NULL);
> + } else {
> + run_on_cpu_data ignored;
> + trace_event_synchronize_vcpu_state_dynamic(vcpu, ignored);
I'd prefer RUN_ON_CPU_NULL here instead of the ignored param.
Other than that,
Reviewed-by: Emilio G. Cota <cota@braap.org>
E.
prev parent reply other threads:[~2017-09-06 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 15:27 [Qemu-devel] [PATCH] trace: Immediately apply per-vCPU state changes if a vCPU is being created Lluís Vilanova
2017-09-06 22:24 ` Emilio G. Cota [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=20170906222448.GA21183@flamenco \
--to=cota@braap.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.com \
--cc=vilanova@ac.upc.edu \
/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;
as well as URLs for NNTP newsgroup(s).