aboutsummaryrefslogtreecommitdiff
path: root/drivers/firmware/psci/psci.c
diff options
context:
space:
mode:
authorJames Morse <[email protected]>2020-05-19 19:21:08 +0100
committerWill Deacon <[email protected]>2020-05-20 09:36:01 +0100
commit472de63b0b8383565e103f809f5df37d1c4390ab (patch)
treed2bc2eb495a0b2e8a8bde740987a2a7104c0d9d4 /drivers/firmware/psci/psci.c
parent82b2077afccd2a46ce15a43a50f2bfbf1b295de5 (diff)
firmware: arm_sdei: Document the motivation behind these set_fs() calls
The SDEI handler save/restores the addr_limit using set_fs(). It isn't very clear why. The reason is to mirror the arch code's entry assembly. The arch code does this because perf may access user-space, and inheriting the addr_limit may be a problem. Add a comment explaining why this is here. Suggested-by: Christoph Hellwig <[email protected]> Signed-off-by: James Morse <[email protected]> Link: https://bugs.chromium.org/p/project-zero/issues/detail?id=822 Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Will Deacon <[email protected]>
Diffstat (limited to 'drivers/firmware/psci/psci.c')
0 files changed, 0 insertions, 0 deletions