From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/xe: handle pinned memory in PM notifier
Date: Wed, 16 Apr 2025 14:19:17 +0200 [thread overview]
Message-ID: <0f48e3d3562d1f22d4d353a2ac6ee2de091f2382.camel@linux.intel.com> (raw)
In-Reply-To: <255d999f-1411-4a33-9934-04894f1690ed@intel.com>
On Tue, 2025-04-15 at 11:27 +0100, Matthew Auld wrote:
> > > @@ -1120,13 +1192,16 @@ int xe_bo_evict_pinned(struct xe_bo *bo)
> > > if (bo->flags & XE_BO_FLAG_PINNED_NORESTORE)
> > > goto out_unlock_bo
> >
> > Should we drop the pinning of the backup object at this point,
> > thinking
> > that on memory pressure we might want to shrink it. Or perhaps
> > reclaim
> > is already turned off at this point?
>
> Yeah, __GFP_IO | __GFP_FS are both restricted here, so I guess we
> can't
> really shrink stuff at this point?
Indeed we can't shrink without those.
/Thomas
next prev parent reply other threads:[~2025-04-20 14:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 16:20 [PATCH 0/3] PM notifier Matthew Auld
2025-04-10 16:20 ` [PATCH 1/3] drm/xe: evict user memory in " Matthew Auld
2025-04-11 15:05 ` Thomas Hellström
2025-04-10 16:20 ` [PATCH 2/3] drm/xe: share bo dma-resv with backup object Matthew Auld
2025-04-11 15:12 ` Thomas Hellström
2025-04-14 10:32 ` Matthew Auld
2025-04-15 9:19 ` Thomas Hellström
2025-04-10 16:20 ` [PATCH 3/3] drm/xe: handle pinned memory in PM notifier Matthew Auld
2025-04-15 9:57 ` Thomas Hellström
2025-04-15 10:27 ` Matthew Auld
2025-04-16 12:19 ` Thomas Hellström [this message]
2025-04-10 16:58 ` ✓ CI.Patch_applied: success for " Patchwork
2025-04-10 16:58 ` ✓ CI.checkpatch: " Patchwork
2025-04-10 16:59 ` ✓ CI.KUnit: " Patchwork
2025-04-10 17:08 ` ✓ CI.Build: " Patchwork
2025-04-10 17:10 ` ✓ CI.Hooks: " Patchwork
2025-04-10 17:11 ` ✓ CI.checksparse: " Patchwork
2025-04-10 17:57 ` ✓ Xe.CI.BAT: " Patchwork
2025-04-10 21:48 ` ✗ Xe.CI.Full: 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=0f48e3d3562d1f22d4d353a2ac6ee2de091f2382.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
/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