✓ CI.checkpatch: success for drm/xe/vf: Post-migration recovery, remove MMIO assert
Patchwork
patchwork at emeril.freedesktop.org
Thu Nov 7 15:20:17 UTC 2024
== Series Details ==
Series: drm/xe/vf: Post-migration recovery, remove MMIO assert
URL : https://patchwork.freedesktop.org/series/141058/
State : success
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit da9d73312174d868b163e768dd9c8e50c3fdb2f8
Author: Tomasz Lis <tomasz.lis at intel.com>
Date: Thu Nov 7 16:13:57 2024 +0100
drm/xe/guc: Do not assert CTB state while sending MMIO
During VF post-migration recovery, MMIO communication channel to GuC
is used, despite CTB channel being enabled. This behavior is rooted
in the save-restore architecture specification.
Therefore, a VF driver cannot assert that CTB is disabled while sending
MMIO messages to GuC. Such assertion needs to be PF only, or be removed.
This patch simply removes the assertion.
Signed-off-by: Tomasz Lis <tomasz.lis at intel.com>
Suggested-by: Michał Wajdeczko <michal.wajdeczko at intel.com>
+ /mt/dim checkpatch ac4e52a591ed566ed065b0abdb6b2cce5f9b3afa drm-intel
da9d73312174 drm/xe/guc: Do not assert CTB state while sending MMIO
More information about the Intel-xe
mailing list