diff options
| author | Anton Blanchard <[email protected]> | 2009-07-16 15:44:29 +0200 |
|---|---|---|
| committer | Ingo Molnar <[email protected]> | 2009-07-18 11:21:31 +0200 |
| commit | ed900c054b541254f0ce5cedaf75206e29bd614e (patch) | |
| tree | c164aaefa1185744d4372d8ff5b11a86a8e1405a /drivers/mtd/lpddr/lpddr_cmds.c | |
| parent | 11b5f81e1b0ea0bc84fe32f0a27054e052b2bf84 (diff) | |
perf_counter: Log vfork as a fork event
Right now we don't output vfork events. Even though we should
always see an exec after a vfork, we may get perfcounter
samples between the vfork and exec. These samples can lead to
some confusion when parsing perfcounter data.
To keep things consistent we should always log a fork event. It
will result in a little more log data, but is less confusing to
trace parsing tools.
Signed-off-by: Anton Blanchard <[email protected]>
Signed-off-by: Peter Zijlstra <[email protected]>
LKML-Reference: <[email protected]>
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'drivers/mtd/lpddr/lpddr_cmds.c')
0 files changed, 0 insertions, 0 deletions