Re: [PATCH] vfs: Add a trace point in the mark_inode_dirty function

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2010-11-29 at 09:41 -0500, Mathieu Desnoyers wrote:

> One question that strikes me is: would you declare this outside of the
> TRACE_EVENT() or inside it ? How would you match the TRACE_EVENT() and the
> TRACE_EVENT_CONDITION() if they are separate, by name ?
> 

TRACE_EVENT_CONDITION() would just add the condition field and
TRACE_EVENT() will just have a null condition:

#define TRACE_EVENT(name, proto, args, tstruct, assign, print) \
	TRACE_EVENT_CONDITION(name, proto, args, , tsturct, \
		assign, print)

where that ", ," is the condition expression. (I also left out the
PARAMS() that would be required here too.)

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux