![]() | |||||||||||
Messages in this thread |
Arjan van de Ven <arjan@infradead.org> writes: > On Wed, 2006-01-18 at 22:54 +0000, Alan Cox wrote: >> On Mer, 2006-01-18 at 11:38 -0800, Dave Hansen wrote: >> > But, it seems that many drivers like to print out pids as a unique >> > identifier for the task. Should we just let them print those >> > potentially non-unique identifiers, deprecate and kill them, or provide >> > a replacement with something else which is truly unique? >> >> Pick a format for container number + pid and document/stick with it - >> something like container::pid (eg 0::114) or 114[0] whatever so long as >> it is consistent > > having a pid_to_string(<task struct>) or maybe task_to_string() thing > for convenient printing of pids/tasks.. I'm all for that. Means you can > even configure how verbose you want it to be (include ->comm or not, > ->state maybe etc) The only way I can see to sanely do this is to pass it the temporary buffer it writes it's contents into. Something like: printk(KERN_XXX "%s\n", task_to_string(buf, tsk)); ? Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||
| Last update: 2006-01-20 06:14 [from the cache] ©2003-2008 | |||||||||||