linux-kernel - Re: [patch 00/37] Linux Kernel Markers instrumentation for sched-devel.git

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 29 Apr 2008 04:01:36 +0900
From:	"KOSAKI Motohiro" <kosaki.motohiro@...fujitsu.com>
To:	"Andrew Morton" <akpm@...ux-foundation.org>
Cc:	"Christoph Hellwig" <hch@...radead.org>,
	"Peter Zijlstra" <a.p.zijlstra@...llo.nl>,
	"Mathieu Desnoyers" <mathieu.desnoyers@...ymtl.ca>,
	"Ingo Molnar" <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: [patch 00/37] Linux Kernel Markers instrumentation for sched-devel.git

>  > > It hides the cosmetically-ugly bits, but not the deeply ugly: each of these
>  > > trace points is an extension to the kernel->userspace API, with all that
>  > > this implies.
>  >
>  > Not at all.  It's only accessibe to kernel code, so it per defintion
>  > can't be a userspace API.
>
>  eh?  It adds human-readable printk strings.

Yes, human-readable.
but I think trace point shouldn't be treat as kernel API.
because it cause showed implementation detail become impossible.

so, it decrease valuable of trace point.

example, nobody hope crash command hidden implementation detail.
I hope trace point is treated as so too.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/