summaryrefslogtreecommitdiff
path: root/drivers/oprofile
diff options
context:
space:
mode:
authorMaynard Johnson <maynardj@us.ibm.com>2009-05-27 19:15:08 +0400
committerIngo Molnar <mingo@elte.hu>2009-07-10 14:35:36 +0400
commit2b8777ca0c944bf6498c45ed9c5c246bd63a719e (patch)
treefb62bd8d92828d6c1e6b66cc1cbb1bd49f0a19fc /drivers/oprofile
parent8d7ff4f2a0b22b7d6d7bc3982257d1dadea22824 (diff)
downloadlinux-2b8777ca0c944bf6498c45ed9c5c246bd63a719e.tar.xz
oprofile: reset bt_lost_no_mapping with other stats
The bt_lost_no_mapping is not getting reset at the start of a profiling run, thus the oprofiled.log shows erroneous values for this statistic. The attached patch fixes this problem. Signed-off-by: Maynard Johnson <maynardj@us.ibm.com> Signed-off-by: Robert Richter <robert.richter@amd.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'drivers/oprofile')
-rw-r--r--drivers/oprofile/oprofile_stats.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/oprofile/oprofile_stats.c b/drivers/oprofile/oprofile_stats.c
index e1f6ce03705e..3c2270a8300c 100644
--- a/drivers/oprofile/oprofile_stats.c
+++ b/drivers/oprofile/oprofile_stats.c
@@ -33,6 +33,7 @@ void oprofile_reset_stats(void)
atomic_set(&oprofile_stats.sample_lost_no_mm, 0);
atomic_set(&oprofile_stats.sample_lost_no_mapping, 0);
atomic_set(&oprofile_stats.event_lost_overflow, 0);
+ atomic_set(&oprofile_stats.bt_lost_no_mapping, 0);
}