Linux Foundation Wiki

project collaboration site

User Tools

Site Tools


realtime:documentation:howto:debugging:smi-latency:detection

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

realtime:documentation:howto:debugging:smi-latency:detection [2018/07/12 13:48]
ebugden created
realtime:documentation:howto:debugging:smi-latency:detection [2018/07/13 06:49] (current)
ebugden Clarify sentence
Line 12: Line 12:
 ---- ----
  
-It is important to note that there are intentionally only a few vague suggestions about how long it should take to handle an SMI in the pages linked above. This is because, in the case of SMI handling, the definition of "too long" depends on the application'​s timing requirements. More specifically,​ the maximum number of SMIs, the maximum frequency at which they can occur, and the maximum amount of time it can take to handle ​them, all depend on the application'​s requirements. One application might be able to handle several SMIs that take 10-15 us to resolve whereas those times may be way too long for another application. Additionally,​ an SMI related latency of over 100 us is generally bad, but again the timing requirements of certain applications could allow for such latencies. So, a knowledge of the system'​s deadline requirements is absolutely necessary for interpreting the results of the suggested tests.+It is important to note that there are intentionally only a few vague suggestions about how long it should take to handle an SMI in the pages linked above. This is because, in the case of SMI handling, the definition of "too long" depends on the application'​s timing requirements. More specifically,​ the maximum number of SMIs, the maximum frequency at which SMIs can occur, and the maximum amount of time it can take to handle ​SMIs, all depend on the application'​s requirements. One application might be able to handle several SMIs that take 10-15 us to resolve whereas those times may be way too long for another application. Additionally,​ an SMI related latency of over 100 us is generally bad, but again the timing requirements of certain applications could allow for such latencies. So, a knowledge of the system'​s deadline requirements is absolutely necessary for interpreting the results of the suggested tests.
  
 ===== Common SMI Triggers ===== ===== Common SMI Triggers =====
realtime/documentation/howto/debugging/smi-latency/detection.1531403303.txt.gz ยท Last modified: 2018/07/12 13:48 by ebugden