From: Anton Blanchard <anton@samba.org>
To: Will Schmidt <will_schmidt@vnet.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
mingo@redhat.com, Steven Rostedt <rostedt@goodmis.org>
Subject: Re: hypervisor call tracepoints hcall_stats touchup.
Date: Thu, 26 Nov 2009 14:28:22 +1100 [thread overview]
Message-ID: <20091126032822.GS32182@kryten> (raw)
In-Reply-To: <1259165529.16349.191.camel@lexx>
Hi Will,
> The tb_total and purr_total values reported via the hcall_stats code
> should be cumulative, rather than being replaced by the latest delta tb
> or purr value.
>
> Tested-by: Will Schmidt <will_schmidt@vnet.ibm.com>
> Signed-off-by: Will Schmidt <will_schmidt@vnet.ibm.com>
Ouch! Nice catch.
Acked-by: Anton Blanchard <anton@samba.org>
Anton
> [ This is a touch-up to the "[3/6] powerpc: tracing: Add hypervisor call
> tracepoints" patch submitted by Anton a few weeks back, so I've copied
> folks Anton had on CC for his original patch, this fix is rather ppc
> specific, so can probably go in via the ppc tree, but I've no real
> preference. ]
>
> diff --git a/arch/powerpc/platforms/pseries/hvCall_inst.c b/arch/powerpc/platforms/pseries/hvCall_inst.c
> index 2f58c71..1fefae7 100644
> --- a/arch/powerpc/platforms/pseries/hvCall_inst.c
> +++ b/arch/powerpc/platforms/pseries/hvCall_inst.c
> @@ -124,8 +124,8 @@ static void probe_hcall_exit(unsigned long opcode, unsigned long retval,
>
> h = &__get_cpu_var(hcall_stats)[opcode / 4];
> h->num_calls++;
> - h->tb_total = mftb() - h->tb_start;
> - h->purr_total = mfspr(SPRN_PURR) - h->purr_start;
> + h->tb_total += mftb() - h->tb_start;
> + h->purr_total += mfspr(SPRN_PURR) - h->purr_start;
>
> put_cpu_var(hcall_stats);
> }
>
prev parent reply other threads:[~2009-11-26 3:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 16:12 hypervisor call tracepoints hcall_stats touchup Will Schmidt
2009-11-25 21:19 ` Steven Rostedt
2009-11-30 15:17 ` Will Schmidt
2009-11-26 3:28 ` Anton Blanchard [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=20091126032822.GS32182@kryten \
--to=anton@samba.org \
--cc=fweisbec@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=will_schmidt@vnet.ibm.com \
/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