qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Lluís Vilanova" <vilanova@ac.upc.edu>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/2] trace: Add "vcpu_init" event
Date: Wed, 21 Sep 2011 09:21:26 +0200	[thread overview]
Message-ID: <4E799076.8050501@siemens.com> (raw)
In-Reply-To: <20110920190601.31721.9457.stgit@ginnungagap.bsc.es>

On 2011-09-20 21:06, Lluís Vilanova wrote:
> Signals the creation of a new vCPU (CPUState structure).
> 
> Signed-off-by: Lluís Vilanova <vilanova@ac.upc.edu>
> ---
>  cpus.c        |    1 +
>  qemu-common.h |    4 +++-
>  trace-events  |    7 +++++++
>  3 files changed, 11 insertions(+), 1 deletions(-)
> 
> diff --git a/cpus.c b/cpus.c
> index 54c188c..ab699bb 100644
> --- a/cpus.c
> +++ b/cpus.c
> @@ -861,6 +861,7 @@ void qemu_init_vcpu(void *_env)
>      } else {
>          qemu_tcg_init_vcpu(env);
>      }
> +    trace_vcpu_init(env);
>  }
>  
>  void qemu_notify_event(void)
> diff --git a/qemu-common.h b/qemu-common.h
> index 404c421..511f0c7 100644
> --- a/qemu-common.h
> +++ b/qemu-common.h
> @@ -296,8 +296,10 @@ struct qemu_work_item {
>      int done;
>  };
>  
> +#include "trace.h"
> +
>  #ifdef CONFIG_USER_ONLY
> -#define qemu_init_vcpu(env) do { } while (0)
> +#define qemu_init_vcpu(env) do { trace_vcpu_init(env); } while (0)

As you are already at it, please make this a proper static inline
instead of a macro.

Both patches look good otherwise.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

      parent reply	other threads:[~2011-09-21  7:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20 19:06 [Qemu-devel] [PATCH 1/2] trace: Add "vcpu_init" event Lluís Vilanova
2011-09-20 19:06 ` [Qemu-devel] [PATCH 2/2] trace: Add "vcpu_reset" event Lluís Vilanova
2011-09-21  7:21 ` Jan Kiszka [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=4E799076.8050501@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).