From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Michael Cheng <michael.cheng@intel.com>, intel-gfx@lists.freedesktop.org
Cc: lucas.demarchi@intel.com, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v12 1/6] drm: Add arch arm64 for drm_clflush_virt_range
Date: Fri, 25 Feb 2022 16:28:32 +0000 [thread overview]
Message-ID: <011a236d-7ed4-0d48-e8a6-c9bd98740d5b@linux.intel.com> (raw)
In-Reply-To: <20220225032436.904942-2-michael.cheng@intel.com>
On 25/02/2022 03:24, Michael Cheng wrote:
> Add arm64 support for drm_clflush_virt_range. caches_clean_inval_pou
> performs a flush by first performing a clean, follow by an invalidation
> operation.
>
> v2 (Michael Cheng): Use correct macro for cleaning and invalidation the
> dcache. Thanks Tvrtko for the suggestion.
>
> v3 (Michael Cheng): Replace asm/cacheflush.h with linux/cacheflush.h
>
> v4 (Michael Cheng): Arm64 does not export dcache_clean_inval_poc as a
> symbol that could be use by other modules, thus use
> caches_clean_inval_pou instead. Also this version
> removes include for cacheflush, since its already
> included base on architecture type.
What does it mean that it is included based on architecture type? Some
of the other header already pulls it in?
Regards,
Tvrtko
> Signed-off-by: Michael Cheng <michael.cheng@intel.com>
> Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
> ---
> drivers/gpu/drm/drm_cache.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_cache.c b/drivers/gpu/drm/drm_cache.c
> index c3e6e615bf09..81c28714f930 100644
> --- a/drivers/gpu/drm/drm_cache.c
> +++ b/drivers/gpu/drm/drm_cache.c
> @@ -174,6 +174,11 @@ drm_clflush_virt_range(void *addr, unsigned long length)
>
> if (wbinvd_on_all_cpus())
> pr_err("Timed out waiting for cache flush\n");
> +
> +#elif defined(CONFIG_ARM64)
> + void *end = addr + length;
> + caches_clean_inval_pou((unsigned long)addr, (unsigned long)end);
> +
> #else
> WARN_ONCE(1, "Architecture has no drm_cache.c support\n");
> #endif
next prev parent reply other threads:[~2022-02-25 16:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 3:24 [Intel-gfx] [PATCH v12 0/6] Use drm_clflush* instead of clflush Michael Cheng
2022-02-25 3:24 ` [Intel-gfx] [PATCH v12 1/6] drm: Add arch arm64 for drm_clflush_virt_range Michael Cheng
2022-02-25 16:28 ` Tvrtko Ursulin [this message]
2022-02-25 16:52 ` Michael Cheng
2022-02-25 17:33 ` Tvrtko Ursulin
2022-02-25 17:40 ` Michael Cheng
2022-02-25 18:19 ` Tvrtko Ursulin
2022-02-25 18:23 ` Michael Cheng
2022-02-25 18:42 ` Tvrtko Ursulin
2022-02-25 18:58 ` Matthew Wilcox
2022-02-25 18:24 ` Robin Murphy
2022-02-25 19:27 ` Michael Cheng
2022-03-02 12:49 ` Robin Murphy
2022-03-02 15:55 ` Michael Cheng
2022-03-02 17:06 ` Alex Deucher
2022-03-02 19:10 ` Robin Murphy
2022-03-07 16:52 ` Michael Cheng
2022-02-25 3:24 ` [Intel-gfx] [PATCH v12 2/6] drm/i915/gt: Re-work intel_write_status_page Michael Cheng
2022-02-25 3:24 ` [Intel-gfx] [PATCH v12 3/6] drm/i915/gt: Drop invalidate_csb_entries Michael Cheng
2022-02-25 3:24 ` [Intel-gfx] [PATCH v12 4/6] drm/i915/gt: Re-work reset_csb Michael Cheng
2022-02-25 3:24 ` [Intel-gfx] [PATCH v12 5/6] drm/i915/: Re-work clflush_write32 Michael Cheng
2022-02-25 3:24 ` [Intel-gfx] [PATCH v12 6/6] drm/i915/gt: replace cache_clflush_range Michael Cheng
2022-02-25 7:28 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Use drm_clflush* instead of clflush Patchwork
2022-02-25 7:29 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-25 7:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-02-26 1:56 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=011a236d-7ed4-0d48-e8a6-c9bd98740d5b@linux.intel.com \
--to=tvrtko.ursulin@linux.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