From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Linux MM <linux-mm@kvack.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [PATCH 0/4] mmu notifier debug annotations/checks
Date: Tue, 20 Aug 2019 10:18:58 +0200 [thread overview]
Message-ID: <20190820081902.24815-1-daniel.vetter@ffwll.ch> (raw)
Hi all,
Here's the respin. Changes:
- 2 patches for checking return values of callbacks dropped, they landed
- move the lockdep annotations ahead, since I think that part is less
contentious. lockdep map now also annotates invalidate_range_end, as
requested by Jason.
- add a patch to prime lockdep, idea from Jason, let's hear whether the
implementation fits.
- I've stuck with the non_block_start/end for now and not switched back to
preempt_disable/enable, but with comments as suggested by Andrew.
Hopefully that fits the bill, otherwise I can go back again if the
consensus is more there.
Review, comments and ideas very much welcome.
Cheers, Daniel
Daniel Vetter (4):
mm, notifier: Add a lockdep map for invalidate_range_start/end
mm, notifier: Prime lockdep
kernel.h: Add non_block_start/end()
mm, notifier: Catch sleeping/blocking for !blockable
include/linux/kernel.h | 25 ++++++++++++++++++++++++-
include/linux/mmu_notifier.h | 8 ++++++++
include/linux/sched.h | 4 ++++
kernel/sched/core.c | 19 ++++++++++++++-----
mm/mmu_notifier.c | 24 +++++++++++++++++++++++-
5 files changed, 73 insertions(+), 7 deletions(-)
--
2.23.0.rc1
next reply other threads:[~2019-08-20 8:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 8:18 Daniel Vetter [this message]
2019-08-20 8:18 ` [PATCH 1/4] mm, notifier: Add a lockdep map for invalidate_range_start/end Daniel Vetter
2019-08-20 13:31 ` Jason Gunthorpe
2019-08-20 8:19 ` [PATCH 2/4] mm, notifier: Prime lockdep Daniel Vetter
2019-08-20 13:31 ` Jason Gunthorpe
2019-08-20 8:19 ` [PATCH 3/4] kernel.h: Add non_block_start/end() Daniel Vetter
2019-08-20 20:24 ` Daniel Vetter
2019-08-22 23:14 ` Andrew Morton
2019-08-23 8:34 ` Daniel Vetter
2019-08-23 12:12 ` Jason Gunthorpe
2019-08-23 12:22 ` Peter Zijlstra
2019-08-23 13:42 ` Daniel Vetter
2019-08-23 14:06 ` Peter Zijlstra
2019-08-23 15:15 ` Daniel Vetter
2019-08-23 8:48 ` Peter Zijlstra
2019-08-20 8:19 ` [PATCH 4/4] mm, notifier: Catch sleeping/blocking for !blockable Daniel Vetter
2019-08-20 13:34 ` Jason Gunthorpe
2019-08-20 15:18 ` Daniel Vetter
2019-08-20 15:27 ` Jason Gunthorpe
2019-08-21 9:34 ` Daniel Vetter
2019-08-21 15:41 ` Daniel Vetter
2019-08-21 16:16 ` Jason Gunthorpe
2019-08-22 8:42 ` Daniel Vetter
2019-08-22 14:24 ` Jason Gunthorpe
2019-08-22 14:27 ` 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=20190820081902.24815-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox