iommu/vt-d: Disable igfx iommu superpage on bxt/skl/glk
Subsystems (5)
cover iommu/vt-d: Disable igfx iommu superpage on bxt/skl/glk
From: Ville Syrjälä <[email protected]>
I ran into some kind of fail with VT-d superpage on Geminlake igfx, so without any better ideas let's just disable it.
Additionally Skylake/Broxton igfx have known issues with VT-d superpage as well, so let's disable it there as well. This should let us re-enable frame buffer compression (FBC) for some extra power savings when the display is on.
Ville Syrjälä (4):
iommu/vt-d: Disable superpage for Geminilake igfx iommu/vt-d: Disable superpage for Broxton igfx iommu/vt-d: Disable superpage for Skylake igfx drm/i915/fbc: Allow FBC + VT-d on SKL/BXT
drivers/gpu/drm/i915/display/intel_fbc.c | 16 --------- drivers/iommu/intel/iommu.c | 44 ++++++++++++++++++++++++ 2 files changed, 44 insertions(+), 16 deletions(-)
Signature · 6 lines
2.31.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 1/4 iommu/vt-d: Disable superpage for Geminilake igfx
From: Ville Syrjälä <[email protected]>
While running "gem_exec_big --r single" from igt-gpu-tools on Geminilake as soon as a 2M mapping is made I tend to get a DMAR write fault. Strangely the faulting address is always a 4K page and usually very far away from the 2M page that got mapped. But if no 2M mappings get used I can't reproduce the fault.
I also tried to dump the PTE for the faulting address but it actually
looks correct to me (ie. definitely seems to have the write bit set):
DMAR: DRHD: handling fault status reg 2
DMAR: [DMA Write] Request device [00:02.0] PASID ffffffff fault addr 7fa8a78000 [fault reason 05] PTE Write access is not set
DMAR: fault 7fa8a78000 (level=1) PTE = 149efc003
So not really sure what's going on and this might just be full on duct tape, but it seems to work here. The machine has now survived a whole day running that test whereas with superpage enabled it fails in less than a minute usually.
TODO: might be nice to disable superpage only for the igfx iommu
instead of both iommus
TODO: would be nice to use the macros from include/drm/i915_pciids.h,
but can't do that with DECLARE_PCI_FIXUP_HEADER()
--- drivers/iommu/intel/iommu.c | 10 ++++++++++ 1 file changed, 10 insertions(+)
drivers/iommu/intel/iommu.c +10 -0
@@ -5617,6 +5617,16 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x1632, quirk_iommu_igfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x163A , quirk_iommu_igfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x163D , quirk_iommu_igfx); +static void quirk_iommu_nosp (struct pci_dev *dev) +{ +pci_info (dev,"Disabling IOMMU superpage for graphics on this chipset\n" ); + intel_iommu_superpage =0 ; +} + +/* Geminilake igfx appears to have issues with superpage */ +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x3184 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x3185 , quirk_iommu_nosp); +static void quirk_iommu_rwbf (struct pci_dev *dev) {if (risky_device (dev))
Signature · 6 lines
2.31.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Lu Baolu
maintainerRe: [Intel-gfx] [PATCH 1/4] iommu/vt-d: Disable superpage for Geminilake igfx
Quoted 14 lines · Ville Syrjala
From: Ville Syrjälä <[email protected]>
While running "
gem_exec_big--r single" from igt-gpu-tools on Geminilake as soon as a 2M mapping is made I tend to get a DMAR write fault. Strangely the faulting address is always a 4K page and usually very far away from the 2M page that got mapped. But if no 2M mappings get used I can't reproduce the fault.I also tried to dump the PTE for the faulting address but it actually
looks correct to me (ie. definitely seems to have the write bit set):
DMAR: DRHD: handling fault status reg 2
DMAR: [DMA Write] Request device [00:02.0] PASID ffffffff fault addr7fa8a78000[fault reason 05] PTE Write access is not set
DMAR: fault7fa8a78000(level=1) PTE =149efc003
Quoted 7 lines
So not really sure what's going on and this might just be full on duct tape, but it seems to work here. The machine has now survived a whole day running that test whereas with superpage enabled it fails in less than a minute usually.
TODO: might be nice to disable superpage only for the igfx iommu
instead of both iommus
If all these quirks are about igfx dedicated iommu's, I would suggest to disable superpage only for the igfx ones.
Best regards,
baolu
Quoted 23 lines
TODO: would be nice to use the macros from
include/drm/i915_pciids.h,
but can't do that withDECLARE_PCI_FIXUP_HEADER()Cc David Woodhouse <[email protected]>Cc Lu Baolu <[email protected]>Signed-off-by Ville Syrjälä <[email protected]>--- drivers/iommu/intel/iommu.c | 10 ++++++++++ 1 file changed, 10 insertions(+)drivers/iommu/intel/iommu.c +3
-0@@ -5617,6 +5617,16 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x1632, quirk_iommu_igfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x163A , quirk_iommu_igfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x163D , quirk_iommu_igfx); +static void quirk_iommu_nosp (struct pci_dev *dev) +{ +pci_info (dev,"Disabling IOMMU superpage for graphics on this chipset\n" );
drivers/iommu/intel/iommu.c DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x1632, quirk_iommu_igfx); · line 5632
Quoted 10 lines
drivers/iommu/intel/iommu.c +7
-0+ intel_iommu_superpage =0 ; +} + +/* Geminilake igfx appears to have issues with superpage */ +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x3184 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x3185 , quirk_iommu_nosp); +static void quirk_iommu_rwbf (struct pci_dev *dev) {if (risky_device (dev))
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH 1/4] iommu/vt-d: Disable superpage for Geminilake igfx
Quoted 20 lines · Lu Baolu
Quoted 19 lines · Ville Syrjala
From: Ville Syrjälä <[email protected]>
While running "
gem_exec_big--r single" from igt-gpu-tools on Geminilake as soon as a 2M mapping is made I tend to get a DMAR write fault. Strangely the faulting address is always a 4K page and usually very far away from the 2M page that got mapped. But if no 2M mappings get used I can't reproduce the fault.I also tried to dump the PTE for the faulting address but it actually
looks correct to me (ie. definitely seems to have the write bit set):
DMAR: DRHD: handling fault status reg 2
DMAR: [DMA Write] Request device [00:02.0] PASID ffffffff fault addr7fa8a78000[fault reason 05] PTE Write access is not set
DMAR: fault7fa8a78000(level=1) PTE =149efc003So not really sure what's going on and this might just be full on duct tape, but it seems to work here. The machine has now survived a whole day running that test whereas with superpage enabled it fails in less than a minute usually.
Quoted 5 lines
Quoted 2 lines
TODO: might be nice to disable superpage only for the igfx iommu
instead of both iommusIf all these quirks are about igfx dedicated iommu's, I would suggest to disable superpage only for the igfx ones.
Sure. Unfortunately there's no convenient mechanism to do that in the iommu driver that I can immediately see. So not something I can just whip up easily. Since you're actually familiar with the driver maybe you can come up with a decent solution for that?
Quoted 37 lines
Best regards,
baoluQuoted 33 lines
TODO: would be nice to use the macros from
include/drm/i915_pciids.h,
but can't do that withDECLARE_PCI_FIXUP_HEADER()Cc David Woodhouse <[email protected]>Cc Lu Baolu <[email protected]>Signed-off-by Ville Syrjälä <[email protected]>--- drivers/iommu/intel/iommu.c | 10 ++++++++++ 1 file changed, 10 insertions(+)drivers/iommu/intel/iommu.c +10
-0@@ -5617,6 +5617,16 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x1632, quirk_iommu_igfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x163A , quirk_iommu_igfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x163D , quirk_iommu_igfx); +static void quirk_iommu_nosp (struct pci_dev *dev) +{ +pci_info (dev,"Disabling IOMMU superpage for graphics on this chipset\n" ); + intel_iommu_superpage =0 ; +} + +/* Geminilake igfx appears to have issues with superpage */ +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x3184 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x3185 , quirk_iommu_nosp); +static void quirk_iommu_rwbf (struct pci_dev *dev) {if (risky_device (dev))
Signature · 6 lines
Ville Syrjälä Intel _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Lu Baolu
maintainerRe: [Intel-gfx] [PATCH 1/4] iommu/vt-d: Disable superpage for Geminilake igfx
Quoted 21 lines · Ville Syrjälä
Quoted 20 lines · Lu Baolu
Quoted 19 lines · Ville Syrjala
From: Ville Syrjälä<[email protected]>
While running "
gem_exec_big--r single" from igt-gpu-tools on Geminilake as soon as a 2M mapping is made I tend to get a DMAR write fault. Strangely the faulting address is always a 4K page and usually very far away from the 2M page that got mapped. But if no 2M mappings get used I can't reproduce the fault.I also tried to dump the PTE for the faulting address but it actually
looks correct to me (ie. definitely seems to have the write bit set):
DMAR: DRHD: handling fault status reg 2
DMAR: [DMA Write] Request device [00:02.0] PASID ffffffff fault addr7fa8a78000[fault reason 05] PTE Write access is not set
DMAR: fault7fa8a78000(level=1) PTE =149efc003So not really sure what's going on and this might just be full on duct tape, but it seems to work here. The machine has now survived a whole day running that test whereas with superpage enabled it fails in less than a minute usually.
Quoted 9 lines
Quoted 4 lines
Quoted 2 lines
TODO: might be nice to disable superpage only for the igfx iommu
instead of both iommusIf all these quirks are about igfx dedicated iommu's, I would suggest to disable superpage only for the igfx ones.
Sure. Unfortunately there's no convenient mechanism to do that in the iommu driver that I can immediately see. So not something I can just whip up easily. Since you're actually familiar with the driver maybe you can come up with a decent solution for that?
How about something like below? [no compile, no test...]
drivers/iommu/intel/iommu.c +31 -1
@@ -338,6 +338,7 @@ static int intel_iommu_strict;static int intel_iommu_superpage =1 ;static int iommu_identity_mapping;static int iommu_skip_te_disable; +static int iommu_skip_igfx_superpage;#define IDENTMAP_GFX 2#define IDENTMAP_AZALIA 4
@@ -652,6 +653,27 @@ static bool domain_update_iommu_snooping(struct intel_iommu *skip)return ret; } +static bool domain_use_super_page (struct dmar_domain *domain) +{ +struct dmar_drhd_unit *drhd; +struct intel_iommu *iommu; +bool ret = true; + +if (!intel_iommu_superpage) +return false; + +rcu_read_lock (); +for_each_active_iommu (iommu, drhd) { +if (drhd->gfx_dedicated && iommu_skip_igfx_superpage) { + ret = false; + break + } + } +rcu_read_unlock (); + +return ret; +} +static int domain_update_iommu_superpage (struct dmar_domain *domain,struct intel_iommu *skip) {
@@ -659,7 +681,7 @@ static int domain_update_iommu_superpage(struct dmar_domain *domain,struct intel_iommu *iommu;int mask =0x3 ; -if (!intel_iommu_superpage) +if (!domain_use_super_page (domain))return 0 ;/* set iommu_superpage to the smallest common denominator */
@@ -5656,6 +5678,14 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x1632, quirk_iommu_igfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x163A , quirk_iommu_igfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x163D , quirk_iommu_igfx); +static void quirk_skip_igfx_superpage (struct pci_dev *dev) +{ +pci_info (dev,"Disabling IOMMU superpage for graphics on this chipset\n" ); + iommu_skip_igfx_superpage =1 ; +} + +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x3184 , quirk_skip_igfx_superpage); +static void quirk_iommu_rwbf (struct pci_dev *dev) {if (risky_device (dev))
Best regards,
baolu
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH 1/4] iommu/vt-d: Disable superpage for Geminilake igfx
Quoted 55 lines · Lu Baolu
Quoted 21 lines · Ville Syrjälä
Quoted 20 lines · Lu Baolu
Quoted 19 lines · Ville Syrjala
From: Ville Syrjälä<[email protected]>
While running "
gem_exec_big--r single" from igt-gpu-tools on Geminilake as soon as a 2M mapping is made I tend to get a DMAR write fault. Strangely the faulting address is always a 4K page and usually very far away from the 2M page that got mapped. But if no 2M mappings get used I can't reproduce the fault.I also tried to dump the PTE for the faulting address but it actually
looks correct to me (ie. definitely seems to have the write bit set):
DMAR: DRHD: handling fault status reg 2
DMAR: [DMA Write] Request device [00:02.0] PASID ffffffff fault addr7fa8a78000[fault reason 05] PTE Write access is not set
DMAR: fault7fa8a78000(level=1) PTE =149efc003So not really sure what's going on and this might just be full on duct tape, but it seems to work here. The machine has now survived a whole day running that test whereas with superpage enabled it fails in less than a minute usually.
Quoted 9 lines
Quoted 4 lines
Quoted 2 lines
TODO: might be nice to disable superpage only for the igfx iommu
instead of both iommusIf all these quirks are about igfx dedicated iommu's, I would suggest to disable superpage only for the igfx ones.
Sure. Unfortunately there's no convenient mechanism to do that in the iommu driver that I can immediately see. So not something I can just whip up easily. Since you're actually familiar with the driver maybe you can come up with a decent solution for that?
How about something like below? [no compile, no test...]
drivers/iommu/intel/iommu.c +5
-0@@ -338,6 +338,7 @@ static int intel_iommu_strict;static int intel_iommu_superpage =1 ;static int iommu_identity_mapping;static int iommu_skip_te_disable; +static int iommu_skip_igfx_superpage;#define IDENTMAP_GFX 2#define IDENTMAP_AZALIA 4@@ -652,6 +653,27 @@ static bool domain_update_iommu_snooping(struct intel_iommu *skip)return ret; } +static bool domain_use_super_page (struct dmar_domain *domain) +{ +struct dmar_drhd_unit *drhd; +struct intel_iommu *iommu;
drivers/iommu/intel/iommu.c static bool domain_update_iommu_snooping(struct · line 670
Quoted 10 lines
drivers/iommu/intel/iommu.c +10
-0+bool ret = true; + +if (!intel_iommu_superpage) +return false; + +rcu_read_lock (); +for_each_active_iommu (iommu, drhd) { +if (drhd->gfx_dedicated && iommu_skip_igfx_superpage) { + ret = false; +break
^
Missing semicolon. Othwerwise seems to work great here. Thanks.
Are you going to turn this into a proper patch, or do you want me to just squash this into my patches and repost?
Quoted 40 lines
drivers/iommu/intel/iommu.c +7
-0+ } + } +rcu_read_unlock (); + +return ret; +} +static int domain_update_iommu_superpage (struct dmar_domain *domain,struct intel_iommu *skip){drivers/iommu/intel/iommu.c +1
-1@@ -659,7 +681,7 @@ static int domain_update_iommu_superpage(structdmar_domain *domain, struct intel_iommu *iommu;int mask =0x3 ; -if (!intel_iommu_superpage) +if (!domain_use_super_page (domain))return 0 ;/* set
iommu_superpageto the smallest common denominator */drivers/iommu/intel/iommu.c +8
-0@@ -5656,6 +5678,14 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x1632, quirk_iommu_igfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x163A , quirk_iommu_igfx);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x163D , quirk_iommu_igfx); +static void quirk_skip_igfx_superpage (struct pci_dev *dev) +{ +pci_info (dev,"Disabling IOMMU superpage for graphics on this chipset\n" ); + iommu_skip_igfx_superpage =1 ; +} + +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x3184 , quirk_skip_igfx_superpage); +static void quirk_iommu_rwbf (struct pci_dev *dev){ if (risky_device(dev))Best regards,
baolu
Signature · 6 lines
Ville Syrjälä Intel _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Lu Baolu
maintainerRe: [Intel-gfx] [PATCH 1/4] iommu/vt-d: Disable superpage for Geminilake igfx
Quoted 66 lines · Ville Syrjälä
Quoted 54 lines · Lu Baolu
Quoted 21 lines · Ville Syrjälä
Quoted 20 lines · Lu Baolu
Quoted 19 lines · Ville Syrjala
From: Ville Syrjälä<[email protected]>
While running "
gem_exec_big--r single" from igt-gpu-tools on Geminilake as soon as a 2M mapping is made I tend to get a DMAR write fault. Strangely the faulting address is always a 4K page and usually very far away from the 2M page that got mapped. But if no 2M mappings get used I can't reproduce the fault.I also tried to dump the PTE for the faulting address but it actually
looks correct to me (ie. definitely seems to have the write bit set):
DMAR: DRHD: handling fault status reg 2
DMAR: [DMA Write] Request device [00:02.0] PASID ffffffff fault addr7fa8a78000[fault reason 05] PTE Write access is not set
DMAR: fault7fa8a78000(level=1) PTE =149efc003So not really sure what's going on and this might just be full on duct tape, but it seems to work here. The machine has now survived a whole day running that test whereas with superpage enabled it fails in less than a minute usually.
Quoted 9 lines
Quoted 4 lines
Quoted 2 lines
TODO: might be nice to disable superpage only for the igfx iommu
instead of both iommusIf all these quirks are about igfx dedicated iommu's, I would suggest to disable superpage only for the igfx ones.
Sure. Unfortunately there's no convenient mechanism to do that in the iommu driver that I can immediately see. So not something I can just whip up easily. Since you're actually familiar with the driver maybe you can come up with a decent solution for that?
How about something like below? [no compile, no test...]
drivers/iommu/intel/iommu.c +5
-0@@ -338,6 +338,7 @@ static int intel_iommu_strict;static int intel_iommu_superpage =1 ;static int iommu_identity_mapping;static int iommu_skip_te_disable; +static int iommu_skip_igfx_superpage;#define IDENTMAP_GFX 2#define IDENTMAP_AZALIA 4@@ -652,6 +653,27 @@ static bool domain_update_iommu_snooping(struct intel_iommu *skip)return ret; } +static bool domain_use_super_page (struct dmar_domain *domain) +{ +struct dmar_drhd_unit *drhd; +struct intel_iommu *iommu;drivers/iommu/intel/iommu.c static bool domain_update_iommu_snooping(struct · line 670
Quoted 10 lines
drivers/iommu/intel/iommu.c +10
-0+bool ret = true; + +if (!intel_iommu_superpage) +return false; + +rcu_read_lock (); +for_each_active_iommu (iommu, drhd) { +if (drhd->gfx_dedicated && iommu_skip_igfx_superpage) { + ret = false; +break ^
Quoted 5 lines
Missing semicolon. Othwerwise seems to work great here. Thanks.
Are you going to turn this into a proper patch, or do you want me to just squash this into my patches and repost?
Please go ahead with a new version.
Best regards,
baolu
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 2/4 iommu/vt-d: Disable superpage for Broxton igfx
In reply to Ville SyrjalaFrom: Ville Syrjälä <[email protected]>
Broxton has known issues with VT-d superpage. Namely frame buffer compression (FBC) can't be safely used when superpage is enabled. Currently we're disabling FBC entirely when VT-d is active, but I think just disabling superpage would be better since FBC can save some power.
TODO: might be nice to disable superpage only for the igfx iommu
instead of both iommus
TODO: would be nice to use the macros from include/drm/i915_pciids.h,
but can't do that with DECLARE_PCI_FIXUP_HEADER()
--- drivers/iommu/intel/iommu.c | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/iommu/intel/iommu.c +7 -0
@@ -5623,6 +5623,13 @@ static void quirk_iommu_nosp(struct pci_dev *dev) intel_iommu_superpage =0 ; } +/* Broxton igfx has issues with superpage */ +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x0A84 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x1A84 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x1A85 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x5A84 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x5A85 , quirk_iommu_nosp); +/* Geminilake igfx appears to have issues with superpage */ DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x3184 , quirk_iommu_nosp);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x3185 , quirk_iommu_nosp);
Signature · 6 lines
2.31.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 3/4 iommu/vt-d: Disable superpage for Skylake igfx
In reply to Ville SyrjalaFrom: Ville Syrjälä <[email protected]>
Skylake has known issues with VT-d superpage. Namely frame buffer compression (FBC) can't be safely used when superpage is enabled. Currently we're disabling FBC entirely when VT-d is active, but I think just disabling superpage would be better since FBC can save some power.
TODO: might be nice to disable superpage only for the igfx iommu
instead of both iommus
TODO: would be nice to use the macros from include/drm/i915_pciids.h,
but can't do that with DECLARE_PCI_FIXUP_HEADER()
--- drivers/iommu/intel/iommu.c | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+)
drivers/iommu/intel/iommu.c +27 -0
@@ -5623,6 +5623,33 @@ static void quirk_iommu_nosp(struct pci_dev *dev) intel_iommu_superpage =0 ; } +/* Skylake igfx has issues with superpage */ +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x1906 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x1913 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x190E , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x1915 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x1902 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x190A , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x190B , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x1917 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x1916 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x1921 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x191E , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x1912 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x191A , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x191B , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x191D , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x1923 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x1926 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x1927 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x192A , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x192B , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x192D , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x1932 , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x193A , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x193B , quirk_iommu_nosp); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x193D , quirk_iommu_nosp); +/* Broxton igfx has issues with superpage */ DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x0A84 , quirk_iommu_nosp);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_INTEL ,0x1A84 , quirk_iommu_nosp);
Signature · 6 lines
2.31.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 4/4 drm/i915/fbc: Allow FBC + VT-d on SKL/BXT
In reply to Ville SyrjalaFrom: Ville Syrjälä <[email protected]>
With the iommu driver disabling VT-d superpage it should be safe to use FBC on SKL/BXT with VT-d otherwise enabled.
--- drivers/gpu/drm/i915/display/intel_fbc.c | 16 ---------------- 1 file changed, 16 deletions(-)
drivers/gpu/drm/i915/display/intel_fbc.c +0 -16
@@ -1448,19 +1448,6 @@ static int intel_sanitize_fbc_option(struct drm_i915_private *dev_priv)return 0 ; } -static bool need_fbc_vtd_wa (struct drm_i915_private *dev_priv) -{ -/* WaFbcTurnOffFbcWhenHyperVisorIsUsed:skl,bxt */ -if (intel_vtd_active () && - (IS_SKYLAKE (dev_priv) ||IS_BROXTON (dev_priv))) { -drm_info (&dev_priv->drm, -"Disabling framebuffer compression (FBC) to prevent screen flicker with VT-d enabled\n" ); -return true; - } - -return false; -} -/** * intel_fbc_init - Initialize FBC * @dev_priv: the i915 device
@@ -1478,9 +1465,6 @@ void intel_fbc_init(struct drm_i915_private *dev_priv)if (!drm_mm_initialized (&dev_priv->mm.stolen))mkwrite_device_info (dev_priv)->display.has_fbc = false; -if (need_fbc_vtd_wa (dev_priv)) -mkwrite_device_info (dev_priv)->display.has_fbc = false; - dev_priv->params.enable_fbc =intel_sanitize_fbc_option (dev_priv);drm_dbg_kms (&dev_priv->drm,"Sanitized enable_fbc value: %d\n" , dev_priv->params.enable_fbc);
Signature · 6 lines
2.31.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for iommu/vt-d: Disable igfx iommu superpage on bxt/skl/glk
In reply to Ville Syrjala== Series Details ==
== Series Details ==
Series: iommu/vt-d: Disable igfx iommu superpage on bxt/skl/glk
URL : https://patchwork.freedesktop.org/series/92374/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip 7da685194fc4 iommu/vt-d: Disable superpage for Geminilake igfx -:18: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line) #18: DMAR: [DMA Write] Request device [00:02.0] PASID ffffffff fault addr 7fa8a78000 [fault reason 05] PTE Write access is not set
total: 0 errors, 1 warnings, 0 checks, 16 lines checked 54ea2020b79a iommu/vt-d: Disable superpage for Broxton igfx 7e8975387280 iommu/vt-d: Disable superpage for Skylake igfx 4f652b23e277 drm/i915/fbc: Allow FBC + VT-d on SKL/BXT
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for iommu/vt-d: Disable igfx iommu superpage on bxt/skl/glk
In reply to Ville Syrjala== Series Details ==
== Series Details ==
Series: iommu/vt-d: Disable igfx iommu superpage on bxt/skl/glk
URL : https://patchwork.freedesktop.org/series/92374/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10326 -> Patchwork_20566
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/index.html
Known issues
------------
Here are the changes found in Patchwork_20566 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@core_hotunplug@unbind-rebind:
- fi-bdw-5557u: NOTRUN -> [WARN][1] ([i915#3718])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/fi-bdw-5557u/igt@[email protected]
* igt@kms_psr@cursor_plane_move:
- fi-bdw-5557u: NOTRUN -> [SKIP][2] ([fdo#109271]) +5 similar issues
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/fi-bdw-5557u/igt@kms_psr@cursor_plane_move.html
* igt@vgem_basic@unload:
- fi-bdw-5557u: NOTRUN -> [INCOMPLETE][3] ([i915#3744])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/fi-bdw-5557u/igt@[email protected]
#### Warnings ####
* igt@runner@aborted:
- fi-bdw-5557u: [FAIL][4] ([i915#1602] / [i915#2029]) -> [FAIL][5] ([i915#2722] / [i915#3744])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/fi-bdw-5557u/igt@[email protected]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/fi-bdw-5557u/igt@[email protected]
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[i915#1602]: https://gitlab.freedesktop.org/drm/intel/issues/1602
[i915#2029]: https://gitlab.freedesktop.org/drm/intel/issues/2029
[i915#2722]: https://gitlab.freedesktop.org/drm/intel/issues/2722
[i915#3718]: https://gitlab.freedesktop.org/drm/intel/issues/3718
[i915#3744]: https://gitlab.freedesktop.org/drm/intel/issues/3744
Participating hosts (41 -> 38)
------------------------------
Missing (3): fi-bdw-samus fi-bsw-cyan fi-ilk-650
Build changes
-------------
* Linux: CI_DRM_10326 -> Patchwork_20566
CI-20190529: 20190529
CI_DRM_10326: 8fa21d35c119a14a3cb14035dde5a9cc7e2321d2 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6134: cd63c83e23789eb194d38b8d272247a88122f2f6 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_20566: 4f652b23e277fac45edeba2beec291d6f5428f3f @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
4f652b23e277 drm/i915/fbc: Allow FBC + VT-d on SKL/BXT 7e8975387280 iommu/vt-d: Disable superpage for Skylake igfx 54ea2020b79a iommu/vt-d: Disable superpage for Broxton igfx 7da685194fc4 iommu/vt-d: Disable superpage for Geminilake igfx
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for iommu/vt-d: Disable igfx iommu superpage on bxt/skl/glk
In reply to Ville Syrjala== Series Details ==
== Series Details ==
Series: iommu/vt-d: Disable igfx iommu superpage on bxt/skl/glk
URL : https://patchwork.freedesktop.org/series/92374/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10326_full -> Patchwork_20566_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_20566_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_20566_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_20566_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_exec_capture@pi@vcs0:
- shard-skl: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-skl8/igt@gem_exec_capture@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl4/igt@gem_exec_capture@[email protected]
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* igt@kms_ccs@pipe-a-crc-primary-rotation-180-y_tiled_ccs:
- {shard-rkl}: NOTRUN -> [SKIP][3] +2 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-rkl-6/igt@kms_ccs@pipe-a-crc-primary-rotation-180-y_tiled_ccs.html
* igt@kms_ccs@pipe-c-random-ccs-data-y_tiled_gen12_mc_ccs:
- {shard-rkl}: [FAIL][4] ([i915#3678]) -> [SKIP][5] +1 similar issue
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-rkl-5/igt@kms_ccs@pipe-c-random-ccs-data-y_tiled_gen12_mc_ccs.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-rkl-6/igt@kms_ccs@pipe-c-random-ccs-data-y_tiled_gen12_mc_ccs.html
Known issues
------------
Here are the changes found in Patchwork_20566_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_persistence@legacy-engines-mixed:
- shard-snb: NOTRUN -> [SKIP][6] ([fdo#109271] / [i915#1099]) +5 similar issues
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-snb2/igt@[email protected]
* igt@gem_exec_fair@basic-deadline:
- shard-kbl: [PASS][7] -> [FAIL][8] ([i915#2846])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-kbl2/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-kbl4/igt@[email protected]
- shard-apl: NOTRUN -> [FAIL][9] ([i915#2846])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-apl8/igt@[email protected]
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-tglb: [PASS][10] -> [FAIL][11] ([i915#2842])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-tglb7/igt@gem_exec_fair@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-tglb2/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@vcs1:
- shard-kbl: [PASS][12] -> [FAIL][13] ([i915#2842]) +1 similar issue
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-kbl3/igt@gem_exec_fair@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-kbl1/igt@gem_exec_fair@[email protected]
* igt@gem_exec_schedule@submit-late-slice@vecs0:
- shard-skl: [PASS][14] -> [DMESG-WARN][15] ([i915#1982])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-skl10/igt@gem_exec_schedule@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl6/igt@gem_exec_schedule@[email protected]
* igt@gem_exec_whisper@basic-fds-forked:
- shard-glk: [PASS][16] -> [DMESG-WARN][17] ([i915#118] / [i915#95])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-glk3/igt@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-glk8/igt@[email protected]
* igt@gem_userptr_blits@dmabuf-sync:
- shard-apl: NOTRUN -> [SKIP][18] ([fdo#109271] / [i915#3323])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-apl7/igt@[email protected]
* igt@gem_userptr_blits@vma-merge:
- shard-snb: NOTRUN -> [FAIL][19] ([i915#2724])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-snb2/igt@[email protected]
* igt@gen9_exec_parse@batch-without-end:
- shard-iclb: NOTRUN -> [SKIP][20] ([fdo#112306])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-iclb7/igt@[email protected]
* igt@i915_module_load@reload-with-fault-injection:
- shard-skl: NOTRUN -> [DMESG-WARN][21] ([i915#1982])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl2/igt@[email protected]
* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp:
- shard-apl: NOTRUN -> [SKIP][22] ([fdo#109271] / [i915#1937])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-apl8/igt@i915_pm_lpsp@[email protected]
* igt@i915_pm_rc6_residency@rc6-fence:
- shard-iclb: NOTRUN -> [WARN][23] ([i915#1804] / [i915#2684])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-iclb7/igt@[email protected]
* igt@i915_suspend@sysfs-reader:
- shard-apl: [PASS][24] -> [DMESG-WARN][25] ([i915#180]) +1 similar issue
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-apl6/igt@[email protected]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-apl2/igt@[email protected]
- shard-kbl: NOTRUN -> [DMESG-WARN][26] ([i915#180])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-kbl1/igt@[email protected]
* igt@kms_addfb_basic@invalid-smem-bo-on-discrete:
- shard-glk: NOTRUN -> [FAIL][27] ([i915#3745])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-glk2/igt@[email protected]
* igt@kms_big_fb@linear-32bpp-rotate-180:
- shard-iclb: [PASS][28] -> [DMESG-WARN][29] ([i915#3621])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-iclb3/igt@[email protected]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-iclb1/igt@[email protected]
* igt@kms_chamelium@dp-crc-multiple:
- shard-glk: NOTRUN -> [SKIP][30] ([fdo#109271] / [fdo#111827]) +4 similar issues
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-glk2/igt@[email protected]
* igt@kms_chamelium@vga-hpd:
- shard-apl: NOTRUN -> [SKIP][31] ([fdo#109271] / [fdo#111827]) +10 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-apl2/igt@[email protected]
* igt@kms_chamelium@vga-hpd-without-ddc:
- shard-iclb: NOTRUN -> [SKIP][32] ([fdo#109284] / [fdo#111827]) +1 similar issue
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-iclb1/igt@[email protected]
* igt@kms_color_chamelium@pipe-a-ctm-limited-range:
- shard-skl: NOTRUN -> [SKIP][33] ([fdo#109271] / [fdo#111827]) +1 similar issue
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl7/igt@[email protected]
* igt@kms_color_chamelium@pipe-a-degamma:
- shard-kbl: NOTRUN -> [SKIP][34] ([fdo#109271] / [fdo#111827]) +7 similar issues
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-kbl2/igt@[email protected]
* igt@kms_color_chamelium@pipe-d-ctm-0-5:
- shard-snb: NOTRUN -> [SKIP][35] ([fdo#109271] / [fdo#111827]) +13 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-snb7/igt@[email protected]
* igt@kms_color_chamelium@pipe-d-ctm-blue-to-red:
- shard-iclb: NOTRUN -> [SKIP][36] ([fdo#109278] / [fdo#109284] / [fdo#111827])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-iclb7/igt@[email protected]
* igt@kms_content_protection@atomic:
- shard-kbl: NOTRUN -> [TIMEOUT][37] ([i915#1319])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-kbl3/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][38] ([fdo#109300] / [fdo#111066])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-iclb7/igt@[email protected]
- shard-apl: NOTRUN -> [TIMEOUT][39] ([i915#1319]) +1 similar issue
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-apl7/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-64x64-random:
- shard-apl: NOTRUN -> [FAIL][40] ([i915#3444])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-apl6/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-kbl: [PASS][41] -> [DMESG-WARN][42] ([i915#180]) +3 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-kbl2/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-kbl7/igt@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-max-size-random:
- shard-glk: NOTRUN -> [SKIP][43] ([fdo#109271]) +52 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-glk2/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-256x85-sliding:
- shard-skl: [PASS][44] -> [FAIL][45] ([i915#3444]) +1 similar issue
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-skl8/igt@[email protected]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl4/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-512x512-random:
- shard-iclb: NOTRUN -> [SKIP][46] ([fdo#109278] / [fdo#109279])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-iclb7/igt@[email protected]
* igt@kms_cursor_crc@pipe-d-cursor-512x170-offscreen:
- shard-iclb: NOTRUN -> [SKIP][47] ([fdo#109278]) +7 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-iclb1/igt@[email protected]
* igt@kms_cursor_legacy@cursora-vs-flipa-atomic-transitions-varying-size:
- shard-kbl: [PASS][48] -> [INCOMPLETE][49] ([fdo#109052])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-kbl7/igt@kms_cursor_legacy@cursora-vs-flipa-atomic-transitions-varying-size.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-kbl2/igt@kms_cursor_legacy@cursora-vs-flipa-atomic-transitions-varying-size.html
* igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ac-hdmi-a1-hdmi-a2:
- shard-glk: [PASS][50] -> [FAIL][51] ([i915#79])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-glk8/igt@kms_flip@[email protected]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-glk1/igt@kms_flip@[email protected]
* igt@kms_flip@2x-plain-flip-fb-recreate-interruptible:
- shard-skl: NOTRUN -> [SKIP][52] ([fdo#109271]) +20 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl2/igt@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile:
- shard-snb: NOTRUN -> [SKIP][53] ([fdo#109271]) +276 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-snb7/igt@[email protected]
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilercccs:
- shard-apl: NOTRUN -> [SKIP][54] ([fdo#109271] / [i915#2672])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-apl2/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-apl: NOTRUN -> [DMESG-WARN][55] ([i915#180])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-apl6/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-2p-shrfb-fliptrack-mmap-gtt:
- shard-iclb: NOTRUN -> [SKIP][56] ([fdo#109280]) +4 similar issues
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-iclb1/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-render:
- shard-skl: [PASS][57] -> [FAIL][58] ([i915#49])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-skl6/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl1/igt@[email protected]
* igt@kms_hdr@bpc-switch-dpms:
- shard-skl: [PASS][59] -> [FAIL][60] ([i915#1188])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-skl6/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl1/igt@[email protected]
* igt@kms_pipe_crc_basic@disable-crc-after-crtc-pipe-d:
- shard-glk: NOTRUN -> [SKIP][61] ([fdo#109271] / [i915#533])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-glk2/igt@[email protected]
* igt@kms_pipe_crc_basic@read-crc-pipe-d-frame-sequence:
- shard-apl: NOTRUN -> [SKIP][62] ([fdo#109271] / [i915#533])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-apl8/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-alpha-7efc:
- shard-apl: NOTRUN -> [FAIL][63] ([fdo#108145] / [i915#265])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-apl6/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-alpha-7efc:
- shard-kbl: NOTRUN -> [FAIL][64] ([fdo#108145] / [i915#265]) +1 similar issue
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-kbl2/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [PASS][65] -> [FAIL][66] ([fdo#108145] / [i915#265])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-skl3/igt@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl4/igt@[email protected]
* igt@kms_plane_scaling@2x-scaler-multi-pipe:
- shard-iclb: NOTRUN -> [SKIP][67] ([fdo#109274])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-iclb4/igt@[email protected]
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-1:
- shard-kbl: NOTRUN -> [SKIP][68] ([fdo#109271] / [i915#658]) +1 similar issue
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-kbl3/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][69] ([i915#658])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-iclb7/igt@[email protected]
- shard-apl: NOTRUN -> [SKIP][70] ([fdo#109271] / [i915#658]) +2 similar issues
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-apl7/igt@[email protected]
- shard-glk: NOTRUN -> [SKIP][71] ([fdo#109271] / [i915#658]) +2 similar issues
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-glk2/igt@[email protected]
* igt@kms_psr2_sf@plane-move-sf-dmg-area-2:
- shard-skl: NOTRUN -> [SKIP][72] ([fdo#109271] / [i915#658])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl2/igt@[email protected]
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-kbl: NOTRUN -> [SKIP][73] ([fdo#109271]) +58 similar issues
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-kbl3/igt@kms_psr@psr2_primary_mmap_cpu.html
- shard-iclb: NOTRUN -> [SKIP][74] ([fdo#109441])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-iclb7/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@kms_psr@psr2_primary_page_flip:
- shard-iclb: [PASS][75] -> [SKIP][76] ([fdo#109441])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-iclb2/igt@kms_psr@psr2_primary_page_flip.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-iclb4/igt@kms_psr@psr2_primary_page_flip.html
* igt@kms_sysfs_edid_timing:
- shard-apl: NOTRUN -> [FAIL][77] ([IGT#2])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-apl6/igt@kms_sysfs_edid_timing.html
* igt@kms_vblank@pipe-d-ts-continuation-idle:
- shard-apl: NOTRUN -> [SKIP][78] ([fdo#109271]) +156 similar issues
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-apl2/igt@[email protected]
* igt@kms_writeback@writeback-fb-id:
- shard-apl: NOTRUN -> [SKIP][79] ([fdo#109271] / [i915#2437])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-apl8/igt@[email protected]
* igt@nouveau_crc@pipe-c-ctx-flip-detection:
- shard-iclb: NOTRUN -> [SKIP][80] ([i915#2530])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-iclb7/igt@[email protected]
* igt@perf_pmu@module-unload:
- shard-skl: [PASS][81] -> [DMESG-WARN][82] ([i915#1982] / [i915#262])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-skl2/igt@[email protected]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl2/igt@[email protected]
* igt@prime_nv_api@i915_nv_double_export:
- shard-iclb: NOTRUN -> [SKIP][83] ([fdo#109291])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-iclb7/igt@prime_nv_api@i915_nv_double_export.html
* igt@sysfs_clients@create:
- shard-apl: NOTRUN -> [SKIP][84] ([fdo#109271] / [i915#2994]) +2 similar issues
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-apl8/igt@[email protected]
* igt@sysfs_clients@fair-7:
- shard-skl: NOTRUN -> [SKIP][85] ([fdo#109271] / [i915#2994])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl2/igt@[email protected]
#### Possible fixes ####
* igt@fbdev@nullptr:
- {shard-rkl}: [SKIP][86] ([i915#2582]) -> [PASS][87]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-rkl-5/igt@[email protected]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-rkl-6/igt@[email protected]
* igt@gem_ctx_persistence@many-contexts:
- {shard-rkl}: [FAIL][88] ([i915#2410]) -> [PASS][89]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-rkl-2/igt@[email protected]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-rkl-5/igt@[email protected]
* igt@gem_eio@unwedge-stress:
- {shard-rkl}: [TIMEOUT][90] ([i915#3063]) -> [PASS][91]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-rkl-5/igt@[email protected]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-rkl-6/igt@[email protected]
* igt@gem_exec_fair@basic-none@vcs0:
- shard-kbl: [FAIL][92] ([i915#2842]) -> [PASS][93] +1 similar issue
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-kbl1/igt@gem_exec_fair@[email protected]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-kbl7/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [FAIL][94] ([i915#2842]) -> [PASS][95]
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-tglb1/igt@gem_exec_fair@[email protected]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-tglb3/igt@gem_exec_fair@[email protected]
- {shard-rkl}: [FAIL][96] ([i915#2842]) -> [PASS][97]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-rkl-5/igt@gem_exec_fair@[email protected]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-rkl-2/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@vecs0:
- shard-kbl: [SKIP][98] ([fdo#109271]) -> [PASS][99]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-kbl3/igt@gem_exec_fair@[email protected]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-kbl1/igt@gem_exec_fair@[email protected]
* igt@gem_mmap_gtt@big-copy-odd:
- shard-skl: [FAIL][100] ([i915#307]) -> [PASS][101]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-skl10/igt@[email protected]
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl6/igt@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [FAIL][102] ([i915#454]) -> [PASS][103]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-iclb4/igt@[email protected]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-iclb5/igt@[email protected]
* igt@i915_pm_rpm@gem-pread:
- {shard-rkl}: [SKIP][104] ([fdo#109308]) -> [PASS][105]
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-rkl-5/igt@[email protected]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-rkl-6/igt@[email protected]
* igt@kms_big_fb@x-tiled-32bpp-rotate-180:
- {shard-rkl}: [SKIP][106] ([i915#3638]) -> [PASS][107]
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-rkl-2/igt@[email protected]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-rkl-6/igt@[email protected]
* igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip:
- {shard-rkl}: [SKIP][108] ([i915#3721]) -> [PASS][109] +4 similar issues
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-rkl-5/igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip.html
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-rkl-6/igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip.html
* igt@kms_big_fb@y-tiled-64bpp-rotate-0:
- shard-glk: [FAIL][110] -> [PASS][111]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-glk1/igt@[email protected]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-glk4/igt@[email protected]
* igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs:
- {shard-rkl}: [FAIL][112] ([i915#3678]) -> [PASS][113] +5 similar issues
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-rkl-5/igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs.html
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-rkl-6/igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs.html
* igt@kms_color@pipe-c-ctm-0-75:
- shard-skl: [DMESG-WARN][114] ([i915#1982]) -> [PASS][115] +1 similar issue
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-skl4/igt@[email protected]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl2/igt@[email protected]
* igt@kms_color@pipe-c-ctm-red-to-blue:
- {shard-rkl}: [SKIP][116] ([i915#1149] / [i915#1849]) -> [PASS][117] +1 similar issue
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-rkl-5/igt@[email protected]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-rkl-6/igt@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-64x64-random:
- {shard-rkl}: [SKIP][118] ([fdo#112022]) -> [PASS][119] +9 similar issues
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-rkl-5/igt@[email protected]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-rkl-6/igt@[email protected]
* igt@kms_cursor_crc@pipe-b-cursor-suspend:
- shard-skl: [INCOMPLETE][120] ([i915#146] / [i915#2405] / [i915#300]) -> [PASS][121]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-skl10/igt@[email protected]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl2/igt@[email protected]
* igt@kms_cursor_legacy@cursora-vs-flipa-legacy:
- {shard-rkl}: [SKIP][122] ([fdo#111825]) -> [PASS][123] +4 similar issues
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-rkl-5/igt@[email protected]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-rkl-6/igt@[email protected]
* igt@kms_draw_crc@fill-fb:
- {shard-rkl}: [SKIP][124] ([fdo#111314]) -> [PASS][125] +6 similar issues
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-rkl-5/igt@[email protected]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-rkl-6/igt@[email protected]
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-kbl: [INCOMPLETE][126] ([i915#155] / [i915#180] / [i915#636]) -> [PASS][127]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-kbl1/igt@[email protected]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-kbl6/igt@[email protected]
* igt@kms_flip@2x-flip-vs-expired-vblank@ac-hdmi-a1-hdmi-a2:
- shard-glk: [FAIL][128] ([i915#79]) -> [PASS][129]
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-glk7/igt@kms_flip@[email protected]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-glk7/igt@kms_flip@[email protected]
* igt@kms_flip@2x-plain-flip-fb-recreate-interruptible@ab-hdmi-a1-hdmi-a2:
- shard-glk: [FAIL][130] ([i915#2122]) -> [PASS][131]
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-glk8/igt@kms_flip@[email protected]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-glk7/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-indfb-msflip-blt:
- shard-skl: [SKIP][132] ([fdo#109271]) -> [PASS][133] +116 similar issues
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-skl6/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-indfb-msflip-blt.html
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl1/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-indfb-msflip-blt.html
* igt@kms_plane@plane-panning-bottom-right-suspend@pipe-b-planes:
- shard-kbl: [DMESG-WARN][134] ([i915#180]) -> [PASS][135] +3 similar issues
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-kbl3/igt@kms_plane@[email protected]
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-kbl6/igt@kms_plane@[email protected]
* igt@kms_plane@plane-panning-bottom-right@pipe-b-planes:
- {shard-rkl}: [SKIP][136] ([i915#3558]) -> [PASS][137] +1 similar issue
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-rkl-5/igt@kms_plane@[email protected]
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-rkl-6/igt@kms_plane@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min:
- shard-skl: [FAIL][138] ([fdo#108145] / [i915#265]) -> [PASS][139]
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-skl10/igt@[email protected]
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-skl8/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-max:
- {shard-rkl}: [SKIP][140] ([i915#1849]) -> [PASS][141] +26 similar issues
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10326/shard-rkl-5/igt@[email protected]
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/shard-rkl-6/igt@[email protected]
* igt@kms_psr@cursor_render:
- {shard-rkl}:
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_20566/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BUILD: failure for iommu/vt-d: Disable igfx iommu superpage on bxt/skl/glk (rev2)
In reply to Ville Syrjala== Series Details ==
== Series Details ==
Series: iommu/vt-d: Disable igfx iommu superpage on bxt/skl/glk (rev2)
URL : https://patchwork.freedesktop.org/series/92374/
State : failure
== Summary ==
Applying: iommu/vt-d: Disable superpage for Geminilake igfx
error: corrupt patch at line 14
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch Patch failed at 0001 iommu/vt-d: Disable superpage for Geminilake igfx When you have resolved this problem, run "git am --continue". If you prefer to skip this patch, run "git am --skip" instead. To restore the original branch and stop patching, run "git am --abort".
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx