dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Roberts <nroberts@igalia.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
	Rob Herring <robh+dt@kernel.org>,
	Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
	Steven Price <steven.price@arm.com>
Subject: Re: [PATCH] drm/shmem-helper: Don't remove the offset in vm_area_struct pgoff
Date: Tue, 23 Feb 2021 16:59:17 +0100	[thread overview]
Message-ID: <87im6idbca.fsf@yahoo.co.uk> (raw)
In-Reply-To: <CAKMK7uFs7z6fAXOntWwBNPBq26PBOkHJ09atv_cYeJCpk4FwjQ@mail.gmail.com>

Daniel Vetter <daniel@ffwll.ch> writes:

> drm_gem_shmem_fault() does not seem to check for purged objects at all.
>
> No idea how this works, or if it ever worked, but yeah something is
> clearly still busted.

Oh of course, the fault handler doesn’t check this. I’ve added a second
patch to make it check and posted it as a separate series here:

https://lists.freedesktop.org/archives/dri-devel/2021-February/298170.html

The two patches combined make the IGT test pass.

> Definitely a good idae to have an igt. btw to make that faster you can
> either use the vm_drop_caches file from proc (it's a bit a hammer), or
> what I recommend: Have a dedicated debugfs file to only drop
> everything from your shrinker. That's much quicker and  controlled.
> See e.g. ttm_tt_debugfs_shrink from d4bd7776a7ac ("drm/ttm: rework
> ttm_tt page limit v4") which recently landed in drm-misc-next.

I agree it would be great to have a debugfs option to trigger the purge.
I wonder if someone more involved in Panfrost would like to implement
this, because I am actually trying to work on VC4 and this is already
turning out to be quite a lot of yak shaving :) I’d also like to
implement the same debugfs option and IGT test for VC4.

Thanks for the feedback.

Regards,
- Neil
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2021-02-23 15:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-17 16:59 [PATCH] drm/shmem-helper: Don't remove the offset in vm_area_struct pgoff Neil Roberts
2021-02-17 19:33 ` kernel test robot
2021-02-18 15:26 ` Steven Price
2021-02-18 15:30   ` Daniel Vetter
2021-02-18 15:45     ` Alyssa Rosenzweig
2021-02-18 16:15       ` Steven Price
2021-02-18 16:38         ` Rob Herring
2021-02-18 16:52           ` Steven Price
2021-02-18 17:15             ` Rob Herring
2021-02-18 18:20               ` Daniel Vetter
2021-02-19 13:36                 ` Steven Price
2021-02-19 15:13                   ` Daniel Vetter
2021-02-19 16:18                     ` Steven Price
2021-02-19 17:45                       ` Daniel Vetter
2021-02-22  8:34                         ` Boris Brezillon
2021-02-22 16:20                           ` Daniel Vetter
2021-02-23 12:42     ` Neil Roberts
2021-02-23 12:54       ` Daniel Vetter
2021-02-23 15:59         ` Neil Roberts [this message]
2021-02-23 16:40           ` Daniel Vetter
2021-02-22 14:24 ` Thomas Zimmermann
2021-02-22 16:21   ` Daniel Vetter

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=87im6idbca.fsf@yahoo.co.uk \
    --to=nroberts@igalia.com \
    --cc=alyssa.rosenzweig@collabora.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=robh+dt@kernel.org \
    --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