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

AndroidSystemSEPolicy

  • Clone with SSH
  • Clone with HTTPS
  • Florian Fischer's avatar
    Florian Fischer authored
    Futures can have a registered Callback of type
    std::function<void(const uint32_t&)> which gets called in a new
    Fiber with the result of the IO Request.
    Note the first completion will cause the execution of a callback and
    partial completion support must be implemented manually in the callback.
    
    Callbacks are stored in a heap allocated std::function on registration
    and are freed by the new Fiber after the callback returned;
    
    The Future with a registered Callback is not referenced in any way in
    the IO subsystem and therefore can be dropped after being submitted.
    This also means that a Future with a registered callback will not be
    signaled by the IO subsystem on completion.
    If signaling is desired one must implement it manually in the registered
    callback.
    827b79ae
    History
    Name Last commit Last update