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 v6 6/6] drm: Add arch arm64 for drm_clflush_virt_range
Date: Tue, 8 Feb 2022 10:20:26 +0000 [thread overview]
Message-ID: <cc66b673-a875-1c50-e437-1ce29e7b2d15@linux.intel.com> (raw)
In-Reply-To: <20220207201127.648624-7-michael.cheng@intel.com>
On 07/02/2022 20:11, Michael Cheng wrote:
> Use flush_tlb_kernel_range when invoking drm_clflush_virt_range on
> arm64 platforms. Using flush_tlb_kernel_range will:
>
> 1. Make sure prior page-table updates have been completed
> 2. Invalidate the TLB
> 3. Check if the TLB invalidation has been completed
Arm does not have a clflush equivalent but invalidating TLBs there
includes flushing caches?
Regards,
Tvrtko
> Signed-off-by: Michael Cheng <michael.cheng@intel.com>
> ---
> drivers/gpu/drm/drm_cache.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_cache.c b/drivers/gpu/drm/drm_cache.c
> index f19d9acbe959..d2506060a7c8 100644
> --- a/drivers/gpu/drm/drm_cache.c
> +++ b/drivers/gpu/drm/drm_cache.c
> @@ -176,6 +176,10 @@ 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;
> + flush_tlb_kernel_range(*addr, *end);
> #else
> pr_err("Architecture has no drm_cache.c support\n");
> WARN_ON_ONCE(1);
WARNING: multiple messages have this Message-ID (diff)
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Michael Cheng <michael.cheng@intel.com>, intel-gfx@lists.freedesktop.org
Cc: balasubramani.vivekanandan@intel.com, wayne.boyer@intel.com,
casey.g.bowman@intel.com, lucas.demarchi@intel.com,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v6 6/6] drm: Add arch arm64 for drm_clflush_virt_range
Date: Tue, 8 Feb 2022 10:20:26 +0000 [thread overview]
Message-ID: <cc66b673-a875-1c50-e437-1ce29e7b2d15@linux.intel.com> (raw)
In-Reply-To: <20220207201127.648624-7-michael.cheng@intel.com>
On 07/02/2022 20:11, Michael Cheng wrote:
> Use flush_tlb_kernel_range when invoking drm_clflush_virt_range on
> arm64 platforms. Using flush_tlb_kernel_range will:
>
> 1. Make sure prior page-table updates have been completed
> 2. Invalidate the TLB
> 3. Check if the TLB invalidation has been completed
Arm does not have a clflush equivalent but invalidating TLBs there
includes flushing caches?
Regards,
Tvrtko
> Signed-off-by: Michael Cheng <michael.cheng@intel.com>
> ---
> drivers/gpu/drm/drm_cache.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_cache.c b/drivers/gpu/drm/drm_cache.c
> index f19d9acbe959..d2506060a7c8 100644
> --- a/drivers/gpu/drm/drm_cache.c
> +++ b/drivers/gpu/drm/drm_cache.c
> @@ -176,6 +176,10 @@ 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;
> + flush_tlb_kernel_range(*addr, *end);
> #else
> pr_err("Architecture has no drm_cache.c support\n");
> WARN_ON_ONCE(1);
next prev parent reply other threads:[~2022-02-08 10:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 20:11 [Intel-gfx] [PATCH v6 0/6] Use drm_clflush* instead of clflush Michael Cheng
2022-02-07 20:11 ` Michael Cheng
2022-02-07 20:11 ` [Intel-gfx] [PATCH v6 1/6] drm/i915/gt: Re-work intel_write_status_page Michael Cheng
2022-02-07 20:11 ` Michael Cheng
2022-02-07 20:11 ` [Intel-gfx] [PATCH v6 2/6] drm/i915/gt: Drop invalidate_csb_entries Michael Cheng
2022-02-07 20:11 ` Michael Cheng
2022-02-07 20:11 ` [Intel-gfx] [PATCH v6 3/6] drm/i915/gt: Re-work reset_csb Michael Cheng
2022-02-07 20:11 ` Michael Cheng
2022-02-07 20:11 ` [Intel-gfx] [PATCH v6 4/6] drm/i915/: Re-work clflush_write32 Michael Cheng
2022-02-07 20:11 ` Michael Cheng
2022-02-09 16:52 ` [Intel-gfx] [PATCH] drm/i915/: fix noderef.cocci warnings kernel test robot
2022-02-09 16:52 ` kernel test robot
2022-02-09 16:52 ` kernel test robot
2022-02-09 16:52 ` [Intel-gfx] [PATCH v6 4/6] drm/i915/: Re-work clflush_write32 kernel test robot
2022-02-09 16:52 ` kernel test robot
2022-02-07 20:11 ` [Intel-gfx] [PATCH v6 5/6] drm/i915/gt: replace cache_clflush_range Michael Cheng
2022-02-07 20:11 ` Michael Cheng
2022-02-07 20:11 ` [Intel-gfx] [PATCH v6 6/6] drm: Add arch arm64 for drm_clflush_virt_range Michael Cheng
2022-02-07 20:11 ` Michael Cheng
2022-02-08 3:51 ` [Intel-gfx] " kernel test robot
2022-02-08 3:51 ` kernel test robot
2022-02-08 3:51 ` kernel test robot
2022-02-08 4:22 ` kernel test robot
2022-02-08 4:22 ` kernel test robot
2022-02-08 10:20 ` Tvrtko Ursulin [this message]
2022-02-08 10:20 ` Tvrtko Ursulin
2022-02-08 15:50 ` [Intel-gfx] " Michael Cheng
2022-02-08 15:50 ` Michael Cheng
2022-02-07 20:29 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Use drm_clflush* instead of clflush (rev5) Patchwork
2022-02-07 20:31 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-02-07 21:01 ` [Intel-gfx] ✗ Fi.CI.BAT: 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=cc66b673-a875-1c50-e437-1ce29e7b2d15@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 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.