Lines Matching full:interrupt
46 regularly sampling the current registers on each CPU (from an interrupt handler, the
47 saved PC value at the time of interrupt is stored), and converting that runtime PC
52 of which task was running at the time of the interrupt, and converting into a file offset
64 reflect reality. In common operation, the time between each sample interrupt is regulated
74 increment once per each event, and generate an interrupt on reaching some pre-defined
83 interrupt after a set number of "events" (in this case an event is one
84 clock cycle). It should be clear that the chances of the interrupt
88 events, providing that the interrupt is tied to the number of events
89 occurring (that is, after N events, an interrupt is generated).
95 counters, then a simpler method is used: the kernel timer interrupt feeds samples
100 interrupt time to producing user-readable profile information.
124 taken at interrupt time is fed into the generic OProfile driver code.
172 After this final step from interrupt to disk file, the data is now
210 <row><entry><option>count</option></entry><entry>The reset value (how many events before an interrupt)</entry></row>
265 programming in order to make the counter's overflow interrupt appear as
266 an NMI (non-maskable interrupt). This allows sampling (and therefore
321 interrupt handler.
331 CPU saves the register set at the time of interrupt on the stack
333 find out which one generated the interrupt. Also determined is whether
334 the system was inside kernel or user space at the time of the interrupt.
338 interrupt happens after another N events have occurred. Other
419 is keyed off the standard sample interrupt, the number of times a
537 Now we can move onto user-space in our description of how raw interrupt
