* Steven Rostedt | 2016-03-07 09:03:47 [-0500]:
>On Sun, 6 Mar 2016 19:32:26 -0800
>"Shi, Yang" wrote:
>
>> Hi Steven,
>>
>> Any comment on this one? I'm supposed it will be taken by your tracing tree?
>>
>
>Usually trace events go in through their subsystem, but since this one
>only touches th
On Sun, 6 Mar 2016 19:32:26 -0800
"Shi, Yang" wrote:
> Hi Steven,
>
> Any comment on this one? I'm supposed it will be taken by your tracing tree?
>
Usually trace events go in through their subsystem, but since this one
only touches the include/trace/events/ directory, I could pull it in
too.
Hi Steven,
Any comment on this one? I'm supposed it will be taken by your tracing tree?
Thanks,
Yang
On 3/4/2016 4:52 AM, Tejun Heo wrote:
On Thu, Mar 03, 2016 at 01:08:57AM -0800, Yang Shi wrote:
commit 5634cc2aa9aebc77bc862992e7805469dcf83dac ("writeback: update writeback
tracepoints to re
On Thu, Mar 03, 2016 at 01:08:57AM -0800, Yang Shi wrote:
> commit 5634cc2aa9aebc77bc862992e7805469dcf83dac ("writeback: update writeback
> tracepoints to report cgroup") made writeback tracepoints print out cgroup
> path when CGROUP_WRITEBACK is enabled, but it may trigger the below bug on -rt
> k
commit 5634cc2aa9aebc77bc862992e7805469dcf83dac ("writeback: update writeback
tracepoints to report cgroup") made writeback tracepoints print out cgroup
path when CGROUP_WRITEBACK is enabled, but it may trigger the below bug on -rt
kernel since kernfs_path and kernfs_path_len are called by tracepoi
5 matches
Mail list logo