User:GNUtoo/Benchmarks: Difference between revisions

From flashrom
Jump to navigation Jump to search
(Created page with "== Methodologies and usual caveats == * The time command doesn't print how long a command ran, instead it measures resource usages, like CPU time. * When writing to a flash ch...")
 
Line 1: Line 1:
== Methodologies and usual caveats ==
== Methodologies and usual caveats ==
* The time command doesn't print how long a command ran, instead it measures resource usages, like CPU time.
* When writing to a flash chip, flashrom will read it, then write the differences and read it again to verify it was written correctly. Because it only writes the differences, benchmarks needs to take it into account by erasing the flash or flashing an known image before starting the test.
* When writing to a flash chip, flashrom will read it, then write the differences and read it again to verify it was written correctly. Because it only writes the differences, benchmarks needs to take it into account by erasing the flash or flashing an known image before starting the test.
* Coreboot has reproducible builds. This can be used to share an image to flash.
* Coreboot has reproducible builds. This can be used to share an image to flash.
* If flashrom failed to write some zones, it might try again. TODO: Verify if/when it prints a warning.
* If flashrom failed to write some zones, it might try again. TODO: Verify if/when it prints a warning.

Revision as of 10:33, 11 June 2017

Methodologies and usual caveats

  • When writing to a flash chip, flashrom will read it, then write the differences and read it again to verify it was written correctly. Because it only writes the differences, benchmarks needs to take it into account by erasing the flash or flashing an known image before starting the test.
  • Coreboot has reproducible builds. This can be used to share an image to flash.
  • If flashrom failed to write some zones, it might try again. TODO: Verify if/when it prints a warning.