1 /*******************************************************************************
2 * Copyright (c) 2014, 2015 Ericsson
4 * All rights reserved. This program and the accompanying materials are
5 * made available under the terms of the Eclipse Public License v1.0 which
6 * accompanies this distribution, and is available at
7 * http://www.eclipse.org/legal/epl-v10.html
10 * Alexandre Montplaisir - Initial API and implementation
11 ******************************************************************************/
13 package org
.eclipse
.tracecompass
.analysis
.os
.linux
.core
.trace
;
15 import java
.util
.Collection
;
17 import org
.eclipse
.jdt
.annotation
.Nullable
;
20 * Interface to define "concepts" present in the Linux kernel (represented by
21 * its tracepoints), that can then be exposed by different tracers under
24 * @author Alexandre Montplaisir
25 * @author Matthew Khouzam - Javadoc
27 public interface IKernelAnalysisEventLayout
{
29 // ------------------------------------------------------------------------
31 // ------------------------------------------------------------------------
34 * The standard layout, very useful for test vectors that are not kernel
37 IKernelAnalysisEventLayout DEFAULT_LAYOUT
= DefaultEventLayout
.INSTANCE
;
40 * Whenever a process appears for the first time in a trace, we assume it
41 * starts inside this system call. (The syscall prefix is defined by the
42 * implementer of this interface.)
44 * TODO Change to a default method with Java 8?
46 String INITIAL_SYSCALL_NAME
= "clone"; //$NON-NLS-1$
48 // ------------------------------------------------------------------------
50 // ------------------------------------------------------------------------
53 * The system has just entered an interrupt handler or interrupt service
54 * routine. On some systems, this is known as the first level interrupt
57 * @return the event name
59 String
eventIrqHandlerEntry();
62 * The system will soon return from an interrupt handler or interrupt
65 * @return the event name
67 String
eventIrqHandlerExit();
70 * Whenever a system call is about to return to userspace, or a hardware
71 * interrupt handler exits, any 'software interrupts' which are marked
72 * pending (usually by hardware interrupts) are run. Much of the real
73 * interrupt handling work is done here. The soft IRQ is also known as a
74 * deferred IRQ in windows. An event identifying as this needs to occur as
75 * the system is beginning to process the interrupt.
77 * @return the event name
79 String
eventSoftIrqEntry();
82 * Whenever a system call is about to return to userspace, or a hardware
83 * interrupt handler exits, any 'software interrupts' which are marked
84 * pending (usually by hardware interrupts) are run Much of the real
85 * interrupt handling work is done here. The soft IRQ is also known as a
86 * deferred IRQ in windows. An event identifying as this needs to occur as
87 * the system is returning from the interrupt.
89 * @return the event name
91 String
eventSoftIrqExit();
94 * Whenever a system call is about to return to userspace, or a hardware
95 * interrupt handler exits, any 'software interrupts' which are marked
96 * pending (usually by hardware interrupts) are run Much of the real
97 * interrupt handling work is done here. The soft IRQ is also known as a
98 * deferred IRQ in windows. An event identifying as this needs to occur as
99 * the system is signaling the need to enter the interrupt.
101 * @return the event name
103 String
eventSoftIrqRaise();
106 * The scheduler will call a scheduler switch event when it is removing a
107 * task from a cpu and placing another one in its place. Which task and when
108 * depend on the scheduling strategy and the task priorities. This is a
111 * @return the event name
113 String
eventSchedSwitch();
116 * sched_PI_setprio is a tracepoint called often when the schedulder
117 * priorities for a given task changes.
119 * @return the event name
122 String
eventSchedPiSetprio();
125 * Scheduler is waking up a task. this happens before it is executed, and
126 * the data is loaded in memory if needed.
128 * @return the event names, as there are often several different ways to
131 Collection
<String
> eventsSchedWakeup();
134 * Scheduler just forked a process, that means it has duplicated the program
135 * and assigned it a different process ID. This event is often followed by
136 * an {@link #eventSchedProcessExec()}. In windows, this is part of the
139 * @return the event name
141 String
eventSchedProcessFork();
144 * The process has finished running and the scheduler takes its TID back.
146 * @return the event name
148 String
eventSchedProcessExit();
151 * The process free tracepoint is called when a process has finished running
152 * and the scheduler retrieves it's process ID.
154 * @return the event name
156 String
eventSchedProcessFree();
159 * Optional event used by some tracers to deliver an initial state.
161 * @return the event name
163 @Nullable String
eventStatedumpProcessState();
166 * System call entry prefix, something like "sys_open" or just "sys".
168 * @return the event name
170 String
eventSyscallEntryPrefix();
173 * System call compatibility layer entry prefix, something like
176 * @return the event name
178 String
eventCompatSyscallEntryPrefix();
181 * System call exit prefix, something like "sys_exit".
183 * @return the event name
185 String
eventSyscallExitPrefix();
188 * The scheduler replaced the current process image with a new one. The
189 * process should also be renamed at this point. In windows, this is part of
190 * the spawn process as well as fork.
192 * @return the event name
196 String
eventSchedProcessExec();
199 * The scheduler calls wakeup on a sleeping process. The process will
200 * probably soon be scheduled in.
202 * @return the event name
206 String
eventSchedProcessWakeup();
209 * The scheduler calls wakeup on a sleeping process. The process will
210 * probably soon be scheduled in. The new wakeup knows who triggered the
213 * @return the event name
217 String
eventSchedProcessWakeupNew();
220 * Entering the high resolution timer expired handler.
222 * In Linux, High resolution timers are used in the following:
226 * <li>posix timers</li>
229 * @return the event name
233 String
eventHRTimerExpireEntry();
236 * Exiting the high resolution timer expired handler.
238 * In Linux, High resolution timers are used in the following:
242 * <li>posix timers</li>
245 * @return the event name
249 String
eventHRTimerExpireExit();
251 // ------------------------------------------------------------------------
253 // ------------------------------------------------------------------------
256 * The field with the IRQ number. This is used in irq_handlers (entry and
257 * exit). For soft IRQs see {@link #fieldVec}.
259 * @return the name of the field with the IRQ number
264 * The field with the vector. This is the soft IRQ vector field used in soft
265 * IRQ raise, entry and exit. For hardware IRQs see {@link #fieldIrq}.
267 * @return the name of the field with the soft IRQ vector name
272 * The field with the thread ID. This is often used in scheduler calls to
273 * know which thread is being affected. (normally not in switch, but in
274 * priority and wakeup calls).
276 * @return the name of the field with the thread ID
281 * The field with the previous thread id. This is used in switching
282 * operations of a scheduler, when a thread is scheduled out for another,
283 * this field shows the thread id being scheduled out.
285 * @return The name of the field with the ID of the previous thread
287 String
fieldPrevTid();
290 * The field with the state of the previous thread. This is used in
291 * switching operations of a scheduler, when a thread is scheduled out for
292 * another, this field shows the state of the thread being scheduled out.
294 * @return the name of the field of the previous thread's state
296 String
fieldPrevState();
299 * The field with the next command to be run. This is used in switching
300 * operations of a scheduler, when a thread is scheduled out for another,
301 * this field shows the command being scheduled in. A command's value is
302 * often a String like "ls" or "hl3.exe".
304 * @return the name of the field with the next command to be run
306 String
fieldNextComm();
309 * The field with the next thread ID. This is used in switching operations
310 * of a scheduler, when a thread is scheduled out for another, this field
311 * shows the thread being scheduled in.
313 * @return the name of the field with the next thread ID
315 String
fieldNextTid();
318 * The field with the child command. This field is used in clone and spawn
319 * activities, to know which executable the clone is running.
321 * @return the name of the field with the child command
323 String
fieldChildComm();
326 * The field with the parent thread ID. This field is used in clone and
327 * spawn activities, to know which thread triggered the clone.
329 * @return the name of the field with the parent thread ID
331 String
fieldParentTid();
334 * The field with the child thread ID. This field is used in clone and spawn
335 * activities, to know which thread is the clone.
337 * @return the name of the field with the child thread ID
339 String
fieldChildTid();
342 * The field with the command. This is used in scheduling tracepoints that
343 * are not switches, and show the current process name. It is often a string
344 * like "zsh" or "cmd.exe".
346 * @return the name of the command field
352 * The field with the name. The name field is used in several disjoint
357 * <li>writeback_* - the name of the io device, often "(unknown)"</li>
358 * <li>module_* - the name of the module such as "binfmt_misc"</li>
359 * <li>irq_handler_entry - the field describes the name of the handler such
363 * @return the name of the field with a name
369 * The field with the status. Often functions like a return value before we
374 * <li>ext4* - status</li>
375 * <li>asoc_snd_soc_cache_sync</li>
377 * <li>state dumps</li>
380 * @return The name of the field with a status
383 String
fieldStatus();
386 * The field with the last command to be run. This is often a string
387 * representing the command of the thread being scheduled out from a
388 * scheduler switch operation.
390 * @return the name of the field with the last command to be run
393 String
fieldPrevComm();
396 * The field with the file name field. This is a string used mostly with
397 * file operations. These operations are often wrapped in system calls and
401 * <li>change mode</li>
402 * <li>change directory</li>
405 * It can also be used in exec commands to see what the command name should
408 * Please note that file read and write often do not use the file name, they
409 * just use the file handle.
411 * @return the name of the field with the file name
414 String
fieldFilename();
417 * The field with the priority. The priority of a given process is used by
418 * most scheduler events. The major exception is the switching operation as
419 * it has two processes so it has a previous and next priority.
421 * @return the name of the field with the thread or process' priority
427 * The field with the new priority. This is used in the scheduler's
428 * pi_setprio event event to show the new priority of the thread or process.
430 * @return the name of the field with the thread or process' new priority
433 String
fieldNewPrio();
436 * The field with the next priority. This is used in the scheduler's switch
437 * event to show the priority of the next thread or process.
439 * @return the name of the field with the thread or process' next priority
442 String
fieldNextPrio();