-
Notifications
You must be signed in to change notification settings - Fork 349
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[CP] Create Protected Queue for Protected Context
Protected queue is required for protected execution.
- Loading branch information
1 parent
223d039
commit 050948b
Showing
3 changed files
with
222 additions
and
6 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,6 +13,50 @@ $ make headers_install INSTALL_HDR_PATH=/path/to/install | |
|
||
The last update was done at the following kernel commit: | ||
|
||
commit 41a97c4a12947c2786a1680d6839bb72d1c57cec (HEAD -> drm-xe-next, origin/drm-xe-next) | ||
|
||
drm/xe/pxp/uapi: Add API to mark a BO as using PXP | ||
|
||
The driver needs to know if a BO is encrypted with PXP to enable the | ||
display decryption at flip time. | ||
Furthermore, we want to keep track of the status of the encryption and | ||
reject any operation that involves a BO that is encrypted using an old | ||
key. There are two points in time where such checks can kick in: | ||
|
||
1 - at VM bind time, all operations except for unmapping will be | ||
rejected if the key used to encrypt the BO is no longer valid. This | ||
check is opt-in via a new VM_BIND flag, to avoid a scenario where a | ||
malicious app purposely shares an invalid BO with a non-PXP aware | ||
app (such as a compositor). If the VM_BIND was failed, the | ||
compositor would be unable to display anything at all. Allowing the | ||
bind to go through means that output still works, it just displays | ||
garbage data within the bounds of the illegal BO. | ||
|
||
2 - at job submission time, if the queue is marked as using PXP, all | ||
objects bound to the VM will be checked and the submission will be | ||
rejected if any of them was encrypted with a key that is no longer | ||
valid. | ||
|
||
Note that there is no risk of leaking the encrypted data if a user does | ||
not opt-in to those checks; the only consequence is that the user will | ||
not realize that the encryption key is changed and that the data is no | ||
longer valid. | ||
|
||
v2: Better commnnts and descriptions (John), rebase | ||
|
||
v3: Properly return the result of key_assign up the stack, do not use | ||
xe_bo in display headers (Jani) | ||
|
||
v4: improve key_instance variable documentation (John) | ||
|
||
Signed-off-by: default avatarDaniele Ceraolo Spurio <[email protected]> | ||
Cc: Matthew Brost <[email protected]> | ||
Cc: Thomas Hellström <[email protected]> | ||
Cc: John Harrison <[email protected]> | ||
Cc: Jani Nikula <[email protected]> | ||
Reviewed-by: default avatarJohn Harrison <[email protected]> | ||
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected] | ||
|
||
commit f2881dfdaaa9ec873dbd383ef5512fc31e576cbb (HEAD -> drm-xe-next, origin/drm-xe-next) | ||
|
||
drm/xe/oa/uapi: Make bit masks unsigned | ||
|
This file contains 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
This file contains 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