Revision ed900c054b541254f0ce5cedaf75206e29bd614e authored by Anton Blanchard on 16 July 2009, 13:44:29 UTC, committed by Ingo Molnar on 18 July 2009, 09:21:31 UTC
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 <anton@samba.org> Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> LKML-Reference: <20090716104817.589309391@samba.org> Signed-off-by: Ingo Molnar <mingo@elte.hu>
1 parent 11b5f81
File | Mode | Size |
---|---|---|
.gitignore | -rw-r--r-- | 102 bytes |
Kconfig | -rw-r--r-- | 4.4 KB |
Makefile | -rw-r--r-- | 2.1 KB |
gen_init_cpio.c | -rw-r--r-- | 12.2 KB |
initramfs_data.S | -rw-r--r-- | 1021 bytes |
initramfs_data.bz2.S | -rw-r--r-- | 1.0 KB |
initramfs_data.gz.S | -rw-r--r-- | 1023 bytes |
initramfs_data.lzma.S | -rw-r--r-- | 1.0 KB |
Computing file changes ...