Does the Halting Necessary for Hardware Trace Collection Inordinately Perturb the Results?
Processor address traces are invaluable for characterizing workloads and testing proposed memory hierarchies. Long traces are needed to exercise modern cache designs and produce meaningful results, but are difficult to collect with hardware monitors because microprocessors access memory too frequent...
Main Author: | |
---|---|
Format: | Others |
Published: |
BYU ScholarsArchive
2004
|
Subjects: | |
Online Access: | https://scholarsarchive.byu.edu/etd/201 https://scholarsarchive.byu.edu/cgi/viewcontent.cgi?article=1200&context=etd |
id |
ndltd-BGMYU2-oai-scholarsarchive.byu.edu-etd-1200 |
---|---|
record_format |
oai_dc |
spelling |
ndltd-BGMYU2-oai-scholarsarchive.byu.edu-etd-12002021-09-01T05:00:53Z Does the Halting Necessary for Hardware Trace Collection Inordinately Perturb the Results? Watson, Myles G. Processor address traces are invaluable for characterizing workloads and testing proposed memory hierarchies. Long traces are needed to exercise modern cache designs and produce meaningful results, but are difficult to collect with hardware monitors because microprocessors access memory too frequently for disks or other large storage to keep up. The small, fast buffers of the monitors fill quickly; in order to obtain long contiguous traces, the processor must be stopped while the buffer is emptied. This halting may perturb the traces collected, but this cannot be measured directly, since long uninterrupted traces cannot be collected. We make the case that hardware performance counters, which collect runtime statistics without influencing execution, can be used to measure halting effects. We use the performance counters of the Pentium 4 processor to collect statistics while halting the processor as if traces were being collected. We then compare these results to the statistics obtained from unhalted runs. We present our results in terms of which counters are affected, why, and what this means for trace-collection systems. 2004-11-16T08:00:00Z text application/pdf https://scholarsarchive.byu.edu/etd/201 https://scholarsarchive.byu.edu/cgi/viewcontent.cgi?article=1200&context=etd http://lib.byu.edu/about/copyright/ Theses and Dissertations BYU ScholarsArchive performance counters processor hardware tracing address trace collection Computer Sciences |
collection |
NDLTD |
format |
Others
|
sources |
NDLTD |
topic |
performance counters processor hardware tracing address trace collection Computer Sciences |
spellingShingle |
performance counters processor hardware tracing address trace collection Computer Sciences Watson, Myles G. Does the Halting Necessary for Hardware Trace Collection Inordinately Perturb the Results? |
description |
Processor address traces are invaluable for characterizing workloads and testing proposed memory hierarchies. Long traces are needed to exercise modern cache designs and produce meaningful results, but are difficult to collect with hardware monitors because microprocessors access memory too frequently for disks or other large storage to keep up. The small, fast buffers of the monitors fill quickly; in order to obtain long contiguous traces, the processor must be stopped while the buffer is emptied. This halting may perturb the traces collected, but this cannot be measured directly, since long uninterrupted traces cannot be collected. We make the case that hardware performance counters, which collect runtime statistics without influencing execution, can be used to measure halting effects. We use the performance counters of the Pentium 4 processor to collect statistics while halting the processor as if traces were being collected. We then compare these results to the statistics obtained from unhalted runs. We present our results in terms of which counters are affected, why, and what this means for trace-collection systems. |
author |
Watson, Myles G. |
author_facet |
Watson, Myles G. |
author_sort |
Watson, Myles G. |
title |
Does the Halting Necessary for Hardware Trace Collection Inordinately Perturb the Results? |
title_short |
Does the Halting Necessary for Hardware Trace Collection Inordinately Perturb the Results? |
title_full |
Does the Halting Necessary for Hardware Trace Collection Inordinately Perturb the Results? |
title_fullStr |
Does the Halting Necessary for Hardware Trace Collection Inordinately Perturb the Results? |
title_full_unstemmed |
Does the Halting Necessary for Hardware Trace Collection Inordinately Perturb the Results? |
title_sort |
does the halting necessary for hardware trace collection inordinately perturb the results? |
publisher |
BYU ScholarsArchive |
publishDate |
2004 |
url |
https://scholarsarchive.byu.edu/etd/201 https://scholarsarchive.byu.edu/cgi/viewcontent.cgi?article=1200&context=etd |
work_keys_str_mv |
AT watsonmylesg doesthehaltingnecessaryforhardwaretracecollectioninordinatelyperturbtheresults |
_version_ |
1719473106004738048 |