-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lisa.tests.cpufreq.schedutil: Add LargeStepUp test for ramp boost fea… #1011
lisa.tests.cpufreq.schedutil: Add LargeStepUp test for ramp boost fea… #1011
Conversation
33cbfae
to
e2010a4
Compare
e2010a4
to
4b15878
Compare
# Tolerate a few bad samples that added too much boost | ||
passed_shape = bad_shape_pct < bad_samples_threshold_pct | ||
|
||
passed = passed_overhead and passed_shape |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to split these into two separate tests? We'd get finer grained results.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if that would really help, all these checks are just checking the overall shape of the signal. If I could simulate the signals with 100% accuracy, they would all go away and replaced by a Series equality check.
|
||
# Ensure accurate duty cycle and idle state misprediction on some | ||
# boards. This helps having predictable execution. | ||
with target.disable_idle_states(): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We keep carrying over an explanation as to why we do this... Perhaps we should stick it in a load-tracking specific "I care about signals so give me a white room` context manager.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good cleanup idea, added to the TODO list
4b15878
to
ee8bcac
Compare
…ture Provide a test for the ramp boost feature as posted on LKML. This test will mostly catch cases where schedutil is not called as often as expected, since it reads most of the signals from the kernel instead of guessing them.
ee8bcac
to
b282ec9
Compare
…ture
Provide a test for the ramp boost feature as posted on LKML.
This test will mostly catch cases where schedutil is not called as often as
expected, since it reads most of the signals from the kernel instead of guessing
them.