[roll] Roll fuchsia [codec] stress decode of h264 and vp9 + PCMM This is mainly a repro and regression test for bug b/236163568. This runs 3 threads, which randomly select decoding an h264 stream decoding into protected buffers, a vp9 stream decoding into protected buffers, or making some random-size allocations and deallocations using protected_memory_size (on devices that have AMLOGIC_SECURE heap). The combination of these happening concurrently was enough to catch the problem where writing to wid + 0xc register for _any_ HW protection range (4-14) in the BL32 firmware can occasionally glitch the H264 decoder (even if writing back the same value, and for no obvious reason). Previous to this CL, which adds this test to run on relevant HW, we rolled a firmware change that avoids this problem with steady-state writes to wid + 0xc by not writing to wid + 0xc (outside of setup steps prior to any H264 decoder use), and instead dedicates one of the HW protection ranges to zeroing during un-protect (range 4). So with that change, this test is expected to pass reliably (including with the new concurrent PCMM stress, now that the bug is fixed). MULTIPLY: use_h264_and_vp9_decoders_and_pcmm_stress_test: 60 BUG: b/236163568 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/697582 Original-Revision: 0c9cf3b8468451a1f9f364eeeae39f387130756d GitOrigin-RevId: a1632a9152c8bfe5e944ccbedbd9771904cfb5de Change-Id: I2d34fd715346dee92637bc5845cde75ef3a7c8eb
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.