On 6/13/16 11:48 AM, David Sterba wrote:
> On Thu, Jun 09, 2016 at 07:48:01PM -0400, je...@suse.com wrote:
>> +#define TP_printk_btrfs(fmt, args...) \
>> +TP_printk("%pU: " fmt, __entry->fsid, args)
>
> So it's identified by the UUID. As there's no previous format of the
> filesystem
On Thu, Jun 09, 2016 at 07:48:01PM -0400, je...@suse.com wrote:
> +#define TP_printk_btrfs(fmt, args...) \
> + TP_printk("%pU: " fmt, __entry->fsid, args)
So it's identified by the UUID. As there's no previous format of the
filesystem identifier (unlike the syslog messages), I'm ok with using
On Thu, Jun 09, 2016 at 07:48:01PM -0400, je...@suse.com wrote:
> From: Jeff Mahoney
>
> When using trace events to debug a problem, it's impossible to determine
> which file system generated a particular event. This patch adds a
> macro to prefix standard information to the
On Thu, Jun 09, 2016 at 07:48:01PM -0400, je...@suse.com wrote:
> From: Jeff Mahoney
>
> When using trace events to debug a problem, it's impossible to determine
> which file system generated a particular event. This patch adds a
> macro to prefix standard information to the
From: Jeff Mahoney
When using trace events to debug a problem, it's impossible to determine
which file system generated a particular event. This patch adds a
macro to prefix standard information to the head of a trace event.
The extent_state alloc/free events are all that's