All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Gabriel Gama" <operatingsystemsdepression@gmail.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [RFC PATCH 3/6] drm/gma500: Fix SGX page-table cache-flush mapping lifetime
Date: Mon, 09 Nov 2026 06:00:50 +0000	[thread overview]
Message-ID: <sashiko-outbox-204475@kernel.org> (raw)
In-Reply-To: <20261109055451.17458-4-operatingsystemsdepression@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] drm/gma500: missing Fixes: trailer for SGX MMU cache-flush fixes
--

commit c92354a62278204d941ae70ac0f3b2869cb66190
Author: Gabriel Gama <operatingsystemsdepression@gmail.com>

> drm/gma500: Fix SGX page-table cache-flush mapping lifetime
>
> Flush the modified directory entry before unmapping it. The old order
> uses a kmap_atomic pointer outside its mapping lifetime, which DMA32
> direct mappings can mask. Use kmap_local_page under the existing spinlock.
>
> Also calculate the CLFLUSH iteration count only on the path that uses it,
> avoiding division by an uninitialized cache-line size when CLFLUSH
> is absent.
>
> Signed-off-by: Gabriel Gama <operatingsystemsdepression@gmail.com>

[Severity: Low]
Both the post-unmap cache flush in psb_mmu_pt_alloc_map_lock() and the
unconditional division by clflush_add in psb_mmu_alloc_pt() were
introduced in 8c8f1c958ab5 ("gma500: introduce the GTT and MMU handling
logic").  Should this include a Fixes: tag?

  Fixes: 8c8f1c958ab5 ("gma500: introduce the GTT and MMU handling logic")

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261109055451.17458-1-operatingsystemsdepression@gmail.com?part=3

  reply	other threads:[~2026-11-09  6:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09  5:54 [RFC PATCH 0/6] drm/gma500: prepare GEM and MMU for 3D rendering and hybrid 2D Gabriel Gama
2026-11-09  5:54 ` [RFC PATCH 1/6] drm/gma500: use the common dumb-buffer size helper Gabriel Gama
2026-11-09  5:54 ` [RFC PATCH 2/6] drm/gma500: do not underflow an unpinned GEM object Gabriel Gama
2026-11-09  5:54 ` [RFC PATCH 3/6] drm/gma500: Fix SGX page-table cache-flush mapping lifetime Gabriel Gama
2026-11-09  6:00   ` sashiko-bot [this message]
2026-11-09  5:54 ` [RFC PATCH 4/6] drm/gma500: Make SGX MMU insertion checked and transactional Gabriel Gama
2026-11-09  5:54 ` [RFC PATCH 5/6] drm/gma500: Propagate SGX MMU setup and GEM pin failures Gabriel Gama
2026-11-09  6:06   ` sashiko-bot
2026-11-09  5:54 ` [RFC PATCH 6/6] drm/gma500: Add software-only KUnit coverage for SGX page tables Gabriel Gama
2026-11-09  6:07   ` sashiko-bot
2026-11-09  6:26     ` Operating System's Depression

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=sashiko-outbox-204475@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=operatingsystemsdepression@gmail.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.