From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: DRI Development <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [PATCH 0/4] mmu notifier debug checks v2
Date: Mon, 10 Dec 2018 11:36:37 +0100 [thread overview]
Message-ID: <20181210103641.31259-1-daniel.vetter@ffwll.ch> (raw)
Hi all,
Here's v2 of my mmu notifier debug checks.
I think the last two patches could probably be extended to all callbacks,
but I'm not really clear on the exact rules. But happy to extend them if
there's interest.
This stuff helps us catch issues in the i915 mmu notifier implementation.
Thanks, Daniel
Daniel Vetter (4):
mm: Check if mmu notifier callbacks are allowed to fail
kernel.h: Add non_block_start/end()
mm, notifier: Catch sleeping/blocking for !blockable
mm, notifier: Add a lockdep map for invalidate_range_start
include/linux/kernel.h | 10 +++++++++-
include/linux/mmu_notifier.h | 6 ++++++
include/linux/sched.h | 4 ++++
kernel/sched/core.c | 6 +++---
mm/mmu_notifier.c | 18 +++++++++++++++++-
5 files changed, 39 insertions(+), 5 deletions(-)
--
2.20.0.rc1
next reply other threads:[~2018-12-10 10:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 10:36 Daniel Vetter [this message]
2018-12-10 10:36 ` [PATCH 1/4] mm: Check if mmu notifier callbacks are allowed to fail Daniel Vetter
2018-12-10 10:36 ` Daniel Vetter
2018-12-10 10:44 ` Koenig, Christian
2018-12-10 10:44 ` Koenig, Christian
2018-12-10 13:27 ` Michal Hocko
2018-12-10 13:27 ` Michal Hocko
2018-12-10 10:36 ` [PATCH 2/4] kernel.h: Add non_block_start/end() Daniel Vetter
2018-12-10 10:36 ` Daniel Vetter
2018-12-10 14:13 ` Michal Hocko
2018-12-10 14:13 ` Michal Hocko
2018-12-10 14:47 ` Peter Zijlstra
2018-12-10 14:47 ` Peter Zijlstra
2018-12-10 15:01 ` Michal Hocko
2018-12-10 15:22 ` Peter Zijlstra
2018-12-10 16:20 ` Michal Hocko
2018-12-10 16:30 ` Peter Zijlstra
2018-12-10 16:30 ` Peter Zijlstra
2018-12-12 10:26 ` Daniel Vetter
2018-12-12 10:26 ` Daniel Vetter
2018-12-10 10:36 ` [PATCH 3/4] mm, notifier: Catch sleeping/blocking for !blockable Daniel Vetter
2018-12-10 10:36 ` [PATCH 4/4] mm, notifier: Add a lockdep map for invalidate_range_start Daniel Vetter
2018-12-10 12:07 ` ✗ Fi.CI.CHECKPATCH: warning for mmu notifier debug checks v2 Patchwork
2018-12-10 12:28 ` ✓ Fi.CI.BAT: success " Patchwork
2018-12-10 15:54 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-12-10 16:47 ` ✗ Fi.CI.BAT: failure for mmu notifier debug checks v2 (rev2) 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=20181210103641.31259-1-daniel.vetter@ffwll.ch \
--to=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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.