#
56ed7870 |
| 15-Dec-2022 |
Josh Lehan <krellan@google.com> |
Fixing crash when core logging was enabled
The operator=() function tried to use the "=" operator to copy the entire structure at once, which of course called the same function again, leading to inf
Fixing crash when core logging was enabled
The operator=() function tried to use the "=" operator to copy the entire structure at once, which of course called the same function again, leading to infinite recursion, and thus, segfault.
Worked around this braino by simply copying each field individually, forgoing the convenience of copying the structure as a whole.
Tested: Use of the core logging feature no longer crashes
Signed-off-by: Josh Lehan <krellan@google.com> Change-Id: Id472d03409296a45bb14180f5c1897dfb42be1aa
show more ...
|
#
de74542c |
| 07-Nov-2020 |
Josh Lehan <krellan@google.com> |
Adding new feature of core PID loop logging
This differs from the normal logging, as this focuses on the core of the PID loop computations.
All variables within the core pid/ec/pid.cpp pid() functi
Adding new feature of core PID loop logging
This differs from the normal logging, as this focuses on the core of the PID loop computations.
All variables within the core pid/ec/pid.cpp pid() function are now logged, so math can be debugged.
Output is throttled to only log a new line when it changes, or when 60 seconds have elapsed.
Creates 2 files for each PID loop, one showing coefficients that were configured for it, and one showing the variables changing over time.
Enable by --corelogging command line option, or by creating /etc/thermal.d/corelogging file.
Tested: Log files appear as expected, when enabled. No changes noticed, when this feature is disabled.
Signed-off-by: Josh Lehan <krellan@google.com> Change-Id: I3f37fe918e7cbc6fb885ffa2f268600d5a317d32
show more ...
|