Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
/*
|
|
|
|
* This file is part of the coreboot project.
|
|
|
|
*
|
2013-07-17 02:47:35 +02:00
|
|
|
* Copyright 2012 Google Inc.
|
2015-09-06 01:07:17 +02:00
|
|
|
* Copyright (C) 2015 Timothy Pearson <tpearson@raptorengineeringinc.com>, Raptor Engineering
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
* the Free Software Foundation; version 2 of the License.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
*/
|
|
|
|
|
2013-05-26 18:17:54 +02:00
|
|
|
#include <inttypes.h>
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
#include <stdio.h>
|
|
|
|
#include <stdlib.h>
|
|
|
|
#include <string.h>
|
2013-01-03 00:43:56 +01:00
|
|
|
#include <unistd.h>
|
2013-04-19 23:22:29 +02:00
|
|
|
#include <inttypes.h>
|
2013-01-03 00:43:56 +01:00
|
|
|
#include <getopt.h>
|
2014-06-17 08:02:03 +02:00
|
|
|
#include <dirent.h>
|
2013-01-03 23:30:33 +01:00
|
|
|
#include <errno.h>
|
|
|
|
#include <fcntl.h>
|
2013-07-17 02:47:35 +02:00
|
|
|
#include <ctype.h>
|
2013-06-20 00:39:09 +02:00
|
|
|
#include <arpa/inet.h>
|
2013-01-03 23:30:33 +01:00
|
|
|
#include <sys/types.h>
|
|
|
|
#include <sys/stat.h>
|
|
|
|
#include <sys/mman.h>
|
Implement GCC code coverage analysis
In order to provide some insight on what code is executed during
coreboot's run time and how well our test scenarios work, this
adds code coverage support to coreboot's ram stage. This should
be easily adaptable for payloads, and maybe even romstage.
See http://gcc.gnu.org/onlinedocs/gcc/Gcov.html for
more information.
To instrument coreboot, select CONFIG_COVERAGE ("Code coverage
support") in Kconfig, and recompile coreboot. coreboot will then
store its code coverage information into CBMEM, if possible.
Then, run "cbmem -CV" as root on the target system running the
instrumented coreboot binary. This will create a whole bunch of
.gcda files that contain coverage information. Tar them up, copy
them to your build system machine, and untar them. Then you can
use your favorite coverage utility (gcov, lcov, ...) to visualize
code coverage.
For a sneak peak of what will expect you, please take a look
at http://www.coreboot.org/~stepan/coreboot-coverage/
Change-Id: Ib287d8309878a1f5c4be770c38b1bc0bb3aa6ec7
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Reviewed-on: http://review.coreboot.org/2052
Tested-by: build bot (Jenkins)
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Martin Roth <martin@se-eng.com>
Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
2012-12-19 01:23:28 +01:00
|
|
|
#include <libgen.h>
|
|
|
|
#include <assert.h>
|
2015-09-08 20:34:43 +02:00
|
|
|
#include <commonlib/cbmem_id.h>
|
|
|
|
#include <commonlib/timestamp_serialized.h>
|
|
|
|
#include <commonlib/coreboot_tables.h>
|
2013-01-03 23:30:33 +01:00
|
|
|
|
2015-07-13 16:53:50 +02:00
|
|
|
#ifdef __OpenBSD__
|
|
|
|
#include <sys/param.h>
|
|
|
|
#include <sys/sysctl.h>
|
|
|
|
#endif
|
|
|
|
|
2013-01-03 23:30:33 +01:00
|
|
|
#define ARRAY_SIZE(a) (sizeof(a) / sizeof((a)[0]))
|
|
|
|
#define MAP_BYTES (1024*1024)
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
|
2014-06-17 08:02:03 +02:00
|
|
|
typedef uint8_t u8;
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
typedef uint16_t u16;
|
|
|
|
typedef uint32_t u32;
|
|
|
|
typedef uint64_t u64;
|
|
|
|
|
2013-07-17 02:47:35 +02:00
|
|
|
#define CBMEM_VERSION "1.1"
|
2013-01-03 00:43:56 +01:00
|
|
|
|
2013-01-03 23:30:33 +01:00
|
|
|
/* verbose output? */
|
|
|
|
static int verbose = 0;
|
|
|
|
#define debug(x...) if(verbose) printf(x)
|
|
|
|
|
|
|
|
/* File handle used to access /dev/mem */
|
2014-06-17 08:02:03 +02:00
|
|
|
static int mem_fd;
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
|
2015-09-30 19:33:01 +02:00
|
|
|
static uint64_t lbtable_address;
|
|
|
|
static size_t lbtable_size;
|
2015-05-16 21:55:54 +02:00
|
|
|
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
/*
|
|
|
|
* calculate ip checksum (16 bit quantities) on a passed in buffer. In case
|
|
|
|
* the buffer length is odd last byte is excluded from the calculation
|
|
|
|
*/
|
|
|
|
static u16 ipchcksum(const void *addr, unsigned size)
|
|
|
|
{
|
|
|
|
const u16 *p = addr;
|
|
|
|
unsigned i, n = size / 2; /* don't expect odd sized blocks */
|
|
|
|
u32 sum = 0;
|
|
|
|
|
|
|
|
for (i = 0; i < n; i++)
|
|
|
|
sum += p[i];
|
|
|
|
|
|
|
|
sum = (sum >> 16) + (sum & 0xffff);
|
|
|
|
sum += (sum >> 16);
|
|
|
|
sum = ~sum & 0xffff;
|
|
|
|
return (u16) sum;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2013-01-03 23:30:33 +01:00
|
|
|
* Functions to map / unmap physical memory into virtual address space. These
|
|
|
|
* functions always maps 1MB at a time and can only map one area at once.
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
*/
|
2013-01-03 23:30:33 +01:00
|
|
|
static void *mapped_virtual;
|
2014-03-31 18:59:58 +02:00
|
|
|
static size_t mapped_size;
|
|
|
|
|
|
|
|
static inline size_t size_to_mib(size_t sz)
|
|
|
|
{
|
|
|
|
return sz >> 20;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void unmap_memory(void)
|
|
|
|
{
|
|
|
|
if (mapped_virtual == NULL) {
|
|
|
|
fprintf(stderr, "Error unmapping memory\n");
|
|
|
|
return;
|
|
|
|
}
|
2015-05-16 21:55:54 +02:00
|
|
|
if (size_to_mib(mapped_size) == 0) {
|
|
|
|
debug("Unmapping %zuMB of virtual memory at %p.\n",
|
|
|
|
size_to_mib(mapped_size), mapped_virtual);
|
2015-09-06 01:07:17 +02:00
|
|
|
} else {
|
2015-05-16 21:55:54 +02:00
|
|
|
debug("Unmapping %zuMB of virtual memory at %p.\n",
|
|
|
|
size_to_mib(mapped_size), mapped_virtual);
|
|
|
|
}
|
2014-03-31 18:59:58 +02:00
|
|
|
munmap(mapped_virtual, mapped_size);
|
|
|
|
mapped_virtual = NULL;
|
|
|
|
mapped_size = 0;
|
|
|
|
}
|
|
|
|
|
2015-09-06 01:07:17 +02:00
|
|
|
static void *map_memory_size(u64 physical, size_t size, uint8_t abort_on_failure)
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
{
|
2013-01-03 23:30:33 +01:00
|
|
|
void *v;
|
|
|
|
off_t p;
|
2013-06-20 00:39:09 +02:00
|
|
|
u64 page = getpagesize();
|
2014-03-31 18:59:58 +02:00
|
|
|
size_t padding;
|
|
|
|
|
|
|
|
if (mapped_virtual != NULL)
|
|
|
|
unmap_memory();
|
2013-01-03 23:30:33 +01:00
|
|
|
|
|
|
|
/* Mapped memory must be aligned to page size */
|
|
|
|
p = physical & ~(page - 1);
|
2014-03-31 18:59:58 +02:00
|
|
|
padding = physical & (page-1);
|
|
|
|
size += padding;
|
2013-01-03 23:30:33 +01:00
|
|
|
|
2015-05-16 21:55:54 +02:00
|
|
|
if (size_to_mib(size) == 0) {
|
|
|
|
debug("Mapping %zuB of physical memory at 0x%jx (requested 0x%jx).\n",
|
|
|
|
size, (intmax_t)p, (intmax_t)physical);
|
2015-09-06 01:07:17 +02:00
|
|
|
} else {
|
2015-05-16 21:55:54 +02:00
|
|
|
debug("Mapping %zuMB of physical memory at 0x%jx (requested 0x%jx).\n",
|
|
|
|
size_to_mib(size), (intmax_t)p, (intmax_t)physical);
|
|
|
|
}
|
2013-01-03 23:30:33 +01:00
|
|
|
|
2014-06-17 08:02:03 +02:00
|
|
|
v = mmap(NULL, size, PROT_READ, MAP_SHARED, mem_fd, p);
|
2013-01-03 23:30:33 +01:00
|
|
|
|
2015-05-16 21:55:54 +02:00
|
|
|
if (v == MAP_FAILED) {
|
|
|
|
/* The mapped area may have overrun the upper cbmem boundary when trying to
|
|
|
|
* align to the page size. Try growing down instead of up...
|
|
|
|
*/
|
|
|
|
p -= page;
|
|
|
|
padding += page;
|
|
|
|
size &= ~(page - 1);
|
|
|
|
size = size + (page - 1);
|
|
|
|
v = mmap(NULL, size, PROT_READ, MAP_SHARED, mem_fd, p);
|
|
|
|
debug(" ... failed. Mapping %zuB of physical memory at 0x%jx.\n",
|
|
|
|
size, (intmax_t)p);
|
|
|
|
}
|
|
|
|
|
2013-01-03 23:30:33 +01:00
|
|
|
if (v == MAP_FAILED) {
|
2015-09-06 01:07:17 +02:00
|
|
|
if (abort_on_failure) {
|
|
|
|
fprintf(stderr, "Failed to mmap /dev/mem: %s\n",
|
|
|
|
strerror(errno));
|
|
|
|
exit(1);
|
|
|
|
} else {
|
|
|
|
return 0;
|
|
|
|
}
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
}
|
2013-01-03 23:30:33 +01:00
|
|
|
|
|
|
|
/* Remember what we actually mapped ... */
|
|
|
|
mapped_virtual = v;
|
2014-03-31 18:59:58 +02:00
|
|
|
mapped_size = size;
|
2013-01-03 23:30:33 +01:00
|
|
|
|
|
|
|
/* ... but return address to the physical memory that was requested */
|
2013-07-17 02:47:35 +02:00
|
|
|
if (padding)
|
2014-03-31 18:59:58 +02:00
|
|
|
debug(" ... padding virtual address with 0x%zx bytes.\n",
|
2013-07-17 02:47:35 +02:00
|
|
|
padding);
|
|
|
|
v += padding;
|
2013-01-03 23:30:33 +01:00
|
|
|
|
|
|
|
return v;
|
|
|
|
}
|
|
|
|
|
2015-09-30 19:33:01 +02:00
|
|
|
static void *map_lbtable(void)
|
2013-01-03 23:30:33 +01:00
|
|
|
{
|
2015-09-30 19:33:01 +02:00
|
|
|
if (lbtable_address == 0 || lbtable_size == 0) {
|
|
|
|
fprintf(stderr, "No coreboot table area found!\n");
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
return map_memory_size(lbtable_address, lbtable_size, 1);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void unmap_lbtable(void)
|
|
|
|
{
|
|
|
|
unmap_memory();
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Find the first cbmem entry filling in the details. */
|
|
|
|
static int find_cbmem_entry(uint32_t id, uint64_t *addr, size_t *size)
|
|
|
|
{
|
|
|
|
uint8_t *table;
|
|
|
|
size_t offset;
|
|
|
|
int ret = -1;
|
|
|
|
|
|
|
|
table = map_lbtable();
|
|
|
|
|
|
|
|
if (table == NULL)
|
|
|
|
return -1;
|
|
|
|
|
|
|
|
offset = 0;
|
|
|
|
|
|
|
|
while (offset < lbtable_size) {
|
|
|
|
struct lb_record *lbr;
|
|
|
|
struct lb_cbmem_entry *lbe;
|
|
|
|
|
|
|
|
lbr = (void *)(table + offset);
|
|
|
|
offset += lbr->size;
|
|
|
|
|
|
|
|
if (lbr->tag != LB_TAG_CBMEM_ENTRY)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
lbe = (void *)lbr;
|
|
|
|
if (lbe->id != id)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
*addr = lbe->address;
|
|
|
|
*size = lbe->entry_size;
|
|
|
|
ret = 0;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
unmap_lbtable();
|
|
|
|
return ret;
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2013-01-03 23:30:33 +01:00
|
|
|
* Try finding the timestamp table and coreboot cbmem console starting from the
|
|
|
|
* passed in memory offset. Could be called recursively in case a forwarding
|
|
|
|
* entry is found.
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
*
|
|
|
|
* Returns pointer to a memory buffer containg the timestamp table or zero if
|
|
|
|
* none found.
|
|
|
|
*/
|
2013-01-03 23:30:33 +01:00
|
|
|
|
|
|
|
static struct lb_cbmem_ref timestamps;
|
|
|
|
static struct lb_cbmem_ref console;
|
2013-01-08 01:26:10 +01:00
|
|
|
static struct lb_memory_range cbmem;
|
2013-01-03 23:30:33 +01:00
|
|
|
|
2013-04-19 23:22:29 +02:00
|
|
|
/* This is a work-around for a nasty problem introduced by initially having
|
|
|
|
* pointer sized entries in the lb_cbmem_ref structures. This caused problems
|
|
|
|
* on 64bit x86 systems because coreboot is 32bit on those systems.
|
|
|
|
* When the problem was found, it was corrected, but there are a lot of
|
|
|
|
* systems out there with a firmware that does not produce the right
|
|
|
|
* lb_cbmem_ref structure. Hence we try to autocorrect this issue here.
|
|
|
|
*/
|
|
|
|
static struct lb_cbmem_ref parse_cbmem_ref(struct lb_cbmem_ref *cbmem_ref)
|
|
|
|
{
|
|
|
|
struct lb_cbmem_ref ret;
|
|
|
|
|
|
|
|
ret = *cbmem_ref;
|
|
|
|
|
|
|
|
if (cbmem_ref->size < sizeof(*cbmem_ref))
|
|
|
|
ret.cbmem_addr = (uint32_t)ret.cbmem_addr;
|
|
|
|
|
2013-07-17 02:47:35 +02:00
|
|
|
debug(" cbmem_addr = %" PRIx64 "\n", ret.cbmem_addr);
|
|
|
|
|
2013-04-19 23:22:29 +02:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2015-09-06 01:07:17 +02:00
|
|
|
static int parse_cbtable(u64 address, size_t table_size, uint8_t abort_on_failure)
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
{
|
2015-09-06 01:07:17 +02:00
|
|
|
int i, found, ret = 0;
|
2013-01-03 23:30:33 +01:00
|
|
|
void *buf;
|
|
|
|
|
2014-10-07 21:56:35 +02:00
|
|
|
debug("Looking for coreboot table at %" PRIx64 " %zd bytes.\n",
|
|
|
|
address, table_size);
|
2015-09-06 01:07:17 +02:00
|
|
|
buf = map_memory_size(address, table_size, abort_on_failure);
|
|
|
|
if (!buf)
|
|
|
|
return -2;
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
|
|
|
|
/* look at every 16 bytes within 4K of the base */
|
2013-01-03 23:30:33 +01:00
|
|
|
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
for (i = 0; i < 0x1000; i += 0x10) {
|
2013-01-03 23:30:33 +01:00
|
|
|
struct lb_header *lbh;
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
struct lb_record* lbr_p;
|
2013-01-03 23:30:33 +01:00
|
|
|
void *lbtable;
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
int j;
|
|
|
|
|
2013-01-03 23:30:33 +01:00
|
|
|
lbh = (struct lb_header *)(buf + i);
|
|
|
|
if (memcmp(lbh->signature, "LBIO", sizeof(lbh->signature)) ||
|
|
|
|
!lbh->header_bytes ||
|
|
|
|
ipchcksum(lbh, sizeof(*lbh))) {
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
continue;
|
|
|
|
}
|
2013-01-03 23:30:33 +01:00
|
|
|
lbtable = buf + i + lbh->header_bytes;
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
|
2013-01-03 23:30:33 +01:00
|
|
|
if (ipchcksum(lbtable, lbh->table_bytes) !=
|
|
|
|
lbh->table_checksum) {
|
|
|
|
debug("Signature found, but wrong checksum.\n");
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
2013-01-03 23:30:33 +01:00
|
|
|
found = 1;
|
|
|
|
debug("Found!\n");
|
|
|
|
|
2015-09-30 19:33:01 +02:00
|
|
|
/* Keep reference to lbtable. */
|
|
|
|
lbtable_address = address;
|
|
|
|
lbtable_address += ((uint8_t *)lbtable - (uint8_t *)lbh);
|
|
|
|
lbtable_size = lbh->table_bytes;
|
|
|
|
|
2013-01-03 23:30:33 +01:00
|
|
|
for (j = 0; j < lbh->table_bytes; j += lbr_p->size) {
|
|
|
|
lbr_p = (struct lb_record*) ((char *)lbtable + j);
|
|
|
|
debug(" coreboot table entry 0x%02x\n", lbr_p->tag);
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
switch (lbr_p->tag) {
|
2013-01-08 01:26:10 +01:00
|
|
|
case LB_TAG_MEMORY: {
|
|
|
|
int i = 0;
|
|
|
|
debug(" Found memory map.\n");
|
|
|
|
struct lb_memory *memory =
|
|
|
|
(struct lb_memory *)lbr_p;
|
2014-10-17 13:46:12 +02:00
|
|
|
while ((char *)&memory->map[i] < ((char *)lbr_p
|
2013-01-08 01:26:10 +01:00
|
|
|
+ lbr_p->size)) {
|
|
|
|
if (memory->map[i].type == LB_MEM_TABLE) {
|
|
|
|
debug(" LB_MEM_TABLE found.\n");
|
|
|
|
/* The last one found is CBMEM */
|
|
|
|
cbmem = memory->map[i];
|
|
|
|
}
|
|
|
|
i++;
|
|
|
|
}
|
|
|
|
continue;
|
|
|
|
}
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
case LB_TAG_TIMESTAMPS: {
|
2013-01-08 00:25:37 +01:00
|
|
|
debug(" Found timestamp table.\n");
|
2013-04-19 23:22:29 +02:00
|
|
|
timestamps = parse_cbmem_ref((struct lb_cbmem_ref *) lbr_p);
|
2013-01-03 23:30:33 +01:00
|
|
|
continue;
|
|
|
|
}
|
|
|
|
case LB_TAG_CBMEM_CONSOLE: {
|
2013-01-08 00:25:37 +01:00
|
|
|
debug(" Found cbmem console.\n");
|
2013-04-19 23:22:29 +02:00
|
|
|
console = parse_cbmem_ref((struct lb_cbmem_ref *) lbr_p);
|
2013-01-03 23:30:33 +01:00
|
|
|
continue;
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
}
|
|
|
|
case LB_TAG_FORWARD: {
|
|
|
|
/*
|
|
|
|
* This is a forwarding entry - repeat the
|
|
|
|
* search at the new address.
|
|
|
|
*/
|
2013-01-03 23:30:33 +01:00
|
|
|
struct lb_forward lbf_p =
|
|
|
|
*(struct lb_forward *) lbr_p;
|
2013-01-08 00:25:37 +01:00
|
|
|
debug(" Found forwarding entry.\n");
|
2013-01-03 23:30:33 +01:00
|
|
|
unmap_memory();
|
2015-09-06 01:07:17 +02:00
|
|
|
ret = parse_cbtable(lbf_p.forward, table_size, 0);
|
|
|
|
if (ret == -2) {
|
|
|
|
/* try again with a smaller memory mapping request */
|
|
|
|
ret = parse_cbtable(lbf_p.forward, table_size / 2, 1);
|
|
|
|
if (ret == -2)
|
|
|
|
exit(1);
|
|
|
|
else
|
|
|
|
return ret;
|
|
|
|
} else {
|
|
|
|
return ret;
|
|
|
|
}
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
}
|
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
}
|
|
|
|
}
|
2013-01-03 23:30:33 +01:00
|
|
|
unmap_memory();
|
|
|
|
|
|
|
|
return found;
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
}
|
|
|
|
|
2015-07-13 16:53:50 +02:00
|
|
|
#if defined(linux) && (defined(__i386__) || defined(__x86_64__))
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
/*
|
|
|
|
* read CPU frequency from a sysfs file, return an frequency in Kilohertz as
|
|
|
|
* an int or exit on any error.
|
|
|
|
*/
|
2015-08-31 04:19:55 +02:00
|
|
|
static unsigned long arch_tick_frequency(void)
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
{
|
|
|
|
FILE *cpuf;
|
|
|
|
char freqs[100];
|
|
|
|
int size;
|
|
|
|
char *endp;
|
|
|
|
u64 rv;
|
|
|
|
|
|
|
|
const char* freq_file =
|
|
|
|
"/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq";
|
|
|
|
|
|
|
|
cpuf = fopen(freq_file, "r");
|
|
|
|
if (!cpuf) {
|
2013-01-03 23:30:33 +01:00
|
|
|
fprintf(stderr, "Could not open %s: %s\n",
|
|
|
|
freq_file, strerror(errno));
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
|
|
|
|
memset(freqs, 0, sizeof(freqs));
|
|
|
|
size = fread(freqs, 1, sizeof(freqs), cpuf);
|
|
|
|
if (!size || (size == sizeof(freqs))) {
|
|
|
|
fprintf(stderr, "Wrong number of bytes(%d) read from %s\n",
|
|
|
|
size, freq_file);
|
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
fclose(cpuf);
|
|
|
|
rv = strtoull(freqs, &endp, 10);
|
|
|
|
|
|
|
|
if (*endp == '\0' || *endp == '\n')
|
|
|
|
return rv;
|
|
|
|
fprintf(stderr, "Wrong formatted value ^%s^ read from %s\n",
|
|
|
|
freqs, freq_file);
|
|
|
|
exit(1);
|
|
|
|
}
|
2015-07-13 16:53:50 +02:00
|
|
|
#elif defined(__OpenBSD__) && (defined(__i386__) || defined(__x86_64__))
|
2015-08-31 04:19:55 +02:00
|
|
|
static unsigned long arch_tick_frequency(void)
|
2015-07-13 16:53:50 +02:00
|
|
|
{
|
|
|
|
int mib[2] = { CTL_HW, HW_CPUSPEED };
|
|
|
|
static int value = 0;
|
|
|
|
size_t value_len = sizeof(value);
|
|
|
|
|
2015-08-31 04:19:55 +02:00
|
|
|
/* Return 1 MHz when sysctl fails. */
|
2015-07-13 16:53:50 +02:00
|
|
|
if ((value == 0) && (sysctl(mib, 2, &value, &value_len, NULL, 0) == -1))
|
2015-08-31 04:19:55 +02:00
|
|
|
return 1;
|
2015-07-13 16:53:50 +02:00
|
|
|
|
2015-08-31 04:19:55 +02:00
|
|
|
return value;
|
2015-07-13 16:53:50 +02:00
|
|
|
}
|
2013-08-01 00:44:37 +02:00
|
|
|
#else
|
2015-08-31 04:19:55 +02:00
|
|
|
static unsigned long arch_tick_frequency(void)
|
|
|
|
{
|
|
|
|
/* 1 MHz = 1us. */
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
|
|
|
static unsigned long tick_freq_mhz;
|
|
|
|
|
|
|
|
static void timestamp_set_tick_freq(unsigned long table_tick_freq_mhz)
|
|
|
|
{
|
|
|
|
tick_freq_mhz = table_tick_freq_mhz;
|
|
|
|
|
|
|
|
/* Honor table frequency. */
|
|
|
|
if (tick_freq_mhz)
|
|
|
|
return;
|
|
|
|
|
|
|
|
tick_freq_mhz = arch_tick_frequency();
|
|
|
|
|
|
|
|
if (!tick_freq_mhz) {
|
|
|
|
fprintf(stderr, "Cannot determine timestamp tick frequency.\n");
|
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
}
|
2013-08-01 00:44:37 +02:00
|
|
|
|
|
|
|
u64 arch_convert_raw_ts_entry(u64 ts)
|
|
|
|
{
|
2015-08-31 04:19:55 +02:00
|
|
|
return ts / tick_freq_mhz;
|
2013-08-01 00:44:37 +02:00
|
|
|
}
|
|
|
|
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
/*
|
|
|
|
* Print an integer in 'normalized' form - with commas separating every three
|
2014-12-03 05:51:19 +01:00
|
|
|
* decimal orders.
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
*/
|
2014-12-03 05:51:19 +01:00
|
|
|
static void print_norm(u64 v)
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
{
|
2014-12-03 05:51:19 +01:00
|
|
|
if (v >= 1000) {
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
/* print the higher order sections first */
|
2014-12-03 05:51:19 +01:00
|
|
|
print_norm(v / 1000);
|
|
|
|
printf(",%3.3u", (u32)(v % 1000));
|
|
|
|
} else {
|
|
|
|
printf("%u", (u32)(v % 1000));
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2013-08-09 20:06:11 +02:00
|
|
|
enum additional_timestamp_id {
|
|
|
|
// Depthcharge entry IDs start at 1000.
|
|
|
|
TS_DC_START = 1000,
|
|
|
|
|
|
|
|
TS_RO_PARAMS_INIT = 1001,
|
|
|
|
TS_RO_VB_INIT = 1002,
|
|
|
|
TS_RO_VB_SELECT_FIRMWARE = 1003,
|
|
|
|
TS_RO_VB_SELECT_AND_LOAD_KERNEL = 1004,
|
|
|
|
|
|
|
|
TS_RW_VB_SELECT_AND_LOAD_KERNEL = 1010,
|
|
|
|
|
|
|
|
TS_VB_SELECT_AND_LOAD_KERNEL = 1020,
|
|
|
|
|
2015-10-27 21:53:02 +01:00
|
|
|
TS_VB_EC_VBOOT_DONE = 1030,
|
|
|
|
|
2013-08-09 20:06:11 +02:00
|
|
|
TS_CROSSYSTEM_DATA = 1100,
|
|
|
|
TS_START_KERNEL = 1101
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct timestamp_id_to_name {
|
|
|
|
u32 id;
|
|
|
|
const char *name;
|
|
|
|
} timestamp_ids[] = {
|
2015-07-11 19:44:10 +02:00
|
|
|
/* Marker to report base_time. */
|
|
|
|
{ 0, "1st timestamp" },
|
2013-08-09 20:06:11 +02:00
|
|
|
{ TS_START_ROMSTAGE, "start of rom stage" },
|
|
|
|
{ TS_BEFORE_INITRAM, "before ram initialization" },
|
|
|
|
{ TS_AFTER_INITRAM, "after ram initialization" },
|
|
|
|
{ TS_END_ROMSTAGE, "end of romstage" },
|
|
|
|
{ TS_START_VBOOT, "start of verified boot" },
|
|
|
|
{ TS_END_VBOOT, "end of verified boot" },
|
2014-12-03 05:51:19 +01:00
|
|
|
{ TS_START_COPYRAM, "starting to load ramstage" },
|
|
|
|
{ TS_END_COPYRAM, "finished loading ramstage" },
|
2013-08-09 20:06:11 +02:00
|
|
|
{ TS_START_RAMSTAGE, "start of ramstage" },
|
2014-12-03 05:51:19 +01:00
|
|
|
{ TS_START_BOOTBLOCK, "start of bootblock" },
|
|
|
|
{ TS_END_BOOTBLOCK, "end of bootblock" },
|
|
|
|
{ TS_START_COPYROM, "starting to load romstage" },
|
|
|
|
{ TS_END_COPYROM, "finished loading romstage" },
|
|
|
|
{ TS_START_ULZMA, "starting LZMA decompress (ignore for x86)" },
|
|
|
|
{ TS_END_ULZMA, "finished LZMA decompress (ignore for x86)" },
|
2013-08-09 20:06:11 +02:00
|
|
|
{ TS_DEVICE_ENUMERATE, "device enumeration" },
|
|
|
|
{ TS_DEVICE_CONFIGURE, "device configuration" },
|
|
|
|
{ TS_DEVICE_ENABLE, "device enable" },
|
|
|
|
{ TS_DEVICE_INITIALIZE, "device initialization" },
|
|
|
|
{ TS_DEVICE_DONE, "device setup done" },
|
|
|
|
{ TS_CBMEM_POST, "cbmem post" },
|
|
|
|
{ TS_WRITE_TABLES, "write tables" },
|
|
|
|
{ TS_LOAD_PAYLOAD, "load payload" },
|
|
|
|
{ TS_ACPI_WAKE_JUMP, "ACPI wake jump" },
|
|
|
|
{ TS_SELFBOOT_JUMP, "selfboot jump" },
|
2014-12-03 05:51:19 +01:00
|
|
|
|
|
|
|
{ TS_START_COPYVER, "starting to load verstage" },
|
|
|
|
{ TS_END_COPYVER, "finished loading verstage" },
|
|
|
|
{ TS_START_TPMINIT, "starting to initialize TPM" },
|
|
|
|
{ TS_END_TPMINIT, "finished TPM initialization" },
|
|
|
|
{ TS_START_VERIFY_SLOT, "starting to verify keyblock/preamble (RSA)" },
|
|
|
|
{ TS_END_VERIFY_SLOT, "finished verifying keyblock/preamble (RSA)" },
|
|
|
|
{ TS_START_HASH_BODY, "starting to verify body (load+SHA2+RSA) " },
|
|
|
|
{ TS_DONE_LOADING, "finished loading body (ignore for x86)" },
|
|
|
|
{ TS_DONE_HASHING, "finished calculating body hash (SHA2)" },
|
|
|
|
{ TS_END_HASH_BODY, "finished verifying body signature (RSA)" },
|
|
|
|
|
2013-08-09 20:06:11 +02:00
|
|
|
{ TS_DC_START, "depthcharge start" },
|
|
|
|
{ TS_RO_PARAMS_INIT, "RO parameter init" },
|
|
|
|
{ TS_RO_VB_INIT, "RO vboot init" },
|
|
|
|
{ TS_RO_VB_SELECT_FIRMWARE, "RO vboot select firmware" },
|
|
|
|
{ TS_RO_VB_SELECT_AND_LOAD_KERNEL, "RO vboot select&load kernel" },
|
|
|
|
{ TS_RW_VB_SELECT_AND_LOAD_KERNEL, "RW vboot select&load kernel" },
|
|
|
|
{ TS_VB_SELECT_AND_LOAD_KERNEL, "vboot select&load kernel" },
|
2015-10-27 21:53:02 +01:00
|
|
|
{ TS_VB_EC_VBOOT_DONE, "finished EC verification" },
|
2013-08-09 20:06:11 +02:00
|
|
|
{ TS_CROSSYSTEM_DATA, "crossystem data" },
|
2015-02-24 20:30:38 +01:00
|
|
|
{ TS_START_KERNEL, "start kernel" },
|
|
|
|
|
|
|
|
/* FSP related timestamps */
|
|
|
|
{ TS_FSP_MEMORY_INIT_START, "calling FspMemoryInit" },
|
|
|
|
{ TS_FSP_MEMORY_INIT_END, "returning from FspMemoryInit" },
|
|
|
|
{ TS_FSP_TEMP_RAM_EXIT_START, "calling FspTempRamExit" },
|
|
|
|
{ TS_FSP_TEMP_RAM_EXIT_END, "returning from FspTempRamExit" },
|
|
|
|
{ TS_FSP_SILICON_INIT_START, "calling FspSiliconInit" },
|
|
|
|
{ TS_FSP_SILICON_INIT_END, "returning from FspSiliconInit" },
|
|
|
|
{ TS_FSP_BEFORE_ENUMERATE, "calling FspNotify(AfterPciEnumeration)" },
|
|
|
|
{ TS_FSP_AFTER_ENUMERATE,
|
|
|
|
"returning from FspNotify(AfterPciEnumeration)" },
|
|
|
|
{ TS_FSP_BEFORE_FINALIZE, "calling FspNotify(ReadyToBoot)" },
|
|
|
|
{ TS_FSP_AFTER_FINALIZE, "returning from FspNotify(ReadyToBoot)" }
|
2013-08-09 20:06:11 +02:00
|
|
|
};
|
|
|
|
|
2015-08-31 05:00:12 +02:00
|
|
|
static const char *timestamp_name(uint32_t id)
|
2013-08-09 20:06:11 +02:00
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 0; i < ARRAY_SIZE(timestamp_ids); i++) {
|
2015-08-31 05:00:12 +02:00
|
|
|
if (timestamp_ids[i].id == id)
|
|
|
|
return timestamp_ids[i].name;
|
2013-08-09 20:06:11 +02:00
|
|
|
}
|
2015-08-31 05:00:12 +02:00
|
|
|
return "<unknown>";
|
|
|
|
}
|
|
|
|
|
|
|
|
static uint64_t timestamp_print_parseable_entry(uint32_t id, uint64_t stamp,
|
|
|
|
uint64_t prev_stamp)
|
|
|
|
{
|
|
|
|
const char *name;
|
|
|
|
uint64_t step_time;
|
|
|
|
|
|
|
|
name = timestamp_name(id);
|
|
|
|
|
|
|
|
step_time = arch_convert_raw_ts_entry(stamp - prev_stamp);
|
|
|
|
|
|
|
|
/* ID<tab>absolute time<tab>relative time<tab>description */
|
|
|
|
printf("%d\t", id);
|
|
|
|
printf("%llu\t", (long long)arch_convert_raw_ts_entry(stamp));
|
|
|
|
printf("%llu\t", (long long)step_time);
|
|
|
|
printf("%s\n", name);
|
|
|
|
|
|
|
|
return step_time;
|
|
|
|
}
|
|
|
|
|
|
|
|
uint64_t timestamp_print_entry(uint32_t id, uint64_t stamp, uint64_t prev_stamp)
|
|
|
|
{
|
|
|
|
const char *name;
|
|
|
|
uint64_t step_time;
|
|
|
|
|
|
|
|
name = timestamp_name(id);
|
2013-08-09 20:06:11 +02:00
|
|
|
|
|
|
|
printf("%4d:", id);
|
2014-12-03 05:51:19 +01:00
|
|
|
printf("%-50s", name);
|
|
|
|
print_norm(arch_convert_raw_ts_entry(stamp));
|
2015-08-06 20:52:08 +02:00
|
|
|
step_time = arch_convert_raw_ts_entry(stamp - prev_stamp);
|
2013-08-09 20:06:11 +02:00
|
|
|
if (prev_stamp) {
|
|
|
|
printf(" (");
|
2015-08-06 20:52:08 +02:00
|
|
|
print_norm(step_time);
|
2013-08-09 20:06:11 +02:00
|
|
|
printf(")");
|
|
|
|
}
|
|
|
|
printf("\n");
|
2015-08-06 20:52:08 +02:00
|
|
|
|
|
|
|
return step_time;
|
2013-08-09 20:06:11 +02:00
|
|
|
}
|
|
|
|
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
/* dump the timestamp table */
|
2015-08-31 05:00:12 +02:00
|
|
|
static void dump_timestamps(int mach_readable)
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
{
|
|
|
|
int i;
|
2013-01-03 23:30:33 +01:00
|
|
|
struct timestamp_table *tst_p;
|
2014-10-07 21:56:35 +02:00
|
|
|
size_t size;
|
2015-07-11 19:44:10 +02:00
|
|
|
uint64_t prev_stamp;
|
2015-08-06 20:52:08 +02:00
|
|
|
uint64_t total_time;
|
2013-01-03 23:30:33 +01:00
|
|
|
|
|
|
|
if (timestamps.tag != LB_TAG_TIMESTAMPS) {
|
|
|
|
fprintf(stderr, "No timestamps found in coreboot table.\n");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2014-10-07 21:56:35 +02:00
|
|
|
size = sizeof(*tst_p);
|
2015-09-06 01:07:17 +02:00
|
|
|
tst_p = map_memory_size((unsigned long)timestamps.cbmem_addr, size, 1);
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
|
2015-08-31 04:19:55 +02:00
|
|
|
timestamp_set_tick_freq(tst_p->tick_freq_mhz);
|
|
|
|
|
2015-08-31 05:00:12 +02:00
|
|
|
if (!mach_readable)
|
|
|
|
printf("%d entries total:\n\n", tst_p->num_entries);
|
2014-10-07 21:56:35 +02:00
|
|
|
size += tst_p->num_entries * sizeof(tst_p->entries[0]);
|
|
|
|
|
|
|
|
unmap_memory();
|
2015-09-06 01:07:17 +02:00
|
|
|
tst_p = map_memory_size((unsigned long)timestamps.cbmem_addr, size, 1);
|
2014-10-07 21:56:35 +02:00
|
|
|
|
2015-07-11 19:44:10 +02:00
|
|
|
/* Report the base time within the table. */
|
|
|
|
prev_stamp = 0;
|
2015-08-31 05:00:12 +02:00
|
|
|
if (mach_readable)
|
|
|
|
timestamp_print_parseable_entry(0, tst_p->base_time,
|
|
|
|
prev_stamp);
|
|
|
|
else
|
|
|
|
timestamp_print_entry(0, tst_p->base_time, prev_stamp);
|
2015-07-11 19:44:10 +02:00
|
|
|
prev_stamp = tst_p->base_time;
|
|
|
|
|
2015-08-06 20:52:08 +02:00
|
|
|
total_time = 0;
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
for (i = 0; i < tst_p->num_entries; i++) {
|
2015-07-11 19:44:10 +02:00
|
|
|
uint64_t stamp;
|
|
|
|
const struct timestamp_entry *tse = &tst_p->entries[i];
|
|
|
|
|
|
|
|
/* Make all timestamps absolute. */
|
|
|
|
stamp = tse->entry_stamp + tst_p->base_time;
|
2015-08-31 05:00:12 +02:00
|
|
|
if (mach_readable)
|
|
|
|
total_time +=
|
|
|
|
timestamp_print_parseable_entry(tse->entry_id,
|
|
|
|
stamp, prev_stamp);
|
|
|
|
else
|
|
|
|
total_time += timestamp_print_entry(tse->entry_id,
|
2015-08-06 20:52:08 +02:00
|
|
|
stamp, prev_stamp);
|
2015-07-11 19:44:10 +02:00
|
|
|
prev_stamp = stamp;
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
}
|
2013-01-03 23:30:33 +01:00
|
|
|
|
2015-08-31 05:00:12 +02:00
|
|
|
if (!mach_readable) {
|
|
|
|
printf("\nTotal Time: ");
|
|
|
|
print_norm(total_time);
|
|
|
|
printf("\n");
|
|
|
|
}
|
2015-08-06 20:52:08 +02:00
|
|
|
|
2013-01-03 23:30:33 +01:00
|
|
|
unmap_memory();
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
}
|
|
|
|
|
2013-01-07 22:37:12 +01:00
|
|
|
/* dump the cbmem console */
|
|
|
|
static void dump_console(void)
|
|
|
|
{
|
|
|
|
void *console_p;
|
|
|
|
char *console_c;
|
|
|
|
uint32_t size;
|
2013-03-30 12:15:12 +01:00
|
|
|
uint32_t cursor;
|
2013-01-07 22:37:12 +01:00
|
|
|
|
|
|
|
if (console.tag != LB_TAG_CBMEM_CONSOLE) {
|
|
|
|
fprintf(stderr, "No console found in coreboot table.\n");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2014-10-07 21:56:35 +02:00
|
|
|
console_p = map_memory_size((unsigned long)console.cbmem_addr,
|
2015-09-06 01:07:17 +02:00
|
|
|
2 * sizeof(uint32_t), 1);
|
2013-01-07 22:37:12 +01:00
|
|
|
/* The in-memory format of the console area is:
|
|
|
|
* u32 size
|
|
|
|
* u32 cursor
|
|
|
|
* char console[size]
|
|
|
|
* Hence we have to add 8 to get to the actual console string.
|
|
|
|
*/
|
2013-08-09 09:40:06 +02:00
|
|
|
size = ((uint32_t *)console_p)[0];
|
|
|
|
cursor = ((uint32_t *)console_p)[1];
|
2013-03-30 12:15:12 +01:00
|
|
|
/* Cursor continues to go on even after no more data fits in
|
|
|
|
* the buffer but the data is dropped in this case.
|
|
|
|
*/
|
|
|
|
if (size > cursor)
|
|
|
|
size = cursor;
|
2013-01-07 22:37:12 +01:00
|
|
|
console_c = malloc(size + 1);
|
2014-10-07 21:56:35 +02:00
|
|
|
unmap_memory();
|
2013-01-07 22:37:12 +01:00
|
|
|
if (!console_c) {
|
|
|
|
fprintf(stderr, "Not enough memory for console.\n");
|
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
|
2014-03-31 18:59:58 +02:00
|
|
|
console_p = map_memory_size((unsigned long)console.cbmem_addr,
|
2015-09-06 01:07:17 +02:00
|
|
|
size + sizeof(size) + sizeof(cursor), 1);
|
2013-01-07 22:37:12 +01:00
|
|
|
memcpy(console_c, console_p + 8, size);
|
|
|
|
console_c[size] = 0;
|
2013-08-09 09:40:06 +02:00
|
|
|
console_c[cursor] = 0;
|
2013-01-07 22:37:12 +01:00
|
|
|
|
2013-03-30 12:15:12 +01:00
|
|
|
printf("%s\n", console_c);
|
|
|
|
if (size < cursor)
|
|
|
|
printf("%d %s lost\n", cursor - size,
|
|
|
|
(cursor - size) == 1 ? "byte":"bytes");
|
2013-01-07 22:37:12 +01:00
|
|
|
|
|
|
|
free(console_c);
|
|
|
|
|
|
|
|
unmap_memory();
|
|
|
|
}
|
|
|
|
|
2013-07-17 02:47:35 +02:00
|
|
|
static void hexdump(unsigned long memory, int length)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
uint8_t *m;
|
|
|
|
int all_zero = 0;
|
|
|
|
|
2015-09-06 01:07:17 +02:00
|
|
|
m = map_memory_size((intptr_t)memory, length, 1);
|
2013-07-17 02:47:35 +02:00
|
|
|
|
|
|
|
if (length > MAP_BYTES) {
|
|
|
|
printf("Truncating hex dump from %d to %d bytes\n\n",
|
|
|
|
length, MAP_BYTES);
|
|
|
|
length = MAP_BYTES;
|
|
|
|
}
|
|
|
|
|
|
|
|
for (i = 0; i < length; i += 16) {
|
|
|
|
int j;
|
|
|
|
|
|
|
|
all_zero++;
|
|
|
|
for (j = 0; j < 16; j++) {
|
|
|
|
if(m[i+j] != 0) {
|
|
|
|
all_zero = 0;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (all_zero < 2) {
|
|
|
|
printf("%08lx:", memory + i);
|
|
|
|
for (j = 0; j < 16; j++)
|
|
|
|
printf(" %02x", m[i+j]);
|
|
|
|
printf(" ");
|
|
|
|
for (j = 0; j < 16; j++)
|
|
|
|
printf("%c", isprint(m[i+j]) ? m[i+j] : '.');
|
|
|
|
printf("\n");
|
|
|
|
} else if (all_zero == 2) {
|
|
|
|
printf("...\n");
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
unmap_memory();
|
|
|
|
}
|
|
|
|
|
|
|
|
static void dump_cbmem_hex(void)
|
|
|
|
{
|
|
|
|
if (cbmem.type != LB_MEM_TABLE) {
|
|
|
|
fprintf(stderr, "No coreboot CBMEM area found!\n");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
hexdump(unpack_lb64(cbmem.start), unpack_lb64(cbmem.size));
|
|
|
|
}
|
|
|
|
|
2015-03-06 04:18:33 +01:00
|
|
|
struct cbmem_id_to_name {
|
|
|
|
uint32_t id;
|
|
|
|
const char *name;
|
|
|
|
};
|
2014-05-14 19:12:55 +02:00
|
|
|
static const struct cbmem_id_to_name cbmem_ids[] = { CBMEM_ID_TO_NAME_TABLE };
|
2013-01-08 01:26:10 +01:00
|
|
|
|
2013-07-17 02:47:35 +02:00
|
|
|
void cbmem_print_entry(int n, uint32_t id, uint64_t base, uint64_t size)
|
2013-01-08 01:26:10 +01:00
|
|
|
{
|
|
|
|
int i;
|
2013-07-17 02:47:35 +02:00
|
|
|
const char *name;
|
2013-01-08 01:26:10 +01:00
|
|
|
|
2013-07-17 02:47:35 +02:00
|
|
|
name = NULL;
|
|
|
|
for (i = 0; i < ARRAY_SIZE(cbmem_ids); i++) {
|
|
|
|
if (cbmem_ids[i].id == id) {
|
|
|
|
name = cbmem_ids[i].name;
|
|
|
|
break;
|
|
|
|
}
|
2013-01-08 01:26:10 +01:00
|
|
|
}
|
|
|
|
|
2013-07-17 02:47:35 +02:00
|
|
|
printf("%2d. ", n);
|
|
|
|
if (name == NULL)
|
|
|
|
printf("%08x ", id);
|
|
|
|
else
|
|
|
|
printf("%s", name);
|
|
|
|
printf(" %08" PRIx64 " ", base);
|
|
|
|
printf(" %08" PRIx64 "\n", size);
|
|
|
|
}
|
2013-01-08 01:26:10 +01:00
|
|
|
|
2015-09-30 19:33:01 +02:00
|
|
|
static void dump_cbmem_toc(void)
|
2013-07-17 02:47:35 +02:00
|
|
|
{
|
|
|
|
int i;
|
2015-09-30 19:33:01 +02:00
|
|
|
uint8_t *table;
|
|
|
|
size_t offset;
|
2013-01-08 01:26:10 +01:00
|
|
|
|
2015-09-30 19:33:01 +02:00
|
|
|
table = map_lbtable();
|
2013-01-08 01:26:10 +01:00
|
|
|
|
2015-09-30 19:33:01 +02:00
|
|
|
if (table == NULL)
|
|
|
|
return;
|
2013-07-17 02:47:35 +02:00
|
|
|
|
|
|
|
printf("CBMEM table of contents:\n");
|
|
|
|
printf(" ID START LENGTH\n");
|
|
|
|
|
2015-09-30 19:33:01 +02:00
|
|
|
i = 0;
|
|
|
|
offset = 0;
|
2013-07-17 02:47:35 +02:00
|
|
|
|
2015-09-30 19:33:01 +02:00
|
|
|
while (offset < lbtable_size) {
|
|
|
|
struct lb_record *lbr;
|
|
|
|
struct lb_cbmem_entry *lbe;
|
2013-07-17 02:47:35 +02:00
|
|
|
|
2015-09-30 19:33:01 +02:00
|
|
|
lbr = (void *)(table + offset);
|
|
|
|
offset += lbr->size;
|
2013-07-17 02:47:35 +02:00
|
|
|
|
2015-09-30 19:33:01 +02:00
|
|
|
if (lbr->tag != LB_TAG_CBMEM_ENTRY)
|
|
|
|
continue;
|
2013-07-17 02:47:35 +02:00
|
|
|
|
2015-09-30 19:33:01 +02:00
|
|
|
lbe = (void *)lbr;
|
|
|
|
cbmem_print_entry(i, lbe->id, lbe->address, lbe->entry_size);
|
|
|
|
i++;
|
2013-01-08 01:26:10 +01:00
|
|
|
}
|
2013-07-17 02:47:35 +02:00
|
|
|
|
2015-09-30 19:33:01 +02:00
|
|
|
unmap_lbtable();
|
2013-01-08 01:26:10 +01:00
|
|
|
}
|
2013-01-07 22:37:12 +01:00
|
|
|
|
Implement GCC code coverage analysis
In order to provide some insight on what code is executed during
coreboot's run time and how well our test scenarios work, this
adds code coverage support to coreboot's ram stage. This should
be easily adaptable for payloads, and maybe even romstage.
See http://gcc.gnu.org/onlinedocs/gcc/Gcov.html for
more information.
To instrument coreboot, select CONFIG_COVERAGE ("Code coverage
support") in Kconfig, and recompile coreboot. coreboot will then
store its code coverage information into CBMEM, if possible.
Then, run "cbmem -CV" as root on the target system running the
instrumented coreboot binary. This will create a whole bunch of
.gcda files that contain coverage information. Tar them up, copy
them to your build system machine, and untar them. Then you can
use your favorite coverage utility (gcov, lcov, ...) to visualize
code coverage.
For a sneak peak of what will expect you, please take a look
at http://www.coreboot.org/~stepan/coreboot-coverage/
Change-Id: Ib287d8309878a1f5c4be770c38b1bc0bb3aa6ec7
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Reviewed-on: http://review.coreboot.org/2052
Tested-by: build bot (Jenkins)
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Martin Roth <martin@se-eng.com>
Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
2012-12-19 01:23:28 +01:00
|
|
|
#define COVERAGE_MAGIC 0x584d4153
|
|
|
|
struct file {
|
|
|
|
uint32_t magic;
|
|
|
|
uint32_t next;
|
|
|
|
uint32_t filename;
|
|
|
|
uint32_t data;
|
|
|
|
int offset;
|
|
|
|
int len;
|
|
|
|
};
|
|
|
|
|
|
|
|
static int mkpath(char *path, mode_t mode)
|
|
|
|
{
|
|
|
|
assert (path && *path);
|
|
|
|
char *p;
|
|
|
|
for (p = strchr(path+1, '/'); p; p = strchr(p + 1, '/')) {
|
|
|
|
*p = '\0';
|
|
|
|
if (mkdir(path, mode) == -1) {
|
|
|
|
if (errno != EEXIST) {
|
|
|
|
*p = '/';
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
*p = '/';
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void dump_coverage(void)
|
|
|
|
{
|
|
|
|
uint64_t start;
|
2015-09-30 19:33:01 +02:00
|
|
|
size_t size;
|
Implement GCC code coverage analysis
In order to provide some insight on what code is executed during
coreboot's run time and how well our test scenarios work, this
adds code coverage support to coreboot's ram stage. This should
be easily adaptable for payloads, and maybe even romstage.
See http://gcc.gnu.org/onlinedocs/gcc/Gcov.html for
more information.
To instrument coreboot, select CONFIG_COVERAGE ("Code coverage
support") in Kconfig, and recompile coreboot. coreboot will then
store its code coverage information into CBMEM, if possible.
Then, run "cbmem -CV" as root on the target system running the
instrumented coreboot binary. This will create a whole bunch of
.gcda files that contain coverage information. Tar them up, copy
them to your build system machine, and untar them. Then you can
use your favorite coverage utility (gcov, lcov, ...) to visualize
code coverage.
For a sneak peak of what will expect you, please take a look
at http://www.coreboot.org/~stepan/coreboot-coverage/
Change-Id: Ib287d8309878a1f5c4be770c38b1bc0bb3aa6ec7
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Reviewed-on: http://review.coreboot.org/2052
Tested-by: build bot (Jenkins)
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Martin Roth <martin@se-eng.com>
Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
2012-12-19 01:23:28 +01:00
|
|
|
void *coverage;
|
|
|
|
unsigned long phys_offset;
|
|
|
|
#define phys_to_virt(x) ((void *)(unsigned long)(x) + phys_offset)
|
|
|
|
|
2015-09-30 19:33:01 +02:00
|
|
|
if (find_cbmem_entry(CBMEM_ID_COVERAGE, &start, &size)) {
|
|
|
|
fprintf(stderr, "No coverage information found\n");
|
Implement GCC code coverage analysis
In order to provide some insight on what code is executed during
coreboot's run time and how well our test scenarios work, this
adds code coverage support to coreboot's ram stage. This should
be easily adaptable for payloads, and maybe even romstage.
See http://gcc.gnu.org/onlinedocs/gcc/Gcov.html for
more information.
To instrument coreboot, select CONFIG_COVERAGE ("Code coverage
support") in Kconfig, and recompile coreboot. coreboot will then
store its code coverage information into CBMEM, if possible.
Then, run "cbmem -CV" as root on the target system running the
instrumented coreboot binary. This will create a whole bunch of
.gcda files that contain coverage information. Tar them up, copy
them to your build system machine, and untar them. Then you can
use your favorite coverage utility (gcov, lcov, ...) to visualize
code coverage.
For a sneak peak of what will expect you, please take a look
at http://www.coreboot.org/~stepan/coreboot-coverage/
Change-Id: Ib287d8309878a1f5c4be770c38b1bc0bb3aa6ec7
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Reviewed-on: http://review.coreboot.org/2052
Tested-by: build bot (Jenkins)
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Martin Roth <martin@se-eng.com>
Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
2012-12-19 01:23:28 +01:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Map coverage area */
|
2015-09-30 19:33:01 +02:00
|
|
|
coverage = map_memory_size(start, size, 1);
|
Implement GCC code coverage analysis
In order to provide some insight on what code is executed during
coreboot's run time and how well our test scenarios work, this
adds code coverage support to coreboot's ram stage. This should
be easily adaptable for payloads, and maybe even romstage.
See http://gcc.gnu.org/onlinedocs/gcc/Gcov.html for
more information.
To instrument coreboot, select CONFIG_COVERAGE ("Code coverage
support") in Kconfig, and recompile coreboot. coreboot will then
store its code coverage information into CBMEM, if possible.
Then, run "cbmem -CV" as root on the target system running the
instrumented coreboot binary. This will create a whole bunch of
.gcda files that contain coverage information. Tar them up, copy
them to your build system machine, and untar them. Then you can
use your favorite coverage utility (gcov, lcov, ...) to visualize
code coverage.
For a sneak peak of what will expect you, please take a look
at http://www.coreboot.org/~stepan/coreboot-coverage/
Change-Id: Ib287d8309878a1f5c4be770c38b1bc0bb3aa6ec7
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Reviewed-on: http://review.coreboot.org/2052
Tested-by: build bot (Jenkins)
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Martin Roth <martin@se-eng.com>
Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
2012-12-19 01:23:28 +01:00
|
|
|
phys_offset = (unsigned long)coverage - (unsigned long)start;
|
|
|
|
|
|
|
|
printf("Dumping coverage data...\n");
|
|
|
|
|
|
|
|
struct file *file = (struct file *)coverage;
|
|
|
|
while (file && file->magic == COVERAGE_MAGIC) {
|
|
|
|
FILE *f;
|
|
|
|
char *filename;
|
|
|
|
|
|
|
|
debug(" -> %s\n", (char *)phys_to_virt(file->filename));
|
|
|
|
filename = strdup((char *)phys_to_virt(file->filename));
|
|
|
|
if (mkpath(filename, 0755) == -1) {
|
|
|
|
perror("Directory for coverage data could "
|
|
|
|
"not be created");
|
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
f = fopen(filename, "wb");
|
|
|
|
if (!f) {
|
|
|
|
printf("Could not open %s: %s\n",
|
|
|
|
filename, strerror(errno));
|
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
if (fwrite((void *)phys_to_virt(file->data),
|
|
|
|
file->len, 1, f) != 1) {
|
|
|
|
printf("Could not write to %s: %s\n",
|
|
|
|
filename, strerror(errno));
|
|
|
|
exit(1);
|
|
|
|
}
|
|
|
|
fclose(f);
|
|
|
|
free(filename);
|
|
|
|
|
|
|
|
if (file->next)
|
|
|
|
file = (struct file *)phys_to_virt(file->next);
|
|
|
|
else
|
|
|
|
file = NULL;
|
|
|
|
}
|
|
|
|
unmap_memory();
|
|
|
|
}
|
|
|
|
|
|
|
|
static void print_version(void)
|
2013-01-03 00:43:56 +01:00
|
|
|
{
|
|
|
|
printf("cbmem v%s -- ", CBMEM_VERSION);
|
|
|
|
printf("Copyright (C) 2012 The ChromiumOS Authors. All rights reserved.\n\n");
|
|
|
|
printf(
|
|
|
|
"This program is free software: you can redistribute it and/or modify\n"
|
|
|
|
"it under the terms of the GNU General Public License as published by\n"
|
|
|
|
"the Free Software Foundation, version 2 of the License.\n\n"
|
|
|
|
"This program is distributed in the hope that it will be useful,\n"
|
|
|
|
"but WITHOUT ANY WARRANTY; without even the implied warranty of\n"
|
|
|
|
"MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n"
|
|
|
|
"GNU General Public License for more details.\n\n"
|
|
|
|
"You should have received a copy of the GNU General Public License\n"
|
|
|
|
"along with this program. If not, see <http://www.gnu.org/licenses/>.\n\n");
|
|
|
|
}
|
|
|
|
|
Implement GCC code coverage analysis
In order to provide some insight on what code is executed during
coreboot's run time and how well our test scenarios work, this
adds code coverage support to coreboot's ram stage. This should
be easily adaptable for payloads, and maybe even romstage.
See http://gcc.gnu.org/onlinedocs/gcc/Gcov.html for
more information.
To instrument coreboot, select CONFIG_COVERAGE ("Code coverage
support") in Kconfig, and recompile coreboot. coreboot will then
store its code coverage information into CBMEM, if possible.
Then, run "cbmem -CV" as root on the target system running the
instrumented coreboot binary. This will create a whole bunch of
.gcda files that contain coverage information. Tar them up, copy
them to your build system machine, and untar them. Then you can
use your favorite coverage utility (gcov, lcov, ...) to visualize
code coverage.
For a sneak peak of what will expect you, please take a look
at http://www.coreboot.org/~stepan/coreboot-coverage/
Change-Id: Ib287d8309878a1f5c4be770c38b1bc0bb3aa6ec7
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Reviewed-on: http://review.coreboot.org/2052
Tested-by: build bot (Jenkins)
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Martin Roth <martin@se-eng.com>
Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
2012-12-19 01:23:28 +01:00
|
|
|
static void print_usage(const char *name)
|
2013-01-03 00:43:56 +01:00
|
|
|
{
|
2015-08-31 05:00:12 +02:00
|
|
|
printf("usage: %s [-cCltTxVvh?]\n", name);
|
2013-01-03 00:43:56 +01:00
|
|
|
printf("\n"
|
2013-01-07 22:37:12 +01:00
|
|
|
" -c | --console: print cbmem console\n"
|
Implement GCC code coverage analysis
In order to provide some insight on what code is executed during
coreboot's run time and how well our test scenarios work, this
adds code coverage support to coreboot's ram stage. This should
be easily adaptable for payloads, and maybe even romstage.
See http://gcc.gnu.org/onlinedocs/gcc/Gcov.html for
more information.
To instrument coreboot, select CONFIG_COVERAGE ("Code coverage
support") in Kconfig, and recompile coreboot. coreboot will then
store its code coverage information into CBMEM, if possible.
Then, run "cbmem -CV" as root on the target system running the
instrumented coreboot binary. This will create a whole bunch of
.gcda files that contain coverage information. Tar them up, copy
them to your build system machine, and untar them. Then you can
use your favorite coverage utility (gcov, lcov, ...) to visualize
code coverage.
For a sneak peak of what will expect you, please take a look
at http://www.coreboot.org/~stepan/coreboot-coverage/
Change-Id: Ib287d8309878a1f5c4be770c38b1bc0bb3aa6ec7
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Reviewed-on: http://review.coreboot.org/2052
Tested-by: build bot (Jenkins)
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Martin Roth <martin@se-eng.com>
Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
2012-12-19 01:23:28 +01:00
|
|
|
" -C | --coverage: dump coverage information\n"
|
2013-01-08 01:26:10 +01:00
|
|
|
" -l | --list: print cbmem table of contents\n"
|
2013-07-17 02:47:35 +02:00
|
|
|
" -x | --hexdump: print hexdump of cbmem area\n"
|
2013-01-07 22:37:12 +01:00
|
|
|
" -t | --timestamps: print timestamp information\n"
|
2015-08-31 05:00:12 +02:00
|
|
|
" -T | --parseable-timestamps: print parseable timestamps\n"
|
2013-01-07 22:37:12 +01:00
|
|
|
" -V | --verbose: verbose (debugging) output\n"
|
2013-01-03 00:43:56 +01:00
|
|
|
" -v | --version: print the version\n"
|
|
|
|
" -h | --help: print this help\n"
|
|
|
|
"\n");
|
|
|
|
exit(1);
|
|
|
|
}
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
|
2014-06-17 08:02:03 +02:00
|
|
|
#ifdef __arm__
|
|
|
|
static void dt_update_cells(const char *name, int *addr_cells_ptr,
|
|
|
|
int *size_cells_ptr)
|
|
|
|
{
|
|
|
|
if (*addr_cells_ptr >= 0 && *size_cells_ptr >= 0)
|
|
|
|
return;
|
|
|
|
|
|
|
|
int buffer;
|
|
|
|
size_t nlen = strlen(name);
|
|
|
|
char *prop = alloca(nlen + sizeof("/#address-cells"));
|
|
|
|
strcpy(prop, name);
|
|
|
|
|
|
|
|
if (*addr_cells_ptr < 0) {
|
|
|
|
strcpy(prop + nlen, "/#address-cells");
|
|
|
|
int fd = open(prop, O_RDONLY);
|
|
|
|
if (fd < 0 && errno != ENOENT) {
|
|
|
|
perror(prop);
|
|
|
|
} else if (fd >= 0) {
|
|
|
|
if (read(fd, &buffer, sizeof(int)) < 0)
|
|
|
|
perror(prop);
|
|
|
|
else
|
|
|
|
*addr_cells_ptr = ntohl(buffer);
|
|
|
|
close(fd);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
if (*size_cells_ptr < 0) {
|
|
|
|
strcpy(prop + nlen, "/#size-cells");
|
|
|
|
int fd = open(prop, O_RDONLY);
|
|
|
|
if (fd < 0 && errno != ENOENT) {
|
|
|
|
perror(prop);
|
|
|
|
} else if (fd >= 0) {
|
|
|
|
if (read(fd, &buffer, sizeof(int)) < 0)
|
|
|
|
perror(prop);
|
|
|
|
else
|
|
|
|
*size_cells_ptr = ntohl(buffer);
|
|
|
|
close(fd);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static char *dt_find_compat(const char *parent, const char *compat,
|
|
|
|
int *addr_cells_ptr, int *size_cells_ptr)
|
|
|
|
{
|
|
|
|
char *ret = NULL;
|
|
|
|
struct dirent *entry;
|
|
|
|
DIR *dir;
|
|
|
|
|
|
|
|
if (!(dir = opendir(parent))) {
|
|
|
|
perror(parent);
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Loop through all files in the directory (DT node). */
|
|
|
|
while ((entry = readdir(dir))) {
|
|
|
|
/* We only care about compatible props or subnodes. */
|
|
|
|
if (entry->d_name[0] == '.' || !((entry->d_type & DT_DIR) ||
|
|
|
|
!strcmp(entry->d_name, "compatible")))
|
|
|
|
continue;
|
|
|
|
|
|
|
|
/* Assemble the file name (on the stack, for speed). */
|
|
|
|
size_t plen = strlen(parent);
|
|
|
|
char *name = alloca(plen + strlen(entry->d_name) + 2);
|
|
|
|
|
|
|
|
strcpy(name, parent);
|
|
|
|
name[plen] = '/';
|
|
|
|
strcpy(name + plen + 1, entry->d_name);
|
|
|
|
|
|
|
|
/* If it's a subnode, recurse. */
|
|
|
|
if (entry->d_type & DT_DIR) {
|
|
|
|
ret = dt_find_compat(name, compat, addr_cells_ptr,
|
|
|
|
size_cells_ptr);
|
|
|
|
|
|
|
|
/* There is only one matching node to find, abort. */
|
|
|
|
if (ret) {
|
|
|
|
/* Gather cells values on the way up. */
|
|
|
|
dt_update_cells(parent, addr_cells_ptr,
|
|
|
|
size_cells_ptr);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* If it's a compatible string, see if it's the right one. */
|
|
|
|
int fd = open(name, O_RDONLY);
|
|
|
|
int clen = strlen(compat);
|
|
|
|
char *buffer = alloca(clen + 1);
|
|
|
|
|
|
|
|
if (fd < 0) {
|
|
|
|
perror(name);
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (read(fd, buffer, clen + 1) < 0) {
|
|
|
|
perror(name);
|
|
|
|
close(fd);
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
close(fd);
|
|
|
|
|
|
|
|
if (!strcmp(compat, buffer)) {
|
|
|
|
/* Initialize these to "unset" for the way up. */
|
|
|
|
*addr_cells_ptr = *size_cells_ptr = -1;
|
|
|
|
|
|
|
|
/* Can't leave string on the stack or we'll lose it! */
|
|
|
|
ret = strdup(parent);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
closedir(dir);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
#endif /* __arm__ */
|
|
|
|
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
int main(int argc, char** argv)
|
|
|
|
{
|
2013-01-07 22:37:12 +01:00
|
|
|
int print_defaults = 1;
|
|
|
|
int print_console = 0;
|
Implement GCC code coverage analysis
In order to provide some insight on what code is executed during
coreboot's run time and how well our test scenarios work, this
adds code coverage support to coreboot's ram stage. This should
be easily adaptable for payloads, and maybe even romstage.
See http://gcc.gnu.org/onlinedocs/gcc/Gcov.html for
more information.
To instrument coreboot, select CONFIG_COVERAGE ("Code coverage
support") in Kconfig, and recompile coreboot. coreboot will then
store its code coverage information into CBMEM, if possible.
Then, run "cbmem -CV" as root on the target system running the
instrumented coreboot binary. This will create a whole bunch of
.gcda files that contain coverage information. Tar them up, copy
them to your build system machine, and untar them. Then you can
use your favorite coverage utility (gcov, lcov, ...) to visualize
code coverage.
For a sneak peak of what will expect you, please take a look
at http://www.coreboot.org/~stepan/coreboot-coverage/
Change-Id: Ib287d8309878a1f5c4be770c38b1bc0bb3aa6ec7
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Reviewed-on: http://review.coreboot.org/2052
Tested-by: build bot (Jenkins)
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Martin Roth <martin@se-eng.com>
Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
2012-12-19 01:23:28 +01:00
|
|
|
int print_coverage = 0;
|
2013-01-08 01:26:10 +01:00
|
|
|
int print_list = 0;
|
2013-07-17 02:47:35 +02:00
|
|
|
int print_hexdump = 0;
|
2013-01-07 22:37:12 +01:00
|
|
|
int print_timestamps = 0;
|
2015-08-31 05:00:12 +02:00
|
|
|
int machine_readable_timestamps = 0;
|
2013-01-03 23:30:33 +01:00
|
|
|
|
2013-01-03 00:43:56 +01:00
|
|
|
int opt, option_index = 0;
|
|
|
|
static struct option long_options[] = {
|
2013-01-07 22:37:12 +01:00
|
|
|
{"console", 0, 0, 'c'},
|
Implement GCC code coverage analysis
In order to provide some insight on what code is executed during
coreboot's run time and how well our test scenarios work, this
adds code coverage support to coreboot's ram stage. This should
be easily adaptable for payloads, and maybe even romstage.
See http://gcc.gnu.org/onlinedocs/gcc/Gcov.html for
more information.
To instrument coreboot, select CONFIG_COVERAGE ("Code coverage
support") in Kconfig, and recompile coreboot. coreboot will then
store its code coverage information into CBMEM, if possible.
Then, run "cbmem -CV" as root on the target system running the
instrumented coreboot binary. This will create a whole bunch of
.gcda files that contain coverage information. Tar them up, copy
them to your build system machine, and untar them. Then you can
use your favorite coverage utility (gcov, lcov, ...) to visualize
code coverage.
For a sneak peak of what will expect you, please take a look
at http://www.coreboot.org/~stepan/coreboot-coverage/
Change-Id: Ib287d8309878a1f5c4be770c38b1bc0bb3aa6ec7
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Reviewed-on: http://review.coreboot.org/2052
Tested-by: build bot (Jenkins)
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Martin Roth <martin@se-eng.com>
Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
2012-12-19 01:23:28 +01:00
|
|
|
{"coverage", 0, 0, 'C'},
|
2013-01-08 01:26:10 +01:00
|
|
|
{"list", 0, 0, 'l'},
|
2013-01-07 22:37:12 +01:00
|
|
|
{"timestamps", 0, 0, 't'},
|
2015-08-31 05:00:12 +02:00
|
|
|
{"parseable-timestamps", 0, 0, 'T'},
|
2013-07-17 02:47:35 +02:00
|
|
|
{"hexdump", 0, 0, 'x'},
|
2013-01-03 23:30:33 +01:00
|
|
|
{"verbose", 0, 0, 'V'},
|
2013-01-03 00:43:56 +01:00
|
|
|
{"version", 0, 0, 'v'},
|
|
|
|
{"help", 0, 0, 'h'},
|
|
|
|
{0, 0, 0, 0}
|
|
|
|
};
|
2015-08-31 05:00:12 +02:00
|
|
|
while ((opt = getopt_long(argc, argv, "cCltTxVvh?",
|
2013-01-03 00:43:56 +01:00
|
|
|
long_options, &option_index)) != EOF) {
|
|
|
|
switch (opt) {
|
2013-01-07 22:37:12 +01:00
|
|
|
case 'c':
|
|
|
|
print_console = 1;
|
|
|
|
print_defaults = 0;
|
|
|
|
break;
|
Implement GCC code coverage analysis
In order to provide some insight on what code is executed during
coreboot's run time and how well our test scenarios work, this
adds code coverage support to coreboot's ram stage. This should
be easily adaptable for payloads, and maybe even romstage.
See http://gcc.gnu.org/onlinedocs/gcc/Gcov.html for
more information.
To instrument coreboot, select CONFIG_COVERAGE ("Code coverage
support") in Kconfig, and recompile coreboot. coreboot will then
store its code coverage information into CBMEM, if possible.
Then, run "cbmem -CV" as root on the target system running the
instrumented coreboot binary. This will create a whole bunch of
.gcda files that contain coverage information. Tar them up, copy
them to your build system machine, and untar them. Then you can
use your favorite coverage utility (gcov, lcov, ...) to visualize
code coverage.
For a sneak peak of what will expect you, please take a look
at http://www.coreboot.org/~stepan/coreboot-coverage/
Change-Id: Ib287d8309878a1f5c4be770c38b1bc0bb3aa6ec7
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Reviewed-on: http://review.coreboot.org/2052
Tested-by: build bot (Jenkins)
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Martin Roth <martin@se-eng.com>
Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
2012-12-19 01:23:28 +01:00
|
|
|
case 'C':
|
|
|
|
print_coverage = 1;
|
|
|
|
print_defaults = 0;
|
|
|
|
break;
|
2013-01-08 01:26:10 +01:00
|
|
|
case 'l':
|
|
|
|
print_list = 1;
|
|
|
|
print_defaults = 0;
|
|
|
|
break;
|
2013-07-17 02:47:35 +02:00
|
|
|
case 'x':
|
|
|
|
print_hexdump = 1;
|
|
|
|
print_defaults = 0;
|
|
|
|
break;
|
2013-01-07 22:37:12 +01:00
|
|
|
case 't':
|
|
|
|
print_timestamps = 1;
|
|
|
|
print_defaults = 0;
|
|
|
|
break;
|
2015-08-31 05:00:12 +02:00
|
|
|
case 'T':
|
|
|
|
print_timestamps = 1;
|
|
|
|
machine_readable_timestamps = 1;
|
|
|
|
print_defaults = 0;
|
|
|
|
break;
|
2013-01-03 23:30:33 +01:00
|
|
|
case 'V':
|
|
|
|
verbose = 1;
|
|
|
|
break;
|
2013-01-03 00:43:56 +01:00
|
|
|
case 'v':
|
|
|
|
print_version();
|
|
|
|
exit(0);
|
|
|
|
break;
|
|
|
|
case 'h':
|
|
|
|
case '?':
|
|
|
|
default:
|
|
|
|
print_usage(argv[0]);
|
|
|
|
exit(0);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
|
2014-06-17 08:02:03 +02:00
|
|
|
mem_fd = open("/dev/mem", O_RDONLY, 0);
|
|
|
|
if (mem_fd < 0) {
|
2013-01-03 23:30:33 +01:00
|
|
|
fprintf(stderr, "Failed to gain memory access: %s\n",
|
|
|
|
strerror(errno));
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2013-06-20 00:39:09 +02:00
|
|
|
#ifdef __arm__
|
2014-06-17 08:02:03 +02:00
|
|
|
int addr_cells, size_cells;
|
|
|
|
char *coreboot_node = dt_find_compat("/proc/device-tree", "coreboot",
|
|
|
|
&addr_cells, &size_cells);
|
2013-06-20 00:39:09 +02:00
|
|
|
|
2014-06-17 08:02:03 +02:00
|
|
|
if (!coreboot_node) {
|
|
|
|
fprintf(stderr, "Could not find 'coreboot' compatible node!\n");
|
2013-06-20 00:39:09 +02:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2014-06-17 08:02:03 +02:00
|
|
|
if (addr_cells < 0) {
|
|
|
|
fprintf(stderr, "Warning: no #address-cells node in tree!\n");
|
|
|
|
addr_cells = 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
int nlen = strlen(coreboot_node);
|
|
|
|
char *reg = alloca(nlen + sizeof("/reg"));
|
|
|
|
|
|
|
|
strcpy(reg, coreboot_node);
|
|
|
|
strcpy(reg + nlen, "/reg");
|
|
|
|
free(coreboot_node);
|
|
|
|
|
|
|
|
int fd = open(reg, O_RDONLY);
|
|
|
|
if (fd < 0) {
|
|
|
|
perror(reg);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
int i;
|
2014-10-07 21:56:35 +02:00
|
|
|
size_t size_to_read = addr_cells * 4 + size_cells * 4;
|
|
|
|
u8 *dtbuffer = alloca(size_to_read);
|
|
|
|
if (read(fd, dtbuffer, size_to_read) < 0) {
|
2014-06-17 08:02:03 +02:00
|
|
|
perror(reg);
|
2013-06-20 00:39:09 +02:00
|
|
|
return 1;
|
|
|
|
}
|
2014-06-17 08:02:03 +02:00
|
|
|
close(fd);
|
2013-06-20 00:39:09 +02:00
|
|
|
|
2014-06-17 08:02:03 +02:00
|
|
|
/* No variable-length byte swap function anywhere in C... how sad. */
|
|
|
|
u64 baseaddr = 0;
|
|
|
|
for (i = 0; i < addr_cells * 4; i++) {
|
|
|
|
baseaddr <<= 8;
|
2014-10-07 21:56:35 +02:00
|
|
|
baseaddr |= *dtbuffer;
|
|
|
|
dtbuffer++;
|
|
|
|
}
|
|
|
|
u64 cb_table_size = 0;
|
|
|
|
for (i = 0; i < size_cells * 4; i++) {
|
|
|
|
cb_table_size <<= 8;
|
|
|
|
cb_table_size |= *dtbuffer;
|
|
|
|
dtbuffer++;
|
2014-06-17 08:02:03 +02:00
|
|
|
}
|
|
|
|
|
2015-09-06 01:07:17 +02:00
|
|
|
parse_cbtable(baseaddr, cb_table_size, 1);
|
2013-06-20 00:39:09 +02:00
|
|
|
#else
|
|
|
|
int j;
|
|
|
|
static const int possible_base_addresses[] = { 0, 0xf0000 };
|
|
|
|
|
2013-01-03 23:30:33 +01:00
|
|
|
/* Find and parse coreboot table */
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
for (j = 0; j < ARRAY_SIZE(possible_base_addresses); j++) {
|
2015-09-06 01:07:17 +02:00
|
|
|
if (parse_cbtable(possible_base_addresses[j], MAP_BYTES, 1))
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
break;
|
|
|
|
}
|
2013-06-20 00:39:09 +02:00
|
|
|
#endif
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
|
2013-01-07 22:37:12 +01:00
|
|
|
if (print_console)
|
|
|
|
dump_console();
|
|
|
|
|
Implement GCC code coverage analysis
In order to provide some insight on what code is executed during
coreboot's run time and how well our test scenarios work, this
adds code coverage support to coreboot's ram stage. This should
be easily adaptable for payloads, and maybe even romstage.
See http://gcc.gnu.org/onlinedocs/gcc/Gcov.html for
more information.
To instrument coreboot, select CONFIG_COVERAGE ("Code coverage
support") in Kconfig, and recompile coreboot. coreboot will then
store its code coverage information into CBMEM, if possible.
Then, run "cbmem -CV" as root on the target system running the
instrumented coreboot binary. This will create a whole bunch of
.gcda files that contain coverage information. Tar them up, copy
them to your build system machine, and untar them. Then you can
use your favorite coverage utility (gcov, lcov, ...) to visualize
code coverage.
For a sneak peak of what will expect you, please take a look
at http://www.coreboot.org/~stepan/coreboot-coverage/
Change-Id: Ib287d8309878a1f5c4be770c38b1bc0bb3aa6ec7
Signed-off-by: Stefan Reinauer <reinauer@google.com>
Reviewed-on: http://review.coreboot.org/2052
Tested-by: build bot (Jenkins)
Reviewed-by: David Hendricks <dhendrix@chromium.org>
Reviewed-by: Martin Roth <martin@se-eng.com>
Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
2012-12-19 01:23:28 +01:00
|
|
|
if (print_coverage)
|
|
|
|
dump_coverage();
|
|
|
|
|
2013-01-08 01:26:10 +01:00
|
|
|
if (print_list)
|
|
|
|
dump_cbmem_toc();
|
|
|
|
|
2013-07-17 02:47:35 +02:00
|
|
|
if (print_hexdump)
|
|
|
|
dump_cbmem_hex();
|
|
|
|
|
2013-01-07 22:37:12 +01:00
|
|
|
if (print_defaults || print_timestamps)
|
2015-08-31 05:00:12 +02:00
|
|
|
dump_timestamps(machine_readable_timestamps);
|
2013-01-03 23:30:33 +01:00
|
|
|
|
2014-06-17 08:02:03 +02:00
|
|
|
close(mem_fd);
|
Utility to dump boot timing table
Coreboot and u-boot create a table of timestamps which allows to see
the boot process performance. The util/cbmem/cbmem.py script allows to
access the table after ChromeOS boots up and display its contents on
the console. The problem is that shipping images do not include Python
interpreter, so there is no way to access the table on a production
machine.
This change introduces a utility which is a Linux app displaying the
timestamp table. Conceivably the output of this utility might be
included in one of the ChromeOS :/system sections, so it was attempted
to write this procedure 'fail safe', namely reporting errors and not
continuing processing if something goes wrong.
Including of coreboot/src .h files will allow to keep the firmware
timestamp implementation and this utility in sync in the future.
Test:
. build the utility (run 'make' while in chroot in util/cbmem)
. copy `cbmem' and 'cbmem.py' to the target
. run both utilities (limiting cbmem.py output to 25 lines or so)
. observe that the generated tables are identical (modulo rounding
up of int division, resulting in 1 ns discrepancies in some
cases)
localhost var # ./cbmem
18 entries total:
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
localhost var # ./cbmem.py | head -25
time base 4249800, total entries 18
1:62,080
2:64,569 (2,489)
3:82,520 (17,951)
4:82,695 (174)
8:84,384 (1,688)
9:131,731 (47,347)
10:131,821 (89)
30:131,849 (27)
40:132,618 (769)
50:134,594 (1,975)
60:134,729 (134)
70:363,440 (228,710)
75:363,453 (13)
80:368,165 (4,711)
90:370,018 (1,852)
99:488,217 (118,199)
1000:491,324 (3,107)
1100:760,475 (269,150)
Change-Id: I013e594d4afe323106d88e7938dd40b17760621c
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://review.coreboot.org/1759
Tested-by: build bot (Jenkins)
Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
2012-09-28 04:24:07 +02:00
|
|
|
return 0;
|
|
|
|
}
|