Project

General

Profile

Actions

Bug #907

closed

lttng list does not report the existence of kernel domain filters

Added by Philippe Proulx over 8 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
08/24/2015
Due date:
% Done:

0%

Estimated time:

Description

If a kernel domain event with a filter is enabled, the list command does not show that it has an attached filter like an UST domain event does.

Steps:

lttng create a
lttng enable-event -k sched_switch --filter 'next_tid > 10'
lttng list

Result:

Tracing session a: [inactive]
    Trace path: /home/eepp/lttng-traces/a-20150824-185417

=== Domain: Kernel ===

Channels:
-------------
- channel0: [enabled]

    Attributes:
      overwrite mode: 0
      subbufers size: 262144
      number of subbufers: 4
      switch timer interval: 0
      read timer interval: 200000
      trace file count: 0
      trace file size (bytes): 0
      output: splice()

    Events:
      sched_switch (loglevel: TRACE_EMERG (0)) (type: tracepoint) [enabled]

Compare to a UST event:

Tracing session b: [inactive]
    Trace path: /home/eepp/lttng-traces/b-20150824-185742

=== Domain: UST global ===

Buffer type: per UID

Channels:
-------------
- channel0: [enabled]

    Attributes:
      overwrite mode: 0
      subbufers size: 131072
      number of subbufers: 4
      switch timer interval: 0
      read timer interval: 0
      trace file count: 0
      trace file size (bytes): 0
      output: mmap()

    Events:
      b (type: tracepoint) [enabled] [with filter]

MI also reports false:

<?xml version="1.0" encoding="UTF-8"?>
<command>
  <name>list</name>
  <output>
    <sessions>
      <session>
        <name>a</name>
        <path>/home/eepp/lttng-traces/a-20150824-185417</path>
        <enabled>false</enabled>
        <snapshot_mode>0</snapshot_mode>
        <live_timer_interval>0</live_timer_interval>
        <domains>
          <domain>
            <type>KERNEL</type>
            <buffer_type>GLOBAL</buffer_type>
            <trackers/>
            <channels>
              <channel>
                <name>channel0</name>
                <enabled>true</enabled>
                <attributes>
                  <overwrite_mode>DISCARD</overwrite_mode>
                  <subbuffer_size>262144</subbuffer_size>
                  <subbuffer_count>4</subbuffer_count>
                  <switch_timer_interval>0</switch_timer_interval>
                  <read_timer_interval>200000</read_timer_interval>
                  <output_type>SPLICE</output_type>
                  <tracefile_size>0</tracefile_size>
                  <tracefile_count>0</tracefile_count>
                  <live_timer_interval>0</live_timer_interval>
                </attributes>
                <events>
                  <event>
                    <name>sched_switch</name>
                    <type>TRACEPOINT</type>
                    <enabled>true</enabled>
                    <filter>false</filter>
                    <loglevel>TRACE_EMERG</loglevel>
                    <loglevel_type>ALL</loglevel_type>
                    <exclusion>false</exclusion>
                  </event>
                </events>
              </channel>
            </channels>
          </domain>
          <domain>
            <type>UST</type>
            <buffer_type>PER_UID</buffer_type>
            <trackers/>
            <channels/>
          </domain>
        </domains>
      </session>
    </sessions>
  </output>
</command>
Actions #1

Updated by Jérémie Galarneau over 8 years ago

Fixed by

commit 00f992f21e448b4347150e6204ed0afbc635a1af
Author: Jérémie Galarneau <jeremie.galarneau@efficios.com>
Date:   Thu Aug 27 17:26:58 2015 -0400

    Fix: Propagate filter status of kernel events to client

    Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>

Actions #2

Updated by Jérémie Galarneau over 8 years ago

  • Status changed from New to Resolved
Actions

Also available in: Atom PDF