Skip to content
Snippets Groups Projects
Select Git revision
  • android-7.1.2_r28_klist
  • master default protected
  • pie-cts-release
  • pie-vts-release
  • pie-cts-dev
  • oreo-mr1-iot-release
  • sdk-release
  • oreo-m6-s4-release
  • oreo-m4-s12-release
  • pie-release
  • pie-r2-release
  • pie-r2-s1-release
  • oreo-vts-release
  • oreo-cts-release
  • oreo-dev
  • oreo-mr1-dev
  • pie-gsi
  • pie-platform-release
  • pie-dev
  • oreo-cts-dev
  • android-o-mr1-iot-release-1.0.4
  • android-9.0.0_r8
  • android-9.0.0_r7
  • android-9.0.0_r6
  • android-9.0.0_r5
  • android-8.1.0_r46
  • android-8.1.0_r45
  • android-n-iot-release-smart-display-r2
  • android-vts-8.1_r5
  • android-cts-8.1_r8
  • android-cts-8.0_r12
  • android-cts-7.1_r20
  • android-cts-7.0_r24
  • android-o-mr1-iot-release-1.0.3
  • android-cts-9.0_r1
  • android-8.1.0_r43
  • android-8.1.0_r42
  • android-n-iot-release-smart-display
  • android-p-preview-5
  • android-9.0.0_r3
40 results

genfs_contexts

  • Primiano Tucci's avatar
    b4b31f9d
    Allow perfetto traced_probes to access tracefs on user · b4b31f9d
    Primiano Tucci authored
    Allows the traced_probes daemon to access the core ftrace
    functionalities on user builds. Specifically this involves:
    - Whitelisting the per_cpu/ subdirectory to access:
      1) trace_pipe_raw file to allow perfetto to read the raw
         ftrace buffer (rather than the text-based /trace endpoint)
      2) cpuX/stats and cpuX/buffer_size_kb that allow to
         tune the buffer size per-cpu pipe and to get basic
         statistics about the ftrace buffer (#events, overruns)
    - Whitelistiing the full event directories rather than the
      /enable files. This gives also access to the /format files
      for the events that are already enabled on user builds.
      /format files simply describe the memory layout
      of the binary logs. Example: https://ghostbin.com/paste/f8m4k
    
    This still does NOT allow enabling the events labeled as
    "_debug" (mostly events that return activity on inodes).
    We'll deal with that separately as soon as we get a POC
    of inode resolution and a sensible blacklist/whitelist model.
    
    Bug: 70942310
    Change-Id: Ic15cca0a9d7bc0e45aa48097a94eadef44c333f8
    b4b31f9d
    History
    Allow perfetto traced_probes to access tracefs on user
    Primiano Tucci authored
    Allows the traced_probes daemon to access the core ftrace
    functionalities on user builds. Specifically this involves:
    - Whitelisting the per_cpu/ subdirectory to access:
      1) trace_pipe_raw file to allow perfetto to read the raw
         ftrace buffer (rather than the text-based /trace endpoint)
      2) cpuX/stats and cpuX/buffer_size_kb that allow to
         tune the buffer size per-cpu pipe and to get basic
         statistics about the ftrace buffer (#events, overruns)
    - Whitelistiing the full event directories rather than the
      /enable files. This gives also access to the /format files
      for the events that are already enabled on user builds.
      /format files simply describe the memory layout
      of the binary logs. Example: https://ghostbin.com/paste/f8m4k
    
    This still does NOT allow enabling the events labeled as
    "_debug" (mostly events that return activity on inodes).
    We'll deal with that separately as soon as we get a POC
    of inode resolution and a sensible blacklist/whitelist model.
    
    Bug: 70942310
    Change-Id: Ic15cca0a9d7bc0e45aa48097a94eadef44c333f8