Hi Eduard-Gabriel, On Fri, Jul 18, 2008 at 11:48:03AM +0300, Pekka J Enberg wrote:On Fri, Jul 18, 2008 at 1:13 PM, Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro> wrote: Yes, I do think it's unreasonable. I, for one, am hoping distributions will pick up the kmemtrace userspace at some point after which I don't need to ever compile it myself. On Fri, Jul 18, 2008 at 1:13 PM, Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro> wrote: Like I've said before, it's debugging/tracing infrastructure so the rules are bit more relaxed. That said, what we should do is (1) make the ABI as future-proof as we can, (2) explicitly mark it as unstable by documenting it in Documentation/ABI/testing and (3) at some point in time move it in Documentation/ABI/stable and hopefully never break it again. But sure, we probably don't need to keep any "bloat" around like we do with the syscall interface, for example. And hopefully, the ABI is good enough to allow adding *new* tracing events while retaining the old ones nicely in a backwards compatible way. On Fri, Jul 18, 2008 at 11:48:03AM +0300, Pekka J Enberg wrote: On Fri, Jul 18, 2008 at 1:13 PM, Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro> wrote: Sure, makes sense. Pekka --
| Andreas Gruenbacher | Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching |
| Alan Cox | Re: [patch 7/8] fdmap v2 - implement sys_socket2 |
| Jens Axboe | Re: regression: CD burning (k3b) went broke |
| Paul E. McKenney | Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures |
git: | |
| KOSAKI Motohiro | [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
| David Miller | [GIT]: Networking |
| Alexey Dobriyan | [PATCH 09/33] netns ct: per-netns /proc/net/nf_conntrack, /proc/net/stat/nf_conntr... |
| Gerrit Renker | [PATCH 18/37] dccp: Support for Mandatory options |
