@lists.freedesktop.org
Cc: Lahtinen, Joonas ; Joonas Lahtinen
; Ekstrand, Jason
Subject: Re: [Intel-gfx] [RFC-v23 00/13] Introduce Intel PXP component - Mesa
single session
Okay, if the get_param is too much at the point, can we at least have a define
to reflect that this is a special number from the kernel
, Sean Z ; Intel-gfx@lists.freedesktop.org
Cc: Gaurav, Kumar ; Lahtinen, Joonas ;
Joonas Lahtinen ; Ekstrand, Jason
Subject: Re: [Intel-gfx] [RFC-v23 00/13] Introduce Intel PXP component - Mesa
single session
Hi,
One of the thing that came up during UMD review is that the default session ID
.
-Original Message-
From: Lionel Landwerlin
Sent: Saturday, January 23, 2021 6:19 AM
To: Huang, Sean Z ; Intel-gfx@lists.freedesktop.org
Cc: Gaurav, Kumar ; Lahtinen, Joonas
; Joonas Lahtinen ;
Ekstrand, Jason
Subject: Re: [Intel-gfx] [RFC-v23 00/13] Introduce Intel PXP component - Mesa
Hi,
One of the thing that came up during UMD review is that the default
session ID is actually uAPI :
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/8064#note_776201
Could we expose it through a get_param on the context?
Thanks,
-Lionel
On 19/01/2021 09:43, Huang, Sean Z wrote:
PXP (Protected Xe Path) is an i915 component, available on
GEN12+ that helps to establish the hardware protected session
and manage the status of the alive software session, as well
as its life cycle.
This patch series is to allow the kernel space to create and
manage a single hardware session (a.
