== Series Details ==
Series: drm/i915/debugfs: Do not return '0' if there is nothing to return
URL : https://patchwork.freedesktop.org/series/97340/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10932_full -> Patchwork_21689_full
== Series Details ==
Series: drm/i915/debugfs: Do not return '0' if there is nothing to return
URL : https://patchwork.freedesktop.org/series/97340/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10932 -> Patchwork_21689
Change functions that always return '0' to be void type.
Signed-off-by: Andi Shyti
Cc: Maciej Patelczyk
---
drivers/gpu/drm/i915/gt/intel_gt_debugfs.c| 7 ---
drivers/gpu/drm/i915/gt/intel_gt_debugfs.h| 2 +-
drivers/gpu/drm/i915/gt/intel_gt_pm_debugfs.c | 16
Hi Zhi,
I love your patch! Perhaps something to improve:
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-tip/drm-tip drm/drm-next
tegra-drm/drm/tegra/for-next v5.16-rc2 next-20211126]
[cannot apply to airlied/drm-next]
[If your patch is applied to the wrong
== Series Details ==
Series: drm/i915: Use per device iommu check (rev4)
URL : https://patchwork.freedesktop.org/series/96715/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10931_full -> Patchwork_21687_full
Summary
== Series Details ==
Series: drm/i915/gen11: Moving WAs to icl_gt_workarounds_init() (rev2)
URL : https://patchwork.freedesktop.org/series/97208/
State : failure
== Summary ==
Applying: drm/i915/gen11: Moving WAs to icl_gt_workarounds_init()
error: patch failed:
== Series Details ==
Series: drm/i915: Use per device iommu check (rev4)
URL : https://patchwork.freedesktop.org/series/96715/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10931 -> Patchwork_21687
Summary
---
== Series Details ==
Series: drm/i915: Use per device iommu check (rev4)
URL : https://patchwork.freedesktop.org/series/96715/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
Hi Harrison,
This patch will fix guc enabling error which is tested on local setup, please
make your comments.
Thanks,
Raviteja
-Original Message-
From: Talla, RavitejaX Goud
Sent: Tuesday, November 23, 2021 8:16 PM
To: intel-gfx@lists.freedesktop.org; Surendrakumar Upadhyay,
== Series Details ==
Series: series starting with [v3,1/2] i915/gvt: Introduce the mmio_info_table.c
to support VFIO new mdev API
URL : https://patchwork.freedesktop.org/series/97323/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10930_full -> Patchwork_21686_full
From: Tvrtko Ursulin
I accidentally noticed a bunch of tests need two engines of the same class
to do anything meanigful but they report success even if they can't run.
Half way through making them skip instead, I realised it was possibly a
design choice to avoid flip-flopping on the CI
== Series Details ==
Series: drm/i915/gemfs: don't mark huge_opt as static
URL : https://patchwork.freedesktop.org/series/97320/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10930_full -> Patchwork_21685_full
Summary
From: Tvrtko Ursulin
When kernel feature was removed the intel_gpu_top part was forgotten.
Signed-off-by: Tvrtko Ursulin
Cc: Daniel Vetter
Acked-by: Petri Latvala
---
man/intel_gpu_top.rst | 4 -
tools/intel_gpu_top.c | 810 +-
2 files changed, 1
From: Tvrtko Ursulin
.../tests/i915/api_intel_allocator.c: In function ‘basic_alloc’:
.../tests/i915/api_intel_allocator.c:158:25: warning: this ‘if’ clause does not
guard... [-Wmisleading-indentation]
158 | if (j == i)
| ^~
On 26/11/2021 14:01, Petri Latvala wrote:
On Fri, Nov 26, 2021 at 01:07:24PM +, Tvrtko Ursulin wrote:
On 19/11/2021 12:59, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
When kernel feature was removed the intel_gpu_top part was forgotten.
Signed-off-by: Tvrtko Ursulin
Cc: Daniel Vetter
From: Tvrtko Ursulin
With both integrated and discrete Intel GPUs in a system, the current
global check of intel_iommu_gfx_mapped, as done from intel_vtd_active()
may not be completely accurate.
In this patch we add i915 parameter to intel_vtd_active() in order to
prepare it for multiple GPUs
On Fri, Nov 26, 2021 at 01:07:24PM +, Tvrtko Ursulin wrote:
>
> On 19/11/2021 12:59, Tvrtko Ursulin wrote:
> > From: Tvrtko Ursulin
> >
> > When kernel feature was removed the intel_gpu_top part was forgotten.
> >
> > Signed-off-by: Tvrtko Ursulin
> > Cc: Daniel Vetter
>
> Will someone
On 26/11/2021 08:26, Lu Baolu wrote:
On 2021/11/25 19:47, Robin Murphy wrote:
On 2021-11-25 10:42, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
With both integrated and discrete Intel GPUs in a system, the current
global check of intel_iommu_gfx_mapped, as done from intel_vtd_active()
may
On Fri, Nov 26, 2021 at 03:06:15PM +0200, Sarvela, Tomi P wrote:
> The trace is full of ext4, so I'm siding on -rc2 issue.
I can see lots of instances of the same stacktrace on
fi-skl-6600u
and one instance on
shard-tglb7
at least since -rc1 (we don't have logs from before), but none on any
On 19/11/2021 12:59, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
When kernel feature was removed the intel_gpu_top part was forgotten.
Signed-off-by: Tvrtko Ursulin
Cc: Daniel Vetter
Will someone ack this or we carry this code until it ships, if it hasn't
already?
Regards,
Tvrtko
The trace is full of ext4, so I'm siding on -rc2 issue.
You can try re-testing the series to see if same failure happens again.
Tomi
> From: Deak, Imre
>
> Hi,
>
> On Thu, Nov 25, 2021 at 10:38:35PM +, Patchwork wrote:
> > == Series Details ==
> >
> > Series: drm/i915: Fix DPT
On 07/08/2021 06:02, Matt Roper wrote:
On Fri, Aug 06, 2021 at 08:54:59PM +0200, Daniel Vetter wrote:
On Fri, Aug 6, 2021 at 8:25 PM John Harrison wrote:
On 7/28/2021 12:21, Matthew Brost wrote:
Disable bonding on gen12+ platforms aside from ones already supported by
the i915 - TGL, RKL,
Hi,
On Thu, Nov 25, 2021 at 10:38:35PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Fix DPT suspend/resume on !HAS_DISPLAY platforms
> URL : https://patchwork.freedesktop.org/series/97291/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from
== Series Details ==
Series: series starting with [v3,1/2] i915/gvt: Introduce the mmio_info_table.c
to support VFIO new mdev API
URL : https://patchwork.freedesktop.org/series/97323/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10930 -> Patchwork_21686
== Series Details ==
Series: series starting with [v3,1/2] i915/gvt: Introduce the mmio_info_table.c
to support VFIO new mdev API
URL : https://patchwork.freedesktop.org/series/97323/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
cc176fe57a84 i915/gvt: Introduce the
On 26/11/2021 11:08, Matthew Auld wrote:
vfs_kernel_mount() modifies the passed in mount options, leaving us with
"huge", instead of "huge=within_size". Normally this shouldn't matter
with the usual module load/unload flow, however with the core_hotunplug
IGT we are hitting the following, when
== Series Details ==
Series: drm/i915/gemfs: don't mark huge_opt as static
URL : https://patchwork.freedesktop.org/series/97320/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10930 -> Patchwork_21685
Summary
---
== Series Details ==
Series: drm/i915/gemfs: don't mark huge_opt as static
URL : https://patchwork.freedesktop.org/series/97320/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
881e20f9f4a0 drm/i915/gemfs: don't mark huge_opt as static
-:13: WARNING:COMMIT_LOG_LONG_LINE:
From: Zhi Wang
To support the new mdev interfaces and the re-factor patches from
Christoph, which moves the GVT-g code into a dedicated module, the GVT-g
initialization path has to be seperated into two phases:
a) Early initialization.
The early initialization of GVT requires to be done when
From: Zhi Wang
To support the early init of GVT-g, which will be put in i915, after the
GVT-g is moved into a dedicated module, we need to save the MMIO snapshot
in the early init of GVT-g, when the HW hasn't been touched.
v3:
- Fix errors when CONFIG_DRM_I915_WERROR is turned on. (Jani)
Cc:
On Thu, Nov 25, 2021 at 07:16:03PM +0200, Imre Deak wrote:
> The drm.mode_config state is not initialized in case of !HAS_DISPLAY
> so taking the fb_lock and iterating the fb list won't work on those
> platforms. Skip the suspend/resume with an explicit check for this.
>
> Fixes: 9755f055f512
vfs_kernel_mount() modifies the passed in mount options, leaving us with
"huge", instead of "huge=within_size". Normally this shouldn't matter
with the usual module load/unload flow, however with the core_hotunplug
IGT we are hitting the following, when re-probing the memory regions:
i915
On Friday, 26 November 2021 09:00:06 CET Bernatowicz, Marcin wrote:
>
> On 11/18/2021 9:41 AM, Janusz Krzysztofik wrote:
> > Strange -ENODEV responses from the kernel to i915 driver rebind attempts
> > have been sporadically observed. After successfully unbinding the driver
> > from a device by
== Series Details ==
Series: drm/i915/fbc: More FBC refactoring (rev2)
URL : https://patchwork.freedesktop.org/series/97239/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10929_full -> Patchwork_21684_full
Summary
---
On 2021/11/25 19:47, Robin Murphy wrote:
On 2021-11-25 10:42, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
With both integrated and discrete Intel GPUs in a system, the current
global check of intel_iommu_gfx_mapped, as done from intel_vtd_active()
may not be completely accurate.
In this patch
On Thu, 25 Nov 2021 20:43:19 +
"Shankar, Uma" wrote:
> > -Original Message-
> > From: Harry Wentland
> > Sent: Tuesday, November 23, 2021 8:35 PM
> > To: Shankar, Uma ; intel-gfx@lists.freedesktop.org;
> > dri-
> > de...@lists.freedesktop.org
> > Cc: ville.syrj...@linux.intel.com;
On 11/18/2021 9:41 AM, Janusz Krzysztofik wrote:
Strange -ENODEV responses from the kernel to i915 driver rebind attempts
have been sporadically observed. After successfully unbinding the driver
from a device by writing a string representing its PCI bus address to
37 matches
Mail list logo
