aboutsummaryrefslogtreecommitdiff
path: root/scripts/oss-fuzz
diff options
context:
space:
mode:
authorLuc Michel <luc@lmichel.fr>2020-10-10 15:57:46 +0200
committerPeter Maydell <peter.maydell@linaro.org>2020-10-27 11:10:44 +0000
commita6414d3b59fe8666a7b093cdcf23c747ce3055b8 (patch)
tree3550ec9205c4b83683208f0c422990d790845be8 /scripts/oss-fuzz
parentf6f3c9b0f783d47ffab961ea18685e30a85f5818 (diff)
downloadqemu-a6414d3b59fe8666a7b093cdcf23c747ce3055b8.zip
qemu-a6414d3b59fe8666a7b093cdcf23c747ce3055b8.tar.gz
qemu-a6414d3b59fe8666a7b093cdcf23c747ce3055b8.tar.bz2
hw/core/clock: trace clock values in Hz instead of ns
The nanosecond unit greatly limits the dynamic range we can display in clock value traces, for values in the order of 1GHz and more. The internal representation can go way beyond this value and it is quite common for today's clocks to be within those ranges. For example, a frequency between 500MHz+ and 1GHz will be displayed as 1ns. Beyond 1GHz, it will show up as 0ns. Replace nanosecond periods traces with frequencies in the Hz unit to have more dynamic range in the trace output. Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org> Reviewed-by: Damien Hedde <damien.hedde@greensocs.com> Signed-off-by: Luc Michel <luc@lmichel.fr> Tested-by: Guenter Roeck <linux@roeck-us.net> Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Diffstat (limited to 'scripts/oss-fuzz')
0 files changed, 0 insertions, 0 deletions