From: Jason Gunthorpe <jgg@ziepe.ca>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
intel-gfx@lists.freedesktop.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/2] mm/mmu_notifier: Mark up direct reclaim paths with MAYFAIL
Date: Wed, 24 Jun 2020 15:48:04 -0300 [thread overview]
Message-ID: <20200624184804.GL6578@ziepe.ca> (raw)
In-Reply-To: <159302152915.4527.9099070806700792078@build.alporthouse.com>
On Wed, Jun 24, 2020 at 06:58:49PM +0100, Chris Wilson wrote:
> > I'm still a little unclear on what you are trying to fix - pinned
> > pages are definitely not freed, do you have some case where pages
> > which are pinned are being cleaned out from the MM despite being
> > pinned? Sounds a bit strange, maybe that is worth adressing directly?
>
> It suffices to say that pin_user_pages does not prevent try_to_unmap_one
> from trying to revoke the page.
This doesn't sound right.. Maybe there are some odd ball cases, but in
common things like page out we absolutely cannot page out or discard
pages under DMA. This would be a significant bug.
What is the actual problem here?
Jason
prev parent reply other threads:[~2020-06-24 18:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 8:02 [PATCH 1/2] mm/mmu_notifier: Mark up direct reclaim paths with MAYFAIL Chris Wilson
2020-06-24 8:02 ` [PATCH 2/2] drm/i915/gem: Use mmu_notifier_range_mayfail() to avoid waiting inside reclaim Chris Wilson
2020-06-24 12:10 ` [PATCH 1/2] mm/mmu_notifier: Mark up direct reclaim paths with MAYFAIL Jason Gunthorpe
2020-06-24 12:21 ` Chris Wilson
2020-06-24 12:39 ` Jason Gunthorpe
2020-06-24 14:12 ` Chris Wilson
2020-06-24 14:16 ` Jason Gunthorpe
2020-06-24 14:21 ` Chris Wilson
2020-06-24 14:25 ` Jason Gunthorpe
2020-06-24 14:37 ` Chris Wilson
2020-06-24 16:50 ` Jason Gunthorpe
2020-06-24 17:58 ` Chris Wilson
2020-06-24 18:48 ` Jason Gunthorpe [this message]
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=20200624184804.GL6578@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).