Luc Michel a6414d3b59 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>		2020-10-27 11:10:44 +00:00
..
bus.c
clock-vmstate.c
clock.c	hw/core/clock: trace clock values in Hz instead of ns	2020-10-27 11:10:44 +00:00
cpu.c
fw-path-provider.c
generic-loader.c
hotplug.c
irq.c
Kconfig
loader-fit.c
loader.c
machine-hmp-cmds.c
machine-qmp-cmds.c
machine.c	machine: move SMP initialization from vl.c	2020-10-26 07:08:40 -04:00
meson.build
nmi.c
null-machine.c
numa.c
or-irq.c
platform-bus.c
ptimer.c
qdev-clock.c
qdev-fw.c
qdev-prop-internal.h
qdev-properties-system.c
qdev-properties.c
qdev.c
register.c
reset.c
resettable.c
split-irq.c
stream.c
sysbus.c
trace-events	hw/core/clock: trace clock values in Hz instead of ns	2020-10-27 11:10:44 +00:00
trace.h
uboot_image.h
vm-change-state-handler.c
vmstate-if.c