...fixing some Cc email addresses I somehow mangled. On 2023-05-10 12:40:07, Souza, Jose wrote: > On Mon, 2023-05-08 at 17:49 +0000, Teres Alexis, Alan Previn wrote: > > On Fri, 2023-05-05 at 00:39 -0700, Justen, Jordan L wrote: > > > On 2023-05-04 22:30:07, Teres Alexis, Alan Previn wrote: > > > > On Thu, 2023-04-27 at 16:48 -0700, Teres Alexis, Alan Previn wrote: > > > > > Because of the additional firmware, component-driver and > > > > > initialization depedencies required on MTL platform before a > > > > > PXP context can be created, UMD calling for PXP creation as a > > > > > way to get-caps can take a long time. An actual real world > > > > > customer stack has seen this happen in the 4-to-8 second range > > > > > after the kernel starts (which sees MESA's init appear in the > > > > > middle of this range as the compositor comes up). To avoid > > > > > unncessary delays experienced by the UMD for get-caps purposes, > > > > > add a GET_PARAM for I915_PARAM_PXP_SUPPORT. > > > > > > > > > alan:snip. > > > > Progress update on the UMD side - I'm working on patch for PR here: > > > > https://gitlab.freedesktop.org/alan_previn_intel/mesa-alan-previn-features/-/commit/fb9d4fbfbef7dfd3f41df335cd31549fd39ddb57 > > > > but taking time to verify certain code paths > > > > > > Just to confirm, if I915_PARAM_PXP_STATUS returns 2 ("will be ready > > > soon"), then it is basically certain that in a production environment, > > > then it will eventually return 1 meaning it's ready, right? > > alan: yes - but not 100%. non-platform-state-machine could still > > cause unexpected failures for example, [1] if hw was fused in a way > > that doesnt permit PXP or [2] enabling certain BIOS debug knobs > > doesnt allow PXP. However at the moment, there is no way for us > > to know for sure without actually creating a protected context. > > Of course having hw-fusing + bios-config that supports PXP have > > always 100% succeeded for me. > > In my opinion it is problematic mark that we support protected > context but then it fails to create protected context. This is why I asked if it was it was "basically certain that in a production environment, then it will eventually return 1 meaning it's ready". Alan's response was a little ambiguous on this point. But, considering the number of applications that will need this feature is low, combined with an extremely low chance that the kernel will end up going from 2 (will be ready soon) to -ENODEV (will never work), well, it seems worth considering advertising it with no delay even if it later fails if used. Arguably a transition from 2 to -ENODEV could be considered a kernel bug, but it doesn't sound like Alan would agree. :) Maybe Alan would agree to saying it's either a kernel, or system integration bug. I think it'd also be ok if we didn't advertise support if an application starts when the kernel is still in the 2 (will be ready soon) state. But, some environments might prefer to wait, so I think the kernel uapi should stay as Alan has it now so we have the flexibility to potentially accommodate this. (Perhaps with driconf, or a build flag, or an env-var.) -Jordan
