[2.3.2.r1.4] msm: kgsl: Three patches from the Feb Android bulletin#2182
Merged
jerpelea merged 3 commits intosonyxperiadev:aosp/LE.UM.2.3.2.r1.4from Feb 17, 2020
Merged
Conversation
Author
|
Kagura boots fine |
ix5
commented
Feb 9, 2020
If a command is using a profiling buffer, make sure that the offset is within the bounds of the specified memory descriptor. Change-Id: Ic0dedbadc77e8eccd957136467bd0c56a1af2dab Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org> Signed-off-by: Deepak Kumar <dkumar@codeaurora.org>
To prepare to allow global buffers to allocate a semi-random GPU address move from a sequential allocator to a bitmap based one. Adapted to the SODP 4.9 kernel to use macros with `(mmu)` arguments: `GLOBAL_MAP_PAGES(mmu)` and `KGSL_IOMMU_GLOBAL_MEM_SIZE(mmu)` and `KGSL_IOMMU_GLOBAL_MEM_SIZE_NG >> PAGE_SHIFT` instead of `GLOBAL_MAP_PAGES` in `DECLARE_BITMAP` Change-Id: Ic0dedbadba36c4c7b7839528103997724eac7d6d Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org> Signed-off-by: Deepak Kumar <dkumar@codeaurora.org> Signed-off-by: ix5 <ix5@users.noreply.github.com>
Execute user profiling in an indirect buffer. This ensures that addresses and values specified directly from the user don't end up in the ringbuffer. FIXME: Felix: Left a comment in adreno_ringbuffer.c about dword length for legacy, needs to be adressed! Change-Id: Ic0dedbadedcaab29ce5738a39c1ff6269261bae4 Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org> Signed-off-by: Harshitha Sai Neelati <hsaine@codeaurora.org> Signed-off-by: ix5 <ix5@users.noreply.github.com>
3de124a to
ee6e89f
Compare
|
Compiles, boots and runs fine on yoshino/lilac on top of latest 4.9.213 |
|
@ix5 [WIP] can be removed? Or still something open? |
Author
|
@stefanhh0 I really wouldn't like to break other devices, but it seems this is ok to merge now. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://source.android.com/security/bulletin/2020-02-01#qualcomm-components
4.14 seems unaffected, we're already patched up (thanks @nathanchance!)
State, as far as I could determine: https://sx.ix5.org/info/post/sodp-2020-02-05-security-state/
Also part of the Feb patches: #2183-> Not necessaryThe
dwordchange inadreno_ringbuffer.cseems bad for legacy to me?Build-tested for kagura.