diff mbox series

drm/doc/rfc/xe: No STAGING in drm.

Message ID 20230522195712.2162736-1-rodrigo.vivi@intel.com (mailing list archive)
State New, archived
Headers show
Series drm/doc/rfc/xe: No STAGING in drm. | expand

Commit Message

Rodrigo Vivi May 22, 2023, 7:57 p.m. UTC
We are not using the STAGING inside drm and the uAPI needs to be
in the acceptable form before we get merged upstream.

Link: https://lore.kernel.org/all/2023051029-overspend-sherry-1b85@gregkh/
Cc: Dave Airlie <airlied@redhat.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Oded Gabbay <ogabbay@kernel.org>
Cc: Francois Dugast <francois.dugast@intel.com>
Cc: Luis Strano <luis.strano@intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
---
 Documentation/gpu/rfc/xe.rst | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

Comments

Lucas De Marchi May 23, 2023, 6:40 a.m. UTC | #1
On Mon, May 22, 2023 at 03:57:12PM -0400, Rodrigo Vivi wrote:
>We are not using the STAGING inside drm and the uAPI needs to be
>in the acceptable form before we get merged upstream.

Is this a change from i915, where the force_probe protection 
is sufficient?

The email exchange with Greg KH  highlighted that the use of STAGING
outside of staging dir doesn't really produce the desired effect*.
Would it be sufficient to taint the kernel with bit 10 or
create a dedicated taint for this case?

Lucas De Marchi

* The logic for adding the taint is in the module load code and is
   triggered for modules with MODULE_INFO(staging), automatically
   added by modpost for modules under drivers/staging

>
>Link: https://lore.kernel.org/all/2023051029-overspend-sherry-1b85@gregkh/
>Cc: Dave Airlie <airlied@redhat.com>
>Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>Cc: Oded Gabbay <ogabbay@kernel.org>
>Cc: Francois Dugast <francois.dugast@intel.com>
>Cc: Luis Strano <luis.strano@intel.com>
>Cc: Matthew Brost <matthew.brost@intel.com>
>Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
>Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>---
> Documentation/gpu/rfc/xe.rst | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
>diff --git a/Documentation/gpu/rfc/xe.rst b/Documentation/gpu/rfc/xe.rst
>index 2516fe141db6..8524095a54bd 100644
>--- a/Documentation/gpu/rfc/xe.rst
>+++ b/Documentation/gpu/rfc/xe.rst
>@@ -67,11 +67,8 @@ platforms.
>
> When the time comes for Xe, the protection will be lifted on Xe and kept in i915.
>
>-Xe driver will be protected with both STAGING Kconfig and force_probe. Changes in
>-the uAPI are expected while the driver is behind these protections. STAGING will
>-be removed when the driver uAPI gets to a mature state where we can guarantee the
>-‘no regression’ rule. Then force_probe will be lifted only for future platforms
>-that will be productized with Xe driver, but not with i915.
>+Xe driver will be protected with force_probe, which will be lifted only for
>+future platforms that will be productized with Xe driver, but not with i915.
>
> Xe – Pre-Merge Goals
> ====================
>-- 
>2.39.2
>
diff mbox series

Patch

diff --git a/Documentation/gpu/rfc/xe.rst b/Documentation/gpu/rfc/xe.rst
index 2516fe141db6..8524095a54bd 100644
--- a/Documentation/gpu/rfc/xe.rst
+++ b/Documentation/gpu/rfc/xe.rst
@@ -67,11 +67,8 @@  platforms.
 
 When the time comes for Xe, the protection will be lifted on Xe and kept in i915.
 
-Xe driver will be protected with both STAGING Kconfig and force_probe. Changes in
-the uAPI are expected while the driver is behind these protections. STAGING will
-be removed when the driver uAPI gets to a mature state where we can guarantee the
-‘no regression’ rule. Then force_probe will be lifted only for future platforms
-that will be productized with Xe driver, but not with i915.
+Xe driver will be protected with force_probe, which will be lifted only for
+future platforms that will be productized with Xe driver, but not with i915.
 
 Xe – Pre-Merge Goals
 ====================