Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not build Intel content restriction modules #705

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

DemiMarie
Copy link
Contributor

These kernel modules are only usable if the GPU is attached to dom0. However, dom0 never has the userspace programs needed to use these modules, so the modules are unused.

@DemiMarie DemiMarie force-pushed the no-intel-mei-i915 branch 2 times, most recently from b787329 to 3294d92 Compare January 1, 2023 04:43
INTEL_MEI_HDCP and DRM_AMD_DC_PDCP are for High-bandwidth Digital
Content Protection (HDCP), and INTEL_MEI_PXP is for Protected Xe Path
(PXP).  Since the Intel CSME and AMD Secure Processor must never be
passed through to a VM, these are only usable if there is an Intel or
AMD GPU attached to dom0.  However, dom0 does not include any programs
that can use these modules, so the modules are unused.  Worse, if HDCP
*was* used, it would, it would allow external displays (which are not
trusted) to communicate with the (closed-source and often out-of-date)
Intel CSME or AMD SP firmware, which is even more privileged than dom0.
@marmarek
Copy link
Member

marmarek commented Jan 9, 2023

openQArun

@marmarek
Copy link
Member

marmarek commented Jan 9, 2023

PipelineRetry

@marmarek
Copy link
Member

openQArun

@marmarek
Copy link
Member

PipelineRetry

@marmarek
Copy link
Member

openQArun

@marmarek
Copy link
Member

PipelineRetry

@DemiMarie
Copy link
Contributor Author

Ping

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants