public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Askar Safin <safinaskar@gmail.com>
To: jia.yao@intel.com
Cc: alex.zuo@intel.com, chris.p.wilson@linux.intel.com,
	intel-gfx@lists.freedesktop.org, piliu@redhat.com,
	linux-kernel@vger.kernel.org, shuicheng.lin@intel.com
Subject: Re: [PATCH v2] drm/i915: Setting/clearing the memory access bit when en/disabling i915
Date: Thu,  9 Oct 2025 04:10:00 +0300	[thread overview]
Message-ID: <20251009011010.37763-1-safinaskar@gmail.com> (raw)
In-Reply-To: <20251007202514.1661491-1-jia.yao@intel.com>

[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

  parent reply	other threads:[~2025-10-09  9:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07 18:06 [PATCH] drm/i915: Setting/clearing the memory access bit when enabling/disabling i915 Jia Yao
2025-10-07 20:25 ` [PATCH v2] drm/i915: Setting/clearing the memory access bit when en/disabling i915 Jia Yao
2025-10-07 21:25   ` Ville Syrjälä
2025-10-07 21:40     ` Yao, Jia
2025-10-08 12:21       ` Ville Syrjälä
2025-10-08 16:06         ` Yao, Jia
2025-10-08 16:15           ` Ville Syrjälä
2025-10-08 17:14             ` Yao, Jia
2025-10-09  1:55               ` Pingfan Liu
2025-10-11 12:35             ` Askar Safin
2025-10-11 12:49             ` Askar Safin
2025-10-13 16:16               ` Yao, Jia
2025-10-14  6:29               ` Pingfan Liu
2025-11-01 16:02                 ` Askar Safin
2025-10-08  5:17   ` Pingfan Liu
2025-10-08  7:05     ` Yao, Jia
2025-10-08 10:58       ` Pingfan Liu
2025-10-08  8:50   ` Askar Safin
2025-10-09  1:10   ` Askar Safin [this message]
2025-10-08  4:06 ` ✓ i915.CI.BAT: success for drm/i915: Setting/clearing the memory access bit when enabling/disabling i915 Patchwork
2025-10-08  4:29 ` ✓ i915.CI.BAT: success for drm/i915: Setting/clearing the memory access bit when enabling/disabling i915 (rev2) Patchwork
2026-01-20  4:42 ` [PATCH v3] drm/i915: Clearing the Memory Space Enable bit when disabling i915 Jia Yao
2026-01-20  9:50   ` Jani Nikula
2026-01-21 21:51     ` Yao, Jia
2026-01-20 16:11   ` Ville Syrjälä
2026-01-21  7:19     ` Yao, Jia
2026-01-21 15:02       ` Ville Syrjälä
2026-01-22  6:43         ` Yao, Jia
2026-01-20  5:31 ` ✗ i915.CI.BAT: failure for drm/i915: Setting/clearing the memory access bit when enabling/disabling i915 (rev3) 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=20251009011010.37763-1-safinaskar@gmail.com \
    --to=safinaskar@gmail.com \
    --cc=alex.zuo@intel.com \
    --cc=chris.p.wilson@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jia.yao@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piliu@redhat.com \
    --cc=shuicheng.lin@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