linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yogesh Tillu <yogesh.tillu@linaro.org>
To: linux-arm-kernel@lists.infradead.org
Cc: tillu.yogesh@gmail.com, linux-perf-users@vger.kernel.org,
	linaro-networking@linaro.org, jean.pihet@linaro.org,
	arnd@linaro.org, Andrew.Pinski@caviumnetworks.com,
	mike.holmes@linaro.org, ola.liljedahl@linaro.org,
	magnus.karlsson@avagotech.com, Prasun.Kapoor@caviumnetworks.com,
	Yogesh Tillu <yogesh.tillu@linaro.org>
Subject: [RFC PATCH 5/5] Application: to read PMU counter through vdso
Date: Mon,  3 Nov 2014 20:34:05 +0530	[thread overview]
Message-ID: <1415027045-6573-6-git-send-email-yogesh.tillu@linaro.org> (raw)
In-Reply-To: <1415027045-6573-1-git-send-email-yogesh.tillu@linaro.org>

Test application to read PMU cycle counter through vDSO path. 

Signed-off-by: Yogesh Tillu <yogesh.tillu@linaro.org>

---
 vdso_userspace_perf.c |   58 +++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 58 insertions(+)
 create mode 100644 vdso_userspace_perf.c

diff --git a/vdso_userspace_perf.c b/vdso_userspace_perf.c
new file mode 100644
index 0000000..42d2682
--- /dev/null
+++ b/vdso_userspace_perf.c
@@ -0,0 +1,58 @@
+#include <stdio.h>
+#include <stdint.h>
+#include <stdlib.h>
+#include <sys/time.h>
+/* Simple loop body to keep things interested. Make sure it gets inlined. */
+static inline int
+loop(int* __restrict__ a, int* __restrict__ b, int n)
+{
+	unsigned sum = 0;
+	for (int i = 0; i < n; ++i)
+		if(a[i] > b[i])
+			sum += a[i] + 5;
+	return sum;
+}
+
+int
+main(int ac, char **av)
+{
+	uint32_t time_start = 0;
+	uint32_t time_end   = 0;
+	int result=0;
+	int *a  = NULL;
+	int *b  = NULL;
+	int len = 0;
+	int sum = 0;
+	int i;
+	struct timeval tv;
+
+	if (ac != 2) return -1;
+	len = atoi(av[1]);
+
+	a = malloc(len*sizeof(*a));
+	b = malloc(len*sizeof(*b));
+
+	for (int i = 0; i < len; ++i) {
+		a[i] = i+128;
+		b[i] = i+64;
+	}
+/* Read Counter  with Busy loop */
+	perf_open_counter();
+	time_start = perf_read_counter();
+	sum = loop(a, b, len);
+	time_end   = perf_read_counter();
+	printf("**********************************************************************\n");
+	printf("Busyloop sum = %d\nTime delta Including Busyloop = %lu [clockcycle]\n", sum, time_end - time_start);
+
+/* Read Counter with profiling read_counter */
+	time_start = perf_read_counter();
+	perf_read_counter();
+	time_end   = perf_read_counter();
+	printf("\nTime delta Without Busyloop   = %lu   [clockcycle]\n", time_end - time_start);
+	printf("**********************************************************************\n");
+
+	free(a); free(b);
+	return 0;
+cleanup: 
+	return -1;
+}
-- 
1.7.9.5

  parent reply	other threads:[~2014-11-03 15:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 15:04 [RFC] ARM64: Accessing perf counters from userspace Yogesh Tillu
2014-11-03 15:04 ` [RFC PATCH 1/5] Application: reads perf cycle counter using perf_event_open syscall Yogesh Tillu
2014-11-03 15:04 ` [RFC PATCH 2/5] Kernel module: to Enable userspace access to PMU counters for ArmV8 Yogesh Tillu
2014-11-03 15:22   ` Måns Rullgård
2014-11-03 16:16   ` Mark Rutland
2014-11-03 15:04 ` [RFC PATCH 3/5] Application: Added test for Direct access of perf counter from userspace using asm Yogesh Tillu
2014-11-03 15:04 ` [RFC PATCH 4/5]ARM64: Kernel: To read PMU cycle counter through vDSO Path Yogesh Tillu
2014-11-03 16:13   ` Mark Rutland
2014-11-03 15:04 ` Yogesh Tillu [this message]
2014-11-03 15:40 ` [RFC] ARM64: Accessing perf counters from userspace Mark Rutland
2014-11-04 18:32   ` Yogesh Tillu
     [not found]     ` <CAPiYAf4ZbEP20AEaEyaDJ9ov-w-F-UNDu9OmurL_3YQx+9p5bA@mail.gmail.com>
2014-11-05 17:39       ` Mark Rutland

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=1415027045-6573-6-git-send-email-yogesh.tillu@linaro.org \
    --to=yogesh.tillu@linaro.org \
    --cc=Andrew.Pinski@caviumnetworks.com \
    --cc=Prasun.Kapoor@caviumnetworks.com \
    --cc=arnd@linaro.org \
    --cc=jean.pihet@linaro.org \
    --cc=linaro-networking@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=magnus.karlsson@avagotech.com \
    --cc=mike.holmes@linaro.org \
    --cc=ola.liljedahl@linaro.org \
    --cc=tillu.yogesh@gmail.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;
as well as URLs for NNTP newsgroup(s).