public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Re: [PATCH v2] drm/i915: Setting/clearing the memory access bit when en/disabling i915
       [not found] <20251007202514.1661491-1-jia.yao@intel.com>
@ 2025-10-09  1:10 ` Askar Safin
  0 siblings, 0 replies; only message in thread
From: Askar Safin @ 2025-10-09  1:10 UTC (permalink / raw)
  To: jia.yao
  Cc: alex.zuo, chris.p.wilson, intel-gfx, piliu, linux-kernel,
	shuicheng.lin

[It seems this letter got lost, so I'm sending it again, this time using git-send-email.
Please, CC lkml additionally next time, hopefully it will work better than intel-gfx@freedesktop ]

On Tue, Oct 7, 2025 at 11:25 PM Jia Yao <jia.yao@intel.com> wrote:
> Make i915's PCI device management more robust by always setting/clearing

Thank you! I tested this patch, and it indeed fixes the problem. You may add:

Tested-By: Askar Safin <safinaskar@gmail.com>

Please, CC me with further patches, I will test them.

Also, I will repeat that the bug doesn't happen if we have
CONFIG_INTEL_IOMMU_DEFAULT_ON=y.
So, probably we just need to patch all distro's configs to include
CONFIG_INTEL_IOMMU_DEFAULT_ON=y
(Ubuntu already does that.)
On the other hand, if there is some deeper issue to fix, then, of
course, I'm glad it is being fixed!

Also, please, add some "Fixes" tag and CC stable to make sure this fix
will be backported to stable kernels.

For example:

  Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
  Cc: <stable@vger.kernel.org>

Here I chose the initial git commit, because i915 always was in git history.

-- 
Askar Safin

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2025-10-09  1:10 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20251007202514.1661491-1-jia.yao@intel.com>
2025-10-09  1:10 ` [PATCH v2] drm/i915: Setting/clearing the memory access bit when en/disabling i915 Askar Safin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox