From: Jason Gunthorpe <jgg@ziepe.ca>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/5] mmu notifer debug annotations
Date: Tue, 27 Aug 2019 20:04:43 -0300 [thread overview]
Message-ID: <20190827230443.GA28580@ziepe.ca> (raw)
In-Reply-To: <20190826201425.17547-1-daniel.vetter@ffwll.ch>
On Mon, Aug 26, 2019 at 10:14:20PM +0200, Daniel Vetter wrote:
> Hi all,
>
> Next round. Changes:
>
> - I kept the two lockdep annotations patches since when I rebased this
> before retesting linux-next didn't yet have them. Otherwise unchanged
> except for a trivial conflict.
>
> - Ack from Peter Z. on the kernel.h patch.
>
> - Added annotations for non_block to invalidate_range_end. I can't test
> that readily since i915 doesn't use it.
>
> - Added might_sleep annotations to also make sure the mm side keeps up
> it's side of the contract here around what's allowed and what's not.
>
> Comments, feedback, review as usual very much appreciated.
>
>
> Daniel Vetter (5):
> mm, notifier: Add a lockdep map for invalidate_range_start/end
> mm, notifier: Prime lockdep
> mm, notifier: annotate with might_sleep()
I took these ones to hmm.git as they have a small conflict with hmm's
changes.
> kernel.h: Add non_block_start/end()
> mm, notifier: Catch sleeping/blocking for !blockable
Lets see about the checkpatch warning and review on these two please
Thanks,
Jason
next prev parent reply other threads:[~2019-08-27 23:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 20:14 Daniel Vetter
2019-08-26 20:14 ` [PATCH 1/5] mm, notifier: Add a lockdep map for invalidate_range_start/end Daniel Vetter
2019-08-26 20:14 ` [PATCH 2/5] mm, notifier: Prime lockdep Daniel Vetter
2019-08-26 20:14 ` [PATCH 3/5] kernel.h: Add non_block_start/end() Daniel Vetter
2019-08-27 22:50 ` Jason Gunthorpe
2019-08-28 18:33 ` Daniel Vetter
2019-08-28 18:43 ` Jason Gunthorpe
2019-08-28 18:56 ` Daniel Vetter
2019-09-03 7:28 ` Daniel Vetter
2019-09-03 7:36 ` Jason Gunthorpe
2019-08-28 11:43 ` Michal Hocko
2019-08-26 20:14 ` [PATCH 4/5] mm, notifier: Catch sleeping/blocking for !blockable Daniel Vetter
2019-08-26 20:14 ` [PATCH 5/5] mm, notifier: annotate with might_sleep() Daniel Vetter
2019-08-27 23:04 ` Jason Gunthorpe [this message]
2019-09-05 14:49 ` [PATCH 0/5] mmu notifer debug annotations Jason Gunthorpe
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=20190827230443.GA28580@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@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