Skip to content
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

Adding Frequency Latency Estimation via CPU Clock Modulation (Duty Cycle Modulation) #1

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

weiwangudel
Copy link

Using "#ifndef DCM" macro to leave the original DVFS latency estimation code unchanged. Minimal/Zero impact to original FTaLaT code functionality.
Enhance the tool with DCM estimation which enables DCM and DVFS comparison.

Thanks!

Wei Wang

weiwangudel and others added 4 commits July 7, 2015 21:42
The model exited complaining about confidency overlap. Need to figure out why.
Cannot estimate latency of clock modulation.
Use uint64_t is somehow important for MSRWRITE to 0x19a.
@weiwangudel
Copy link
Author

Sorry, missing one commit. Will close and open another request.

@weiwangudel weiwangudel closed this Aug 5, 2015
@weiwangudel
Copy link
Author

Sorry, reopen it. Did not miss today's commit. Recent commit is in the bottom.

@weiwangudel weiwangudel reopened this Aug 5, 2015
echo "############################" >> ${OUTPUT_DIR}/${OUTPUT_FILE}"_"${startFreq}"-"${testFreq}${OUTPUT_EXT}
done
fi
setDutyCycle-16.exe
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see from where this is coming.

@weiwangudel
Copy link
Author

Thanks for reviewing the code!
ftalat_dcm_runner.sh is adapted from ftalat_runner.sh
The line 50 "setDutyCycle-16.exe" actually is a compiled program that resets the frequency to "nominal". I think I can remove the 50th line.
Alternatively, I can re-work on the source code of setDutyCycle-16.exe and commit it.
Which do you prefer?

Thanks!

Wei

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants