Quoting John Hubbard (2020-05-22 06:19:27) > The purpose of posting this series is to launch a test in the > intel-gfx-ci tree. (The patches have already been merged into Andrew's > linux-mm tree.) > > This applies to today's linux.git (note the base-commit tag at the > bottom). > > Changes since V1: > > * Fixed a bug in the refactoring patch: added FOLL_FAST_ONLY to the > list of gup_flags *not* to WARN() on. This lead to a failure in the > first intel-gfx-ci test run [1]. > > [1] https://lore.kernel.org/r/159008745422.32320.5724805750977048669@xxxxxxxxxxxxxxxxxxxxx Ran this through our CI, warn and subsequent lockup were gone. That lockup is worrying me now, but that doesn't seem to be an issue from this series. The i915 changes were simple enough, I would have computed the pin flags just once (since the readonly bit is static, that would be interesting if that was allowed to change mid gup :) Reviewed-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
