Linux Kernel Markers for 2.6.21-mm2
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest10 patches 50 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/10 | Linux Kernel Markers - Add kconfig menus for the marker codearch/ arch/ arch/ +24 more | +149 | 1 reply | |
| 2/10 | Linux Kernel Markers, architecture independent code.include/ include/ include/ +1 more | +414 | 5 replies | |
| 3/10 | Allow userspace applications to use marker.h to parse the markers section in the kernel binary.include/ include/ | +5 | 8 replies | |
| 4/10 | Linux Kernel Markers - PowerPC optimized versionarch/ arch/ include/ | +111 | 1 reply | |
| 5/10 | Linux Kernel Markers - i386 optimized versionarch/ arch/ include/ | +184 | 11 replies | |
| 6/10 | Linux Kernel Markers - Non optimized architecturesinclude/ include/ include/ +20 more | +323 | 7 replies | |
| 7/10 | Linux Kernel Markers - DocumentationDocumentation/ | +266 | 14 replies | |
| 8/10 | Defines the linker macro EXTRA_RWDATA for the marker data section.include/ | +13 | 0 replies | |
| 9/10 | Linux Kernel Markers - Use EXTRA_RWDATA in architecturesarch/ arch/ arch/ +26 more | +33 | 0 replies | |
| 10/10 | Port of blktrace to the Linux Kernel Markers.block/ block/ block/ +7 more | +323 | 2 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [patch 00/10] Linux Kernel Markers for 2.6.21-mm2
Hi Andrew,
He is an updated, folded, version of the Linux Kernel Markers. It replaces the version found in 2.6.21-mm2 at the exact same spot in the series file.
Main changes :
- It renames the MARK() trace_mark(), as suggested by Christoph Hellwig.
- It now defines the structures contained out of the marker section outside of the #ifdef __KERNEL__ so the SystemTAP tool can use the header to extract the markers from the kernel binary.
- The i386 optimization has been tweaked a bit : the call is now in the else branch. It has something to do with the i386 "fast path" being the taken branch of a jump, to make loops faster. It seems that the if/else statements are also affected : the if () will be faster than the else. Therefore, I put the call in the else, to make sure the fastest path is when the marker is disabled.
- I added the blktrace port to the markers infrastructure. It makes one in-tree markers user.
Please remove :
linux-kernel-markers-kconfig-menus.patch linux-kernel-markers-architecture-independant-code.patch linux-kernel-markers-powerpc-optimization.patch linux-kernel-markers-i386-optimization.patch markers-add-instrumentation-markers-menus-to-avr32.patch linux-kernel-markers-non-optimized-architectures.patch markers-alpha-and-avr32-supportadd-alpha-markerh-add-arm26-markerh.patch linux-kernel-markers-documentation.patch
#
markers-define-the-linker-macro-extra_rwdata.patch markers-use-extra_rwdata-in-architectures.patch
And add, instead :
linux-kernel-markers-kconfig-menus.patch linux-kernel-markers-architecture-independant-code.patch linux-kernel-markers-header-visible-from-userspace.h linux-kernel-markers-powerpc-optimization.patch linux-kernel-markers-i386-optimization.patch linux-kernel-markers-non-optimized-architectures.patch linux-kernel-markers-documentation.patch
# linux-kernel-markers-define-the-linker-macro-extra_rwdata.patch linux-kernel-markers-use-extra_rwdata-in-architectures.patch #
linux-kernel-markers-port-blktrace-to-markers.patch
Thanks,
Mathieu
Signature · 3 lines
Mathieu Desnoyers Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68