From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 5/7] drm/i915: move I915_GEM_GPU_DOMAINS to i915_gem.h
Date: Fri, 20 Jan 2023 05:40:46 -0500 [thread overview]
Message-ID: <Y8pvrrVAwtoEVsUD@intel.com> (raw)
In-Reply-To: <20230118131538.3558599-5-jani.nikula@intel.com>
On Wed, Jan 18, 2023 at 03:15:36PM +0200, Jani Nikula wrote:
> Declutter i915_drv.h.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/i915_drv.h | 7 -------
> drivers/gpu/drm/i915/i915_gem.h | 7 +++++++
> 2 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index 73ce5447cae8..eed552e507dc 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -68,13 +68,6 @@ struct drm_i915_clock_gating_funcs;
> struct vlv_s0ix_state;
> struct intel_pxp;
>
> -#define I915_GEM_GPU_DOMAINS \
> - (I915_GEM_DOMAIN_RENDER | \
> - I915_GEM_DOMAIN_SAMPLER | \
> - I915_GEM_DOMAIN_COMMAND | \
> - I915_GEM_DOMAIN_INSTRUCTION | \
> - I915_GEM_DOMAIN_VERTEX)
> -
> #define I915_COLOR_UNEVICTABLE (-1) /* a non-vma sharing the address space */
>
> #define GEM_QUIRK_PIN_SWIZZLED_PAGES BIT(0)
> diff --git a/drivers/gpu/drm/i915/i915_gem.h b/drivers/gpu/drm/i915/i915_gem.h
> index a5cdf6662d01..82e9d289398c 100644
> --- a/drivers/gpu/drm/i915/i915_gem.h
> +++ b/drivers/gpu/drm/i915/i915_gem.h
> @@ -39,6 +39,13 @@ struct i915_gem_ww_ctx;
> struct i915_gtt_view;
> struct i915_vma;
>
> +#define I915_GEM_GPU_DOMAINS \
> + (I915_GEM_DOMAIN_RENDER | \
> + I915_GEM_DOMAIN_SAMPLER | \
> + I915_GEM_DOMAIN_COMMAND | \
> + I915_GEM_DOMAIN_INSTRUCTION | \
> + I915_GEM_DOMAIN_VERTEX)
> +
this is getting used in i915_vma.c which is not directly importing
the i915_gem.h... should we add this include there explicitly or
rely on the .h indirection include?
> void i915_gem_init_early(struct drm_i915_private *i915);
> void i915_gem_cleanup_early(struct drm_i915_private *i915);
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-01-20 10:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 13:15 [Intel-gfx] [PATCH 1/7] drm/i915: add i915_config.h and move relevant declarations there Jani Nikula
2023-01-18 13:15 ` [Intel-gfx] [PATCH 2/7] drm/i915: move I915_IDLE_ENGINES_TIMEOUT next to its only user Jani Nikula
2023-01-18 13:27 ` Tvrtko Ursulin
2023-01-20 10:32 ` Rodrigo Vivi
2023-01-20 10:39 ` Jani Nikula
2023-01-18 13:15 ` [Intel-gfx] [PATCH 3/7] drm/i915: drop a number of unnecessary forward declarations Jani Nikula
2023-01-18 13:28 ` Tvrtko Ursulin
2023-01-20 10:34 ` Rodrigo Vivi
2023-01-18 13:15 ` [Intel-gfx] [PATCH 4/7] drm/i915: move a few HAS_ macros closer to their place Jani Nikula
2023-01-20 10:36 ` Rodrigo Vivi
2023-01-18 13:15 ` [Intel-gfx] [PATCH 5/7] drm/i915: move I915_GEM_GPU_DOMAINS to i915_gem.h Jani Nikula
2023-01-18 13:27 ` Tvrtko Ursulin
2023-01-18 14:05 ` Das, Nirmoy
2023-01-20 10:40 ` Rodrigo Vivi [this message]
2023-01-18 13:15 ` [Intel-gfx] [PATCH 6/7] drm/i915: move I915_COLOR_UNEVICTABLE to i915_gem_gtt.h Jani Nikula
2023-01-18 13:28 ` Tvrtko Ursulin
2023-01-20 10:43 ` Rodrigo Vivi
2023-01-23 13:17 ` Jani Nikula
2023-01-18 13:15 ` [Intel-gfx] [PATCH 7/7] drm/i915: move GT_FREQUENCY_MULTIPLIER and GEN9_FREQ_SCALER to intel_rps.h Jani Nikula
2023-01-18 13:28 ` Tvrtko Ursulin
2023-01-18 13:32 ` [Intel-gfx] [PATCH 1/7] drm/i915: add i915_config.h and move relevant declarations there Tvrtko Ursulin
2023-01-20 8:22 ` Jani Nikula
2023-01-18 22:03 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/7] " Patchwork
2023-01-18 22:34 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-01-19 1:39 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/7] drm/i915: add i915_config.h and move relevant declarations there (rev2) Patchwork
2023-01-19 1:39 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-01-19 2:09 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-01-20 1:16 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=Y8pvrrVAwtoEVsUD@intel.com \
--to=rodrigo.vivi@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox