From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Jani Nikula <jani.nikula@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, Dave Airlie <airlied@redhat.com>
Subject: Re: [PATCH 02/11] drm/i915: Put future HW and their uAPIs under STAGING & BROKEN
Date: Thu, 24 Oct 2019 16:35:30 -0700 [thread overview]
Message-ID: <20191024233530.GA3088@intel.com> (raw)
In-Reply-To: <20191024114028.6170-3-chris@chris-wilson.co.uk>
On Thu, Oct 24, 2019 at 12:40:19PM +0100, Chris Wilson wrote:
> We would like some freedom to break the user API/ABI for future HW but
> yet still expose the driver for upstream development on that HW.
> Currently, we have the i915.force_probe module parameter to avoid binding
> to HW while the driver is under development, but that is still a little
> too soft with respect to the stringent no-regression rules if we also
> plan to be redesigning the uAPI to go along with the new HW.
>
> To allow the uAPI to be changed during development, only expose that API
> and in development HW under STAGING (and BROKEN). Hopefully, making it
> explicit that such interfaces to that HW are under development and not
> to be blindly enabled by distributions.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Dave Airlie <airlied@redhat.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/i915/Kconfig | 8 ++++++++
> drivers/gpu/drm/i915/Kconfig.debug | 1 +
> drivers/gpu/drm/i915/Kconfig.unstable | 20 ++++++++++++++++++++
> 3 files changed, 29 insertions(+)
> create mode 100644 drivers/gpu/drm/i915/Kconfig.unstable
>
> diff --git a/drivers/gpu/drm/i915/Kconfig b/drivers/gpu/drm/i915/Kconfig
> index 3c6d57df262d..1fd9e665b742 100644
> --- a/drivers/gpu/drm/i915/Kconfig
> +++ b/drivers/gpu/drm/i915/Kconfig
> @@ -148,3 +148,11 @@ menu "drm/i915 Profile Guided Optimisation"
> depends on DRM_I915
> source "drivers/gpu/drm/i915/Kconfig.profile"
> endmenu
> +
> +menu "drm/i915 Ustable Evolution"
> + visible if EXPERT
> + visible if STAGING
> + visible if BROKEN
> + depends on DRM_I915
> + source "drivers/gpu/drm/i915/Kconfig.unstable"
> +endmenu
> diff --git a/drivers/gpu/drm/i915/Kconfig.debug b/drivers/gpu/drm/i915/Kconfig.debug
> index d2ba8f7e5e50..ef123eb29168 100644
> --- a/drivers/gpu/drm/i915/Kconfig.debug
> +++ b/drivers/gpu/drm/i915/Kconfig.debug
> @@ -44,6 +44,7 @@ config DRM_I915_DEBUG
> select DRM_I915_SELFTEST
> select DRM_I915_DEBUG_RUNTIME_PM
> select DRM_I915_DEBUG_MMIO
> + select BROKEN # for prototype uAPI
> default n
> help
> Choose this option to turn on extra driver debugging that may affect
> diff --git a/drivers/gpu/drm/i915/Kconfig.unstable b/drivers/gpu/drm/i915/Kconfig.unstable
> new file mode 100644
> index 000000000000..ecc8458b5a32
> --- /dev/null
> +++ b/drivers/gpu/drm/i915/Kconfig.unstable
> @@ -0,0 +1,20 @@
> +# SPDX-License-Identifier: GPL-2.0-only
> +config DRM_I915_UNSTABLE
> + bool "Enable unstable API for early prototype development"
> + depends on EXPERT
> + depends on STAGING
> + depends on BROKEN # should never be enabled by distros!
> + # We use the dependency on !COMPILE_TEST to not be enabled in
> + # allmodconfig or allyesconfig configurations
> + depends on !COMPILE_TEST
> + default n
> + help
> + Enable prototype uAPI under general discussion before they are
> + finalized. Such prototypes may be withdrawn or substantially
> + changed before release. They are only enabled here so that a wide
> + number of interested parties (userspace driver developers) can
> + verify that the uAPI meet their expectations.
> +
> + Recommended for driver developers _only_.
> +
> + If in the slightest bit of doubt, say "N".
> --
> 2.24.0.rc0
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Jani Nikula <jani.nikula@intel.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, Dave Airlie <airlied@redhat.com>
Subject: Re: [Intel-gfx] [PATCH 02/11] drm/i915: Put future HW and their uAPIs under STAGING & BROKEN
Date: Thu, 24 Oct 2019 16:35:30 -0700 [thread overview]
Message-ID: <20191024233530.GA3088@intel.com> (raw)
Message-ID: <20191024233530.4mKZPtyCcKQx1_N8qXxFsYFhm0DUyXVUXvRYoMJTe4A@z> (raw)
In-Reply-To: <20191024114028.6170-3-chris@chris-wilson.co.uk>
On Thu, Oct 24, 2019 at 12:40:19PM +0100, Chris Wilson wrote:
> We would like some freedom to break the user API/ABI for future HW but
> yet still expose the driver for upstream development on that HW.
> Currently, we have the i915.force_probe module parameter to avoid binding
> to HW while the driver is under development, but that is still a little
> too soft with respect to the stringent no-regression rules if we also
> plan to be redesigning the uAPI to go along with the new HW.
>
> To allow the uAPI to be changed during development, only expose that API
> and in development HW under STAGING (and BROKEN). Hopefully, making it
> explicit that such interfaces to that HW are under development and not
> to be blindly enabled by distributions.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Dave Airlie <airlied@redhat.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/i915/Kconfig | 8 ++++++++
> drivers/gpu/drm/i915/Kconfig.debug | 1 +
> drivers/gpu/drm/i915/Kconfig.unstable | 20 ++++++++++++++++++++
> 3 files changed, 29 insertions(+)
> create mode 100644 drivers/gpu/drm/i915/Kconfig.unstable
>
> diff --git a/drivers/gpu/drm/i915/Kconfig b/drivers/gpu/drm/i915/Kconfig
> index 3c6d57df262d..1fd9e665b742 100644
> --- a/drivers/gpu/drm/i915/Kconfig
> +++ b/drivers/gpu/drm/i915/Kconfig
> @@ -148,3 +148,11 @@ menu "drm/i915 Profile Guided Optimisation"
> depends on DRM_I915
> source "drivers/gpu/drm/i915/Kconfig.profile"
> endmenu
> +
> +menu "drm/i915 Ustable Evolution"
> + visible if EXPERT
> + visible if STAGING
> + visible if BROKEN
> + depends on DRM_I915
> + source "drivers/gpu/drm/i915/Kconfig.unstable"
> +endmenu
> diff --git a/drivers/gpu/drm/i915/Kconfig.debug b/drivers/gpu/drm/i915/Kconfig.debug
> index d2ba8f7e5e50..ef123eb29168 100644
> --- a/drivers/gpu/drm/i915/Kconfig.debug
> +++ b/drivers/gpu/drm/i915/Kconfig.debug
> @@ -44,6 +44,7 @@ config DRM_I915_DEBUG
> select DRM_I915_SELFTEST
> select DRM_I915_DEBUG_RUNTIME_PM
> select DRM_I915_DEBUG_MMIO
> + select BROKEN # for prototype uAPI
> default n
> help
> Choose this option to turn on extra driver debugging that may affect
> diff --git a/drivers/gpu/drm/i915/Kconfig.unstable b/drivers/gpu/drm/i915/Kconfig.unstable
> new file mode 100644
> index 000000000000..ecc8458b5a32
> --- /dev/null
> +++ b/drivers/gpu/drm/i915/Kconfig.unstable
> @@ -0,0 +1,20 @@
> +# SPDX-License-Identifier: GPL-2.0-only
> +config DRM_I915_UNSTABLE
> + bool "Enable unstable API for early prototype development"
> + depends on EXPERT
> + depends on STAGING
> + depends on BROKEN # should never be enabled by distros!
> + # We use the dependency on !COMPILE_TEST to not be enabled in
> + # allmodconfig or allyesconfig configurations
> + depends on !COMPILE_TEST
> + default n
> + help
> + Enable prototype uAPI under general discussion before they are
> + finalized. Such prototypes may be withdrawn or substantially
> + changed before release. They are only enabled here so that a wide
> + number of interested parties (userspace driver developers) can
> + verify that the uAPI meet their expectations.
> +
> + Recommended for driver developers _only_.
> +
> + If in the slightest bit of doubt, say "N".
> --
> 2.24.0.rc0
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-10-24 23:34 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 11:40 CI testing of persistence and sysfs Chris Wilson
2019-10-24 11:40 ` [Intel-gfx] " Chris Wilson
2019-10-24 11:40 ` [PATCH 01/11] drm/i915/gem: Make context persistence optional Chris Wilson
2019-10-24 11:40 ` [Intel-gfx] " Chris Wilson
2019-10-25 9:10 ` Joonas Lahtinen
2019-10-25 9:10 ` [Intel-gfx] " Joonas Lahtinen
2019-10-25 18:22 ` Jason Ekstrand
2019-10-25 18:22 ` [Intel-gfx] " Jason Ekstrand
2019-10-25 21:29 ` Chris Wilson
2019-10-25 21:29 ` [Intel-gfx] " Chris Wilson
2019-10-29 16:19 ` Jason Ekstrand
2019-10-29 16:19 ` [Intel-gfx] " Jason Ekstrand
2019-10-29 18:02 ` Chris Wilson
2019-10-29 18:02 ` [Intel-gfx] " Chris Wilson
2019-10-24 11:40 ` [PATCH 02/11] drm/i915: Put future HW and their uAPIs under STAGING & BROKEN Chris Wilson
2019-10-24 11:40 ` [Intel-gfx] " Chris Wilson
2019-10-24 23:25 ` David Airlie
2019-10-24 23:25 ` [Intel-gfx] " David Airlie
2019-10-24 23:35 ` Rodrigo Vivi [this message]
2019-10-24 23:35 ` Rodrigo Vivi
2019-10-25 7:09 ` Jani Nikula
2019-10-25 7:09 ` [Intel-gfx] " Jani Nikula
2019-10-24 11:40 ` [PATCH 03/11] drm/i915/gt: Expose engine properties via sysfs Chris Wilson
2019-10-24 11:40 ` [Intel-gfx] " Chris Wilson
2019-10-24 11:40 ` [PATCH 04/11] drm/i915/gt: Expose engine->mmio_base " Chris Wilson
2019-10-24 11:40 ` [Intel-gfx] " Chris Wilson
2019-10-24 11:40 ` [PATCH 05/11] drm/i915/gt: Expose timeslice duration to sysfs Chris Wilson
2019-10-24 11:40 ` [Intel-gfx] " Chris Wilson
2019-10-24 11:40 ` [PATCH 06/11] drm/i915/gt: Expose reset stop timeout via sysfs Chris Wilson
2019-10-24 11:40 ` [Intel-gfx] " Chris Wilson
2019-10-24 11:40 ` [PATCH 07/11] drm/i915/gt: Expose preempt reset " Chris Wilson
2019-10-24 11:40 ` [Intel-gfx] " Chris Wilson
2019-10-24 11:40 ` [PATCH 08/11] drm/i915/gt: Expose heartbeat interval " Chris Wilson
2019-10-24 11:40 ` [Intel-gfx] " Chris Wilson
2019-10-24 11:40 ` [PATCH 09/11] drm/i915: Flush idle barriers when waiting Chris Wilson
2019-10-24 11:40 ` [Intel-gfx] " Chris Wilson
2019-10-24 11:40 ` [PATCH 10/11] drm/i915: Allow userspace to specify ringsize on construction Chris Wilson
2019-10-24 11:40 ` [Intel-gfx] " Chris Wilson
2019-10-24 11:40 ` [PATCH 11/11] drm/i915/gem: Honour O_NONBLOCK before throttling execbuf submissions Chris Wilson
2019-10-24 11:40 ` [Intel-gfx] " Chris Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191024233530.GA3088@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.