From: Raag Jadav <raag.jadav@intel.com>
To: Nitin Gote <nitin.r.gote@intel.com>
Cc: intel-xe@lists.freedesktop.org,
Matthew Brost <matthew.brost@intel.com>,
Matthew Auld <matthew.auld@intel.com>
Subject: Re: [PATCH] drm/xe/pm: do not warn about missing runtime PM protection after hot-unplug
Date: Thu, 30 Jul 2026 07:59:13 +0200 [thread overview]
Message-ID: <amroMZ8MF0PrF8dh@black.igk.intel.com> (raw)
In-Reply-To: <20260730053635.1515929-2-nitin.r.gote@intel.com>
On Thu, Jul 30, 2026 at 11:06:36AM +0530, Nitin Gote wrote:
> After hot-unplug, device_del() disables runtime PM. A deferred fd close
> can still run later during process exit and destroy remaining exec queues,
> which may call xe_pm_runtime_get_noresume().
This sounds like could cause many other side effects. Why not make sure
the exec queues are taken care of as part of hot-unplug path?
Raag
next prev parent reply other threads:[~2026-07-30 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 5:36 [PATCH] drm/xe/pm: do not warn about missing runtime PM protection after hot-unplug Nitin Gote
2026-07-30 5:06 ` ✓ CI.KUnit: success for " Patchwork
2026-07-30 5:45 ` ✓ Xe.CI.BAT: " Patchwork
2026-07-30 5:59 ` Raag Jadav [this message]
2026-07-30 6:39 ` ✓ Xe.CI.FULL: " 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=amroMZ8MF0PrF8dh@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@intel.com \
--cc=nitin.r.gote@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