From: George Dunlap <george.dunlap@citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 02/16] xen: sched: move up the trace record for vcpu_wake and vcpu_sleep
Date: Thu, 18 Feb 2016 10:34:59 +0000 [thread overview]
Message-ID: <56C59E53.7070600@citrix.com> (raw)
In-Reply-To: <20160216181121.27876.65964.stgit@Solace.station>
On 16/02/16 18:11, Dario Faggioli wrote:
> vcpu_wake() and vcpu_sleep() are called before the specific
> schedulers wakeup and sleep routines (in fact, it is them
> that calls those specific routine).
>
> Make the trace reflect that, by moving the records up. In
> fact, it is more natural and easy to find the record of
> the event (e.g., the wakeup) *before* the records of the
> actions that deals with the event itself.
>
> Signed-off-by: Dario Faggioli <dario.faggioli@citrix.com>
> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Acked-by: George Dunlap <george.dunlap@citrix.com>
> ---
> Cc: George Dunlap <george.dunlap@citrix.com>
> ---
> xen/common/schedule.c | 16 ++++++++++------
> 1 file changed, 10 insertions(+), 6 deletions(-)
>
> diff --git a/xen/common/schedule.c b/xen/common/schedule.c
> index 7306d71..c87922f 100644
> --- a/xen/common/schedule.c
> +++ b/xen/common/schedule.c
> @@ -381,7 +381,11 @@ void sched_destroy_domain(struct domain *d)
> void vcpu_sleep_nosync(struct vcpu *v)
> {
> unsigned long flags;
> - spinlock_t *lock = vcpu_schedule_lock_irqsave(v, &flags);
> + spinlock_t *lock;
> +
> + TRACE_2D(TRC_SCHED_SLEEP, v->domain->domain_id, v->vcpu_id);
> +
> + lock = vcpu_schedule_lock_irqsave(v, &flags);
>
> if ( likely(!vcpu_runnable(v)) )
> {
> @@ -392,8 +396,6 @@ void vcpu_sleep_nosync(struct vcpu *v)
> }
>
> vcpu_schedule_unlock_irqrestore(lock, flags, v);
> -
> - TRACE_2D(TRC_SCHED_SLEEP, v->domain->domain_id, v->vcpu_id);
> }
>
> void vcpu_sleep_sync(struct vcpu *v)
> @@ -409,7 +411,11 @@ void vcpu_sleep_sync(struct vcpu *v)
> void vcpu_wake(struct vcpu *v)
> {
> unsigned long flags;
> - spinlock_t *lock = vcpu_schedule_lock_irqsave(v, &flags);
> + spinlock_t *lock;
> +
> + TRACE_2D(TRC_SCHED_WAKE, v->domain->domain_id, v->vcpu_id);
> +
> + lock = vcpu_schedule_lock_irqsave(v, &flags);
>
> if ( likely(vcpu_runnable(v)) )
> {
> @@ -424,8 +430,6 @@ void vcpu_wake(struct vcpu *v)
> }
>
> vcpu_schedule_unlock_irqrestore(lock, flags, v);
> -
> - TRACE_2D(TRC_SCHED_WAKE, v->domain->domain_id, v->vcpu_id);
> }
>
> void vcpu_unblock(struct vcpu *v)
>
next prev parent reply other threads:[~2016-02-18 10:35 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 18:11 [PATCH v2 00/16] Scheduling related tracing improvements Dario Faggioli
2016-02-16 18:11 ` [PATCH v2 01/16] xen: sched: __runq_tickle takes a useless cpu parameter Dario Faggioli
2016-02-18 10:33 ` George Dunlap
2016-02-16 18:11 ` [PATCH v2 02/16] xen: sched: move up the trace record for vcpu_wake and vcpu_sleep Dario Faggioli
2016-02-18 10:34 ` George Dunlap [this message]
2016-02-16 18:11 ` [PATCH v2 03/16] xen: sched: improve domain creation tracing Dario Faggioli
2016-02-18 11:04 ` George Dunlap
2016-02-24 11:21 ` Dario Faggioli
2016-02-24 11:52 ` Jan Beulich
2016-02-24 13:20 ` Dario Faggioli
2016-02-16 18:11 ` [PATCH v2 04/16] xen: credit2: pack trace data better for xentrace_format Dario Faggioli
2016-02-18 11:10 ` George Dunlap
2016-02-18 13:42 ` Dario Faggioli
2016-02-16 18:11 ` [PATCH v2 05/16] xen: RTDS: " Dario Faggioli
2016-02-18 11:12 ` George Dunlap
2016-02-18 14:43 ` Meng Xu
2016-02-16 18:11 ` [PATCH v2 06/16] xen: sched: tracing: enable TSC tracing for all events Dario Faggioli
2016-02-16 18:21 ` Meng Xu
2016-02-17 9:52 ` Dario Faggioli
2016-02-17 15:26 ` Meng Xu
2016-02-18 11:43 ` George Dunlap
2016-02-18 16:52 ` Dario Faggioli
2016-02-22 11:02 ` George Dunlap
2016-02-16 18:12 ` [PATCH v2 07/16] xentrace: formats: update format of scheduling events Dario Faggioli
2016-02-18 12:28 ` George Dunlap
2016-02-16 18:12 ` [PATCH v2 08/16] xentrace: formats: add events from Credit scheduler Dario Faggioli
2016-02-16 18:12 ` [PATCH v2 09/16] xentrace: formats: add events from Credit2 scheduler Dario Faggioli
2016-02-16 18:12 ` [PATCH v2 10/16] xentrace: formats: add events from RTDS scheduler Dario Faggioli
2016-02-16 18:12 ` [PATCH v2 11/16] xentrace: formats: add domain create and destroy events Dario Faggioli
2016-02-16 18:12 ` [PATCH v2 12/16] xenalyze: handle scheduling events Dario Faggioli
2016-02-18 15:18 ` George Dunlap
2016-02-16 18:12 ` [PATCH v2 13/16] xenalyze: handle Credit1 scheduler events Dario Faggioli
2016-02-18 15:28 ` George Dunlap
2016-02-18 15:31 ` George Dunlap
2016-02-18 16:58 ` Dario Faggioli
2016-02-16 18:13 ` [PATCH v2 14/16] xenalyze: handle Credit2 " Dario Faggioli
2016-02-18 15:17 ` George Dunlap
2016-02-16 18:13 ` [PATCH v2 15/16] xenalyze: handle RTDS " Dario Faggioli
2016-02-18 15:28 ` George Dunlap
2016-02-18 17:02 ` Dario Faggioli
2016-02-18 17:06 ` George Dunlap
2016-02-18 17:10 ` Dario Faggioli
2016-02-16 18:13 ` [PATCH v2 16/16] xenalyze: handle DOM0 operaions events Dario Faggioli
2016-03-04 18:25 ` [PATCH v2 00/16] Scheduling related tracing improvements Dario Faggioli
2016-03-04 19:52 ` Konrad Rzeszutek Wilk
2016-03-07 10:50 ` Jan Beulich
2016-03-07 10:54 ` Wei Liu
2016-03-07 11:21 ` Jan Beulich
2016-03-07 11:27 ` Wei Liu
2016-03-07 14:21 ` Dario Faggioli
2016-03-07 15:36 ` Konrad Rzeszutek Wilk
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=56C59E53.7070600@citrix.com \
--to=george.dunlap@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).