All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Paunovic <royalnet026@gmail.com>
To: Triet Hoang <triet.hoang.dev@gmail.com>
Cc: Igor Paunovic <royalnet026@gmail.com>,
	Tomeu Vizoso <tomeu@tomeuvizoso.net>,
	Oded Gabbay <ogabbay@kernel.org>,
	Markus Elfring <markus.elfring@web.de>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] drm/rocket: Check allocations before use
Date: Wed, 19 Aug 2026 18:35:07 +0200	[thread overview]
Message-ID: <20260819163509.5743-1-royalnet026@gmail.com> (raw)
In-Reply-To: <20260818041505.1579320-1-triet.hoang.dev@gmail.com>

Hi Triet,

Ran v5 on RK3588 hardware (Orange Pi 5 Plus, all three cores), on a
tree with PROVE_LOCKING and DEBUG_ATOMIC_SLEEP enabled: 30 sequential
client cycles (open/submit/close), 10 pairs of concurrent clients, and
a round across runtime suspend/resume - 45/45 inferences bit-correct
against the reference, zero warnings of any kind, cores returning to
runtime-suspended cleanly.

One honest limit: this exercises the success paths your checks guard;
the allocation-failure branches themselves I reviewed but did not
fault-inject.

Tested-by: Igor Paunovic <royalnet026@gmail.com> # RK3588, functional,
                                                 # no fault injection

Regards,
Igor

  parent reply	other threads:[~2026-08-19 16:35 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17  5:39 [PATCH] drm/rocket: Check allocations before use Triet Hoang
2026-08-17  5:53 ` sashiko-bot
2026-08-17  7:20   ` [PATCH v2] " Triet Hoang
2026-08-17  7:35     ` sashiko-bot
2026-08-17  9:20     ` Markus Elfring
2026-08-17  9:31       ` [PATCH v3] " Triet Hoang
2026-08-17  9:45         ` sashiko-bot
2026-08-17  9:55         ` Markus Elfring
2026-08-17 11:22           ` Triet Hoang
2026-08-17  9:30     ` [PATCH v2] " Igor Paunovic
2026-08-17  9:53       ` Triet Hoang
2026-08-17 13:14       ` Triet Hoang
2026-08-17 14:01       ` [PATCH v4 1/2] " Triet Hoang
2026-08-17 14:01         ` [PATCH v4 2/2] drm/rocket: Keep scheduler allocation in rocket_file_priv Triet Hoang
2026-08-17 14:11           ` sashiko-bot
2026-08-17 17:06           ` Markus Elfring
2026-08-17 14:18         ` [PATCH v4 1/2] drm/rocket: Check allocations before use sashiko-bot
2026-08-17 16:40         ` Markus Elfring
2026-08-18  1:31           ` Triet Hoang
2026-08-18  5:48             ` [v4 " Markus Elfring
2026-08-18  6:21               ` [PATCH] " Triet Hoang
2026-08-17 14:28       ` [PATCH v2] " Triet Hoang
2026-08-18  1:55         ` Triet Hoang
2026-08-18  1:56         ` Triet Hoang
2026-08-18  4:15       ` [PATCH v5 1/2] " Triet Hoang
2026-08-18  4:15         ` [PATCH v5 2/2] drm/rocket: Keep scheduler allocation in rocket_file_priv Triet Hoang
2026-08-18  4:23           ` [PATCH v5] drm/rocket: Check allocations before use Triet Hoang
2026-08-19 16:35           ` [PATCH v5 2/2] drm/rocket: Keep scheduler allocation in rocket_file_priv Igor Paunovic
2026-08-18  4:32         ` [PATCH v5 1/2] drm/rocket: Check allocations before use sashiko-bot
2026-08-19 16:35         ` Igor Paunovic [this message]
2026-08-20  1:31           ` Triet Hoang

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=20260819163509.5743-1-royalnet026@gmail.com \
    --to=royalnet026@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.elfring@web.de \
    --cc=ogabbay@kernel.org \
    --cc=tomeu@tomeuvizoso.net \
    --cc=triet.hoang.dev@gmail.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.