From: John Hubbard <jhubbard@nvidia.com> To: Chris Wilson <chris@chris-wilson.co.uk>, Andrew Morton <akpm@linux-foundation.org> Cc: Souptick Joarder <jrdr.linux@gmail.com>, Matthew Wilcox <willy@infradead.org>, Jani Nikula <jani.nikula@linux.intel.com>, Joonas Lahtinen <joonas.lahtinen@linux.intel.com>, Rodrigo Vivi <rodrigo.vivi@intel.com>, David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>, Tvrtko Ursulin <tvrtko.ursulin@intel.com>, Matthew Auld <matthew.auld@intel.com>, <intel-gfx@lists.freedesktop.org>, <dri-devel@lists.freedesktop.org>, LKML <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org> Subject: Re: [PATCH v2 0/4] mm/gup, drm/i915: refactor gup_fast, convert to pin_user_pages() Date: Sat, 23 May 2020 15:33:47 -0700 [thread overview] Message-ID: <d87cdee8-aa0f-91ca-ea86-e89c4536458f@nvidia.com> (raw) In-Reply-To: <159022688563.11139.3402294435382936623@build.alporthouse.com> On 2020-05-23 02:41, Chris Wilson wrote: > 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@build.alporthouse.com > > Ran this through our CI, warn and subsequent lockup were gone. That DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1590273216; bh=oK85oUq4LCrgTs8kxvJryKE7a7GUQfAveFtGpNOU2dQ=; h=X-PGP-Universal:Subject:To:CC:References:From:X-Nvconfidentiality: Message-ID:Date:User-Agent:MIME-Version:In-Reply-To: X-Originating-IP:X-ClientProxiedBy:Content-Type:Content-Language: Content-Transfer-Encoding; b=QoI4eJbYYVxcoARKgFJdRrxzB/GBPqy5yKIF46/pjR75LEiZvvAX947VBwywSMYhx It8aQpMm6kMaF/rxiv0IPBf3tNGxNziWBAAhDXCyNqmvAS5s1HfdQh5ZoYbyDynKbJ uF+u9JjBOYo5uTnn3IUaGPRgl/p9k6OhwRhbJ9nYreDwIF1/1pPeo97jwP2jW7AtDf xDO5iJhGmwLYHPzRLilgiDdLbNhIGAP1XJ/4t/DByshidOUalduU7HxVQ9IOnysnCw QcqSlpyPgx5LkJOvs63gO8n28hHJnoJ4FggNXC3D311lBWRuD7iekdP5WuvmrxUb8N rZKwTpl0vJl9w== Yea! Thanks again for these test runs. I really don't like posting patches that I can't run-time test, but this CI system mitigates that pretty well. > lockup is worrying me now, but that doesn't seem to be an issue from > this series. I do think it's worth following up on. And it seems like it would be very easy to repro: just hack in a forced failure at the call site of pin_user_pages_fast_only(), and follow the breadcrumbs. > > 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@chris-wilson.co.uk> > -Chris > Thanks for the review! And if lifting that check up higher in the call stack is desired, I'm all in favor of that being done...in a separate patch. :) I'm trying to keep a very light touch when converting these call sites. thanks, -- John Hubbard NVIDIA
WARNING: multiple messages have this Message-ID
From: John Hubbard <jhubbard@nvidia.com> To: Chris Wilson <chris@chris-wilson.co.uk>, Andrew Morton <akpm@linux-foundation.org> Cc: Matthew Wilcox <willy@infradead.org>, dri-devel@lists.freedesktop.org, Tvrtko Ursulin <tvrtko.ursulin@intel.com>, David Airlie <airlied@linux.ie>, intel-gfx@lists.freedesktop.org, LKML <linux-kernel@vger.kernel.org>, linux-mm@kvack.org, Souptick Joarder <jrdr.linux@gmail.com>, Rodrigo Vivi <rodrigo.vivi@intel.com>, Matthew Auld <matthew.auld@intel.com> Subject: Re: [PATCH v2 0/4] mm/gup, drm/i915: refactor gup_fast, convert to pin_user_pages() Date: Sat, 23 May 2020 15:33:47 -0700 [thread overview] Message-ID: <d87cdee8-aa0f-91ca-ea86-e89c4536458f@nvidia.com> (raw) In-Reply-To: <159022688563.11139.3402294435382936623@build.alporthouse.com> On 2020-05-23 02:41, Chris Wilson wrote: > 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@build.alporthouse.com > > Ran this through our CI, warn and subsequent lockup were gone. That DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1590273216; bh=oK85oUq4LCrgTs8kxvJryKE7a7GUQfAveFtGpNOU2dQ=; h=X-PGP-Universal:Subject:To:CC:References:From:X-Nvconfidentiality: Message-ID:Date:User-Agent:MIME-Version:In-Reply-To: X-Originating-IP:X-ClientProxiedBy:Content-Type:Content-Language: Content-Transfer-Encoding; b=QoI4eJbYYVxcoARKgFJdRrxzB/GBPqy5yKIF46/pjR75LEiZvvAX947VBwywSMYhx It8aQpMm6kMaF/rxiv0IPBf3tNGxNziWBAAhDXCyNqmvAS5s1HfdQh5ZoYbyDynKbJ uF+u9JjBOYo5uTnn3IUaGPRgl/p9k6OhwRhbJ9nYreDwIF1/1pPeo97jwP2jW7AtDf xDO5iJhGmwLYHPzRLilgiDdLbNhIGAP1XJ/4t/DByshidOUalduU7HxVQ9IOnysnCw QcqSlpyPgx5LkJOvs63gO8n28hHJnoJ4FggNXC3D311lBWRuD7iekdP5WuvmrxUb8N rZKwTpl0vJl9w== Yea! Thanks again for these test runs. I really don't like posting patches that I can't run-time test, but this CI system mitigates that pretty well. > lockup is worrying me now, but that doesn't seem to be an issue from > this series. I do think it's worth following up on. And it seems like it would be very easy to repro: just hack in a forced failure at the call site of pin_user_pages_fast_only(), and follow the breadcrumbs. > > 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@chris-wilson.co.uk> > -Chris > Thanks for the review! And if lifting that check up higher in the call stack is desired, I'm all in favor of that being done...in a separate patch. :) I'm trying to keep a very light touch when converting these call sites. thanks, -- John Hubbard NVIDIA _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID
From: John Hubbard <jhubbard@nvidia.com> To: Chris Wilson <chris@chris-wilson.co.uk>, Andrew Morton <akpm@linux-foundation.org> Cc: Matthew Wilcox <willy@infradead.org>, dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>, intel-gfx@lists.freedesktop.org, LKML <linux-kernel@vger.kernel.org>, linux-mm@kvack.org, Souptick Joarder <jrdr.linux@gmail.com>, Matthew Auld <matthew.auld@intel.com> Subject: Re: [Intel-gfx] [PATCH v2 0/4] mm/gup, drm/i915: refactor gup_fast, convert to pin_user_pages() Date: Sat, 23 May 2020 15:33:47 -0700 [thread overview] Message-ID: <d87cdee8-aa0f-91ca-ea86-e89c4536458f@nvidia.com> (raw) In-Reply-To: <159022688563.11139.3402294435382936623@build.alporthouse.com> On 2020-05-23 02:41, Chris Wilson wrote: > 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@build.alporthouse.com > > Ran this through our CI, warn and subsequent lockup were gone. That DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1590273216; bh=oK85oUq4LCrgTs8kxvJryKE7a7GUQfAveFtGpNOU2dQ=; h=X-PGP-Universal:Subject:To:CC:References:From:X-Nvconfidentiality: Message-ID:Date:User-Agent:MIME-Version:In-Reply-To: X-Originating-IP:X-ClientProxiedBy:Content-Type:Content-Language: Content-Transfer-Encoding; b=QoI4eJbYYVxcoARKgFJdRrxzB/GBPqy5yKIF46/pjR75LEiZvvAX947VBwywSMYhx It8aQpMm6kMaF/rxiv0IPBf3tNGxNziWBAAhDXCyNqmvAS5s1HfdQh5ZoYbyDynKbJ uF+u9JjBOYo5uTnn3IUaGPRgl/p9k6OhwRhbJ9nYreDwIF1/1pPeo97jwP2jW7AtDf xDO5iJhGmwLYHPzRLilgiDdLbNhIGAP1XJ/4t/DByshidOUalduU7HxVQ9IOnysnCw QcqSlpyPgx5LkJOvs63gO8n28hHJnoJ4FggNXC3D311lBWRuD7iekdP5WuvmrxUb8N rZKwTpl0vJl9w== Yea! Thanks again for these test runs. I really don't like posting patches that I can't run-time test, but this CI system mitigates that pretty well. > lockup is worrying me now, but that doesn't seem to be an issue from > this series. I do think it's worth following up on. And it seems like it would be very easy to repro: just hack in a forced failure at the call site of pin_user_pages_fast_only(), and follow the breadcrumbs. > > 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@chris-wilson.co.uk> > -Chris > Thanks for the review! And if lifting that check up higher in the call stack is desired, I'm all in favor of that being done...in a separate patch. :) I'm trying to keep a very light touch when converting these call sites. thanks, -- John Hubbard NVIDIA _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-05-23 22:33 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-22 5:19 John Hubbard 2020-05-22 5:19 ` [Intel-gfx] " John Hubbard 2020-05-22 5:19 ` John Hubbard 2020-05-22 5:19 ` [PATCH v2 1/4] mm/gup: move __get_user_pages_fast() down a few lines in gup.c John Hubbard 2020-05-22 5:19 ` [Intel-gfx] " John Hubbard 2020-05-22 5:19 ` John Hubbard 2020-05-22 5:19 ` [PATCH v2 2/4] mm/gup: refactor and de-duplicate gup_fast() code John Hubbard 2020-05-22 5:19 ` [Intel-gfx] " John Hubbard 2020-05-22 5:19 ` John Hubbard 2020-05-22 5:19 ` [PATCH v2 3/4] mm/gup: introduce pin_user_pages_fast_only() John Hubbard 2020-05-22 5:19 ` [Intel-gfx] " John Hubbard 2020-05-22 5:19 ` John Hubbard 2020-05-22 5:19 ` [PATCH v2 4/4] drm/i915: convert get_user_pages() --> pin_user_pages() John Hubbard 2020-05-22 5:19 ` [Intel-gfx] " John Hubbard 2020-05-22 5:19 ` John Hubbard 2020-05-23 9:41 ` [PATCH v2 0/4] mm/gup, drm/i915: refactor gup_fast, convert to pin_user_pages() Chris Wilson 2020-05-23 9:41 ` [Intel-gfx] " Chris Wilson 2020-05-23 9:41 ` Chris Wilson 2020-05-23 22:33 ` John Hubbard [this message] 2020-05-23 22:33 ` [Intel-gfx] " John Hubbard 2020-05-23 22:33 ` John Hubbard 2020-05-23 18:35 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork 2020-05-23 18:37 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork 2020-05-23 20:34 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork 2020-05-23 21:35 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=d87cdee8-aa0f-91ca-ea86-e89c4536458f@nvidia.com \ --to=jhubbard@nvidia.com \ --cc=airlied@linux.ie \ --cc=akpm@linux-foundation.org \ --cc=chris@chris-wilson.co.uk \ --cc=daniel@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=intel-gfx@lists.freedesktop.org \ --cc=jani.nikula@linux.intel.com \ --cc=joonas.lahtinen@linux.intel.com \ --cc=jrdr.linux@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=matthew.auld@intel.com \ --cc=rodrigo.vivi@intel.com \ --cc=tvrtko.ursulin@intel.com \ --cc=willy@infradead.org \ --subject='Re: [PATCH v2 0/4] mm/gup, drm/i915: refactor gup_fast, convert to pin_user_pages()' \ /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
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.