From: Luming Yu <luming.yu@gmail.com>
To: arnd@arndb.de, linux-kernel@vger.kernel.org
Cc: Luming Yu <luming.yu@gmail.com>, Luming Yu <luming.yu@intel.com>
Subject: [PATCH 08/13] HW-latency: A stupid memory scanner for raw memory latency test
Date: Sun, 4 Nov 2012 20:59:39 -0500 [thread overview]
Message-ID: <1352080784-30839-9-git-send-email-luming.yu@gmail.com> (raw)
In-Reply-To: <1352080784-30839-1-git-send-email-luming.yu@gmail.com>
It's simple memory latency test without any consideration of memory
hierarchy and memory model. It just does simply scan byte by byte.
Signed-off-by: Luming Yu <luming.yu@intel.com>
---
drivers/misc/hw_latency_test.c | 53 ++++++++++++++++++++++++++++++++++++++++--
1 file changed, 51 insertions(+), 2 deletions(-)
diff --git a/drivers/misc/hw_latency_test.c b/drivers/misc/hw_latency_test.c
index 78436da..f47b911 100644
--- a/drivers/misc/hw_latency_test.c
+++ b/drivers/misc/hw_latency_test.c
@@ -46,11 +46,15 @@ static DEFINE_MUTEX(ring_buffer_mutex);
static unsigned long buf_size = 262144UL;
static struct task_struct *kthread;
+static u8 *__start = (u8 *)0xffff880000000000;
+static u8 *__end = (u8 *)0xffffc7ffffffffff;
+
struct sample {
unsigned int cpu;
u64 seqnum;
u64 duration;
struct timespec timestamp;
+ u64 addr;
unsigned long lost;
};
@@ -134,6 +138,7 @@ static int buffer_add_sample(u64 sample)
s.seqnum = data.count;
s.duration = sample;
s.timestamp = CURRENT_TIME;
+ s.addr = (u64) __start;
ret = __buffer_add_sample(&s);
if (sample > data.max_sample)
@@ -247,6 +252,42 @@ out:
return ret;
}
+static int get_mem_sample(void *unused)
+{
+ ktime_t start, t1, t2;
+ s64 diff, total = 0;
+ u64 sample = 0;
+ int ret = 1;
+ u8 temp;
+
+ now = start = ktime_get();
+ do {
+ t1 = now;
+ now = t2 = ktime_get();
+
+ total = ktime_to_ns(ktime_sub(t2, start));
+ temp = *__start++;
+ diff = ktime_to_ns(ktime_sub(t2, t1));
+
+ if (diff < 0) {
+ printk(KERN_ERR BANNER "time running backwards\n");
+ goto out;
+ }
+
+ if (diff > sample)
+ sample = diff;
+
+ if (__start == __end) {
+ __start = (u8 *)0xffff880000000000;
+ printk(KERN_INFO BANNER "one pass finished, jmp to the beginning\n");
+ }
+
+ } while (total <= data.sample_width);
+
+ ret = buffer_add_sample(sample);
+out:
+ return ret;
+}
struct sample_function tsc_sample = {
.name = "tsc",
@@ -266,6 +307,12 @@ struct sample_function random_bytes_sample = {
.get_sample = get_random_bytes_sample,
};
+struct sample_function mem_sample = {
+ .name = "mem",
+ .type = 1,
+ .get_sample = get_mem_sample,
+};
+
static DECLARE_BITMAP(testing_cpu_map, NR_CPUS);
static int kthread_fn(void *unused)
@@ -617,11 +664,12 @@ static ssize_t debug_sample_fread(struct file *filp, char __user *ubuf,
goto out;
}
}
- len = snprintf(buf, sizeof(buf), "[%d]%010lu.%010lu\t%llu\n",
+ len = snprintf(buf, sizeof(buf), "[%d]%010lu.%010lu\t%llu\t[%llx]\n",
sample->cpu,
sample->timestamp.tv_sec,
sample->timestamp.tv_nsec,
- sample->duration);
+ sample->duration,
+ sample->addr);
if (len > cnt)
goto out;
if (copy_to_user(ubuf, buf,len))
@@ -827,6 +875,7 @@ static int hw_test_init(void)
sample_function_register(&tsc_sample);
sample_function_register(&tsc_freq_sample);
sample_function_register(&random_bytes_sample);
+ sample_function_register(&mem_sample);
ret = init_stats();
if (0 != ret)
--
1.7.12.1
next prev parent reply other threads:[~2012-11-04 13:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 1:59 [PATCH 00/13] A simple hardware detector for latency as well as throughtput ver 0.10 Luming Yu
2012-11-05 1:59 ` [PATCH 01/13] HW-latency: hardware latency test 0.10 Luming Yu
2012-11-04 21:07 ` Maarten Lankhorst
2012-11-05 12:14 ` Luming Yu
2012-11-04 21:23 ` John Kacur
2012-11-05 12:20 ` Luming Yu
2012-11-05 8:44 ` No recipient
2012-11-05 8:44 ` Ove Karlsen
2012-11-05 1:59 ` [PATCH 02/13] HW-latency: Fix a lockdep warnning Luming Yu
2012-11-05 1:59 ` [PATCH 03/13] HW-latency: Use get_random_bytes_arch Luming Yu
2012-11-05 1:59 ` [PATCH 04/13] HW-latency: Differentiate three modes to use CPU carry out testing Luming Yu
2012-11-05 1:59 ` [PATCH 05/13] HW-latency: Add CPU field in sample output Luming Yu
2012-11-05 1:59 ` [PATCH 06/13] HW-latency: cycle through all online cpus to re-test cpufreq Luming Yu
2012-11-05 1:59 ` [PATCH 07/13] HW-latency: delete too many "Fast TSC calibration using PIT" in cpufreq sampling Luming Yu
2012-11-05 1:59 ` Luming Yu [this message]
2012-11-05 1:59 ` [PATCH 09/13] HW-latency: Fix unwanted crash caused by write to dummy debugfs interface Luming Yu
2012-11-05 1:59 ` [PATCH 10/13] HW-latency: add address range for x86-32 Luming Yu
2012-11-05 1:59 ` [PATCH 11/13] HW-latency: fix a warnning in previous patch Luming Yu
2012-11-05 1:59 ` [PATCH 12/13] HW-latency: Add sample unit in sample data Luming Yu
2012-11-05 1:59 ` [PATCH 13/13] HW-latency: some sample data format change Luming Yu
2012-11-08 16:04 ` [PATCH 00/13] A simple hardware detector for latency as well as throughtput ver 0.10 Theodore Ts'o
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=1352080784-30839-9-git-send-email-luming.yu@gmail.com \
--to=luming.yu@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.