read target long size for page size

The ring buffer page uses local_t to keep track of the size of data
held on an individual page. local_t is a long which means that it is
either 4 bytes on a 32bit box, or 8bytes on a 64bit box.

The code must be able to cope with this difference.

Signed-off-by: Steven Rostedt <srostedt@redhat.com>

1 files changed, 12 insertions, 2 deletions

diff --git a/trace-read.c b/trace-read.c
index fd8e206..ffb1374 100644
--- a/trace-read.c
+++ b/trace-read.c
@@ -388,8 +388,18 @@ struct record *peak_data(int cpu)
                 /* FIXME: handle header page */
                 cpu_data[cpu].timestamp = data2host8(ptr);
                 ptr += 8;
-                cpu_data[cpu].page_size = data2host8(ptr);
-                ptr += 8;
+                switch (long_size) {
+                case 4:
+                        cpu_data[cpu].page_size = data2host4(ptr);
+                        ptr += 4;
+                        break;
+                case 8:
+                        cpu_data[cpu].page_size = data2host8(ptr);
+                        ptr += 8;
+                        break;
+                default:
+                        die("bad long size");
+                }
         }
 
 read_again: