Debian Codegraph @

media_softlet/linux/common/os/xe/include/README.md

raw
1 This directory contains a copy of the installed kernel headers
2 required by the iHD driver to communicate with the kernel.
3 Whenever driver needs new definitions for new kernel
4 APIs, these files should be updated.
5
6 These files in master should only be updated once the changes have landed
7 in the drm-xe-next tree (see https://gitlab.freedesktop.org/drm/xe/kernel.git).
8
9 You can copy files installed after running this from the kernel
10 repository, at version the driver require:
11
12 $ make headers_install INSTALL_HDR_PATH=/path/to/install
13
14 The last update was done at the following kernel commit:
15
16 commit 41a97c4a12947c2786a1680d6839bb72d1c57cec (HEAD -> drm-xe-next, origin/drm-xe-next)
17
18 drm/xe/pxp/uapi: Add API to mark a BO as using PXP
19
20 The driver needs to know if a BO is encrypted with PXP to enable the
21 display decryption at flip time.
22 Furthermore, we want to keep track of the status of the encryption and
23 reject any operation that involves a BO that is encrypted using an old
24 key. There are two points in time where such checks can kick in:
25
26 1 - at VM bind time, all operations except for unmapping will be
27 rejected if the key used to encrypt the BO is no longer valid. This
28 check is opt-in via a new VM_BIND flag, to avoid a scenario where a
29 malicious app purposely shares an invalid BO with a non-PXP aware
30 app (such as a compositor). If the VM_BIND was failed, the
31 compositor would be unable to display anything at all. Allowing the
32 bind to go through means that output still works, it just displays
33 garbage data within the bounds of the illegal BO.
34
35 2 - at job submission time, if the queue is marked as using PXP, all
36 objects bound to the VM will be checked and the submission will be
37 rejected if any of them was encrypted with a key that is no longer
38 valid.
39
40 Note that there is no risk of leaking the encrypted data if a user does
41 not opt-in to those checks; the only consequence is that the user will
42 not realize that the encryption key is changed and that the data is no
43 longer valid.
44
45 v2: Better commnnts and descriptions (John), rebase
46
47 v3: Properly return the result of key_assign up the stack, do not use
48 xe_bo in display headers (Jani)
49
50 v4: improve key_instance variable documentation (John)
51
52 Signed-off-by: default avatarDaniele Ceraolo Spurio <[email protected]>
53 Cc: Matthew Brost <[email protected]>
54 Cc: Thomas Hellström <[email protected]>
55 Cc: John Harrison <[email protected]>
56 Cc: Jani Nikula <[email protected]>
57 Reviewed-by: default avatarJohn Harrison <[email protected]>
58 Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
59
60 commit f2881dfdaaa9ec873dbd383ef5512fc31e576cbb (HEAD -> drm-xe-next, origin/drm-xe-next)
61
62 drm/xe/oa/uapi: Make bit masks unsigned
63
64 The infrastructure to query GuC firmware version is already in place. It
65 is extended with a new micro-controller type to query the HuC firmware
66 version. It can be used from user space to know if HuC is running.
67
68 Cc: John Harrison <[email protected]>
69 Cc: Francois Dugast <[email protected]>
70 Cc: Lucas De Marchi <[email protected]>
71 Signed-off-by: Francois Dugast <[email protected]>
72 Signed-off-by: José Roberto de Souza <[email protected]>
73 Reviewed-by: Rodrigo Vivi <[email protected]>
74 Reviewed-by: John Harrison <[email protected]>
75 Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]