dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@collabora.com>
To: dri-devel@lists.freedesktop.org
Cc: "Daniel Vetter" <daniel@ffwll.ch>,
	"Marty E . Plummer" <hanetzer@startmail.com>,
	"Rob Herring" <robh@kernel.org>,
	"Clément Péron" <peron.clem@gmail.com>,
	"Nicolas Boichat" <drinkcat@chromium.org>,
	"Neil Armstrong" <neil.armstrong@linaro.org>,
	"Faith Ekstrand" <faith.ekstrand@collabora.com>,
	"Daniel Stone" <daniels@collabora.com>,
	"Liviu Dudau" <Liviu.Dudau@arm.com>,
	"Steven Price" <steven.price@arm.com>,
	"Robin Murphy" <robin.murphy@arm.com>,
	kernel@collabora.com, "Heiko Stuebner" <heiko@sntech.de>,
	"Tatsuyuki Ishi" <ishitatsuyuki@gmail.com>,
	"Chris Diamand" <chris.diamand@foss.arm.com>,
	"Ketil Johnsen" <ketil.johnsen@arm.com>
Subject: Re: [PATCH v5 10/14] drm/panthor: Add the scheduler logical block
Date: Wed, 28 Feb 2024 19:11:40 +0100	[thread overview]
Message-ID: <20240228191140.6e3d8ce8@collabora.com> (raw)
In-Reply-To: <20240218214131.3035480-11-boris.brezillon@collabora.com>

On Sun, 18 Feb 2024 22:41:24 +0100
Boris Brezillon <boris.brezillon@collabora.com> wrote:

> +static void panthor_sched_immediate_tick(struct panthor_device *ptdev)
> +{
> +	struct panthor_scheduler *sched = ptdev->scheduler;
> +
> +	sched_queue_delayed_work(sched, tick, 0);
> +}
> +
> +/**
> + * panthor_sched_report_mmu_fault() - Report MMU faults to the scheduler.
> + */
> +void panthor_sched_report_mmu_fault(struct panthor_device *ptdev)
> +{
> +	/* Force a tick to immediately kill faulty groups. */
> +	panthor_sched_immediate_tick(ptdev);

We need

	if (ptdev->scheduler)
		panthor_sched_immediate_tick(ptdev);

to prevent a NULL deref in panthor_sched_immediate_tick() if the MMU
fault handler is called before the scheduler block is initialized (FW
boot might trigger MMU faults on AS0).

> +}

  reply	other threads:[~2024-02-28 18:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18 21:41 [PATCH v5 00/14] drm: Add a driver for CSF-based Mali GPUs Boris Brezillon
2024-02-18 21:41 ` [PATCH v5 01/14] drm/panthor: Add uAPI Boris Brezillon
2024-02-18 21:41 ` [PATCH v5 02/14] drm/panthor: Add GPU register definitions Boris Brezillon
2024-02-18 21:41 ` [PATCH v5 03/14] drm/panthor: Add the device logical block Boris Brezillon
2024-02-18 21:41 ` [PATCH v5 04/14] drm/panthor: Add the GPU " Boris Brezillon
2024-02-18 21:41 ` [PATCH v5 05/14] drm/panthor: Add GEM " Boris Brezillon
2024-02-18 21:41 ` [PATCH v5 06/14] drm/panthor: Add the devfreq " Boris Brezillon
2024-02-18 21:41 ` [PATCH v5 07/14] drm/panthor: Add the MMU/VM " Boris Brezillon
2024-02-19 14:54   ` Steven Price
2024-02-28 18:14   ` Boris Brezillon
2024-02-18 21:41 ` [PATCH v5 08/14] drm/panthor: Add the FW " Boris Brezillon
2024-02-18 21:41 ` [PATCH v5 09/14] drm/panthor: Add the heap " Boris Brezillon
2024-02-18 21:41 ` [PATCH v5 10/14] drm/panthor: Add the scheduler " Boris Brezillon
2024-02-28 18:11   ` Boris Brezillon [this message]
2024-02-18 21:41 ` [PATCH v5 11/14] drm/panthor: Add the driver frontend block Boris Brezillon
2024-02-29  9:11   ` Boris Brezillon
2024-02-18 21:41 ` [PATCH v5 12/14] drm/panthor: Allow driver compilation Boris Brezillon
2024-02-28 10:35   ` Boris Brezillon
2024-02-18 21:41 ` [PATCH v5 13/14] dt-bindings: gpu: mali-valhall-csf: Add support for Arm Mali CSF GPUs Boris Brezillon
2024-02-18 21:41 ` [PATCH v5 14/14] drm/panthor: Add an entry to MAINTAINERS Boris Brezillon
2024-02-26 13:50 ` [PATCH v5 00/14] drm: Add a driver for CSF-based Mali GPUs Liviu Dudau
2024-02-27  7:11 ` Maxime Ripard
2024-02-28 10:31 ` Heiko Stübner

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=20240228191140.6e3d8ce8@collabora.com \
    --to=boris.brezillon@collabora.com \
    --cc=Liviu.Dudau@arm.com \
    --cc=chris.diamand@foss.arm.com \
    --cc=daniel@ffwll.ch \
    --cc=daniels@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=drinkcat@chromium.org \
    --cc=faith.ekstrand@collabora.com \
    --cc=hanetzer@startmail.com \
    --cc=heiko@sntech.de \
    --cc=ishitatsuyuki@gmail.com \
    --cc=kernel@collabora.com \
    --cc=ketil.johnsen@arm.com \
    --cc=neil.armstrong@linaro.org \
    --cc=peron.clem@gmail.com \
    --cc=robh@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=steven.price@arm.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