Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: Michael Cheng <michael.cheng@intel.com>
Cc: intel-gfx@lists.freedesktop.org, lucas.demarchi@intel.com,
	dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v10 2/6] drm/i915/gt: Re-work intel_write_status_page
Date: Tue, 22 Feb 2022 14:04:21 -0800	[thread overview]
Message-ID: <YhVd5bAYTLc9VbDu@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <20220210183636.1187973-3-michael.cheng@intel.com>

On Thu, Feb 10, 2022 at 10:36:32AM -0800, Michael Cheng wrote:
> Re-work intel_write_status_page to use drm_clflush_virt_range. This
> will prevent compiler errors when building for non-x86 architectures.
> 

It looks like this will also cause old x86 cpu's that don't have clflush
to do an extra wbinvd that they didn't do before; based on commit
9a29dd85a09d ("drm/i915: Fixup intel_write_status_page() for old CPUs
without clflush") we were just hoping that they were sufficiently
coherent that we can get away without extra flushing.

As far as I can see, this function is only used from a selftest, not
from real driver codepaths, so the extra flushing shouldn't have any
negative impact on end users.

Reviewed-by: Matt Roper <matthew.d.roper@intel.com>

> Signed-off-by: Michael Cheng <michael.cheng@intel.com>
> ---
>  drivers/gpu/drm/i915/gt/intel_engine.h | 13 ++++---------
>  1 file changed, 4 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/gt/intel_engine.h b/drivers/gpu/drm/i915/gt/intel_engine.h
> index 0e353d8c2bc8..986777c2430d 100644
> --- a/drivers/gpu/drm/i915/gt/intel_engine.h
> +++ b/drivers/gpu/drm/i915/gt/intel_engine.h
> @@ -4,6 +4,7 @@
>  
>  #include <asm/cacheflush.h>
>  #include <drm/drm_util.h>
> +#include <drm/drm_cache.h>
>  
>  #include <linux/hashtable.h>
>  #include <linux/irq_work.h>
> @@ -143,15 +144,9 @@ intel_write_status_page(struct intel_engine_cs *engine, int reg, u32 value)
>  	 * of extra paranoia to try and ensure that the HWS takes the value
>  	 * we give and that it doesn't end up trapped inside the CPU!
>  	 */
> -	if (static_cpu_has(X86_FEATURE_CLFLUSH)) {
> -		mb();
> -		clflush(&engine->status_page.addr[reg]);
> -		engine->status_page.addr[reg] = value;
> -		clflush(&engine->status_page.addr[reg]);
> -		mb();
> -	} else {
> -		WRITE_ONCE(engine->status_page.addr[reg], value);
> -	}
> +	drm_clflush_virt_range(&engine->status_page.addr[reg], sizeof(value));
> +	WRITE_ONCE(engine->status_page.addr[reg], value);
> +	drm_clflush_virt_range(&engine->status_page.addr[reg], sizeof(value));
>  }
>  
>  /*
> -- 
> 2.25.1
> 

-- 
Matt Roper
Graphics Software Engineer
VTT-OSGC Platform Enablement
Intel Corporation
(916) 356-2795

  reply	other threads:[~2022-02-22 22:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 18:36 [Intel-gfx] [PATCH v10 0/6] Use drm_clflush* instead of clflush Michael Cheng
2022-02-10 18:36 ` [Intel-gfx] [PATCH v10 1/6] drm: Add arch arm64 for drm_clflush_virt_range Michael Cheng
2022-02-22 21:49   ` Matt Roper
2022-02-10 18:36 ` [Intel-gfx] [PATCH v10 2/6] drm/i915/gt: Re-work intel_write_status_page Michael Cheng
2022-02-22 22:04   ` Matt Roper [this message]
2022-02-10 18:36 ` [Intel-gfx] [PATCH v10 3/6] drm/i915/gt: Drop invalidate_csb_entries Michael Cheng
2022-02-22 22:31   ` Matt Roper
2022-02-10 18:36 ` [Intel-gfx] [PATCH v10 4/6] drm/i915/gt: Re-work reset_csb Michael Cheng
2022-02-22 22:35   ` Matt Roper
2022-02-10 18:36 ` [Intel-gfx] [PATCH v10 5/6] drm/i915/: Re-work clflush_write32 Michael Cheng
2022-02-22 22:37   ` Matt Roper
2022-02-10 18:36 ` [Intel-gfx] [PATCH v10 6/6] drm/i915/gt: replace cache_clflush_range Michael Cheng
2022-02-22 22:40   ` Matt Roper
2022-02-10 19:07 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Use drm_clflush* instead of clflush (rev9) Patchwork
2022-02-10 19:08 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-10 19:34 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-10 23:22 ` [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=YhVd5bAYTLc9VbDu@mdroper-desk1.amr.corp.intel.com \
    --to=matthew.d.roper@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=michael.cheng@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