Re: [Intel-gfx] [PATCH 3/3] mm, notifier: Add a lockdep map for invalidate_range_start

2018-11-27 Thread Daniel Vetter
On Tue, Nov 27, 2018 at 05:33:58PM +, Chris Wilson wrote: > Quoting Daniel Vetter (2018-11-27 17:28:43) > > On Tue, Nov 27, 2018 at 5:50 PM Chris Wilson > > wrote: > > > > > > Quoting Daniel Vetter (2018-11-27 07:49:18) > > > > On Thu, Nov 22, 2018 at 05:51:06PM +0100, Daniel Vetter wrote: >

Re: [Intel-gfx] [PATCH 3/3] mm, notifier: Add a lockdep map for invalidate_range_start

2018-11-27 Thread Chris Wilson
Quoting Daniel Vetter (2018-11-27 17:28:43) > On Tue, Nov 27, 2018 at 5:50 PM Chris Wilson wrote: > > > > Quoting Daniel Vetter (2018-11-27 07:49:18) > > > On Thu, Nov 22, 2018 at 05:51:06PM +0100, Daniel Vetter wrote: > > > > This is a similar idea to the fs_reclaim fake lockdep lock. It's > > >

Re: [Intel-gfx] [PATCH 3/3] mm, notifier: Add a lockdep map for invalidate_range_start

2018-11-27 Thread Daniel Vetter
On Tue, Nov 27, 2018 at 5:50 PM Chris Wilson wrote: > > Quoting Daniel Vetter (2018-11-27 07:49:18) > > On Thu, Nov 22, 2018 at 05:51:06PM +0100, Daniel Vetter wrote: > > > This is a similar idea to the fs_reclaim fake lockdep lock. It's > > > fairly easy to provoke a specific notifier to be run

Re: [Intel-gfx] [PATCH 3/3] mm, notifier: Add a lockdep map for invalidate_range_start

2018-11-27 Thread Chris Wilson
Quoting Daniel Vetter (2018-11-27 07:49:18) > On Thu, Nov 22, 2018 at 05:51:06PM +0100, Daniel Vetter wrote: > > This is a similar idea to the fs_reclaim fake lockdep lock. It's > > fairly easy to provoke a specific notifier to be run on a specific > > range: Just prep it, and then munmap() it. >