== Series Details ==
Series: series starting with [1/2] drm/i915/tgl: Set subplatforms (rev2)
URL : https://patchwork.freedesktop.org/series/79681/
State : failure
== Summary ==
Applying: drm/i915/tgl: Set subplatforms
error: corrupt patch at line 30
error: could not build fake ancestor
hint:
It might be helpful to add a default case in the switch statement for
unsupported cases.
-Original Message-
From: Intel-gfx On Behalf Of José
Roberto de Souza
Sent: Monday, July 20, 2020 10:10 AM
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 1/2] drm/i915/tgl: Set subp
== Series Details ==
Series: drm/i915/gem: Free the fence after a fence-chain lookup failure
URL : https://patchwork.freedesktop.org/series/80358/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8849_full -> Patchwork_18316_full
==
== Series Details ==
Series: drm/i915/gt: Implement WA_1406941453 (rev2)
URL : https://patchwork.freedesktop.org/series/78243/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8846_full -> Patchwork_18312_full
Summary
---
The following changes since commit 2b823fc2568fc354551a63c37f5f5490d70a53d1:
linux-firmware: Update AMD SEV firmware (2020-07-21 09:07:20 -0400)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-firmware guc_v45
for you to fetch changes up to c82f39064bd5c70a18c6
== Series Details ==
Series: drm/i915/gt: Remove defunct intel_virtual_engine_get_sibling()
URL : https://patchwork.freedesktop.org/series/80364/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8850 -> Patchwork_18317
Summary
== Series Details ==
Series: drm/i915/gt: Remove defunct intel_virtual_engine_get_sibling()
URL : https://patchwork.freedesktop.org/series/80364/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.0
Fast mode used, each commit won't be checked separately.
_
As the last user was eliminated in commit e21fecdcde40 ("drm/i915/gt:
Distinguish the virtual breadcrumbs from the irq breadcrumbs"), we can
remove the function. One less implementation detail creeping beyond its
scope.
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
---
drivers/gpu/drm/i915/gt/
== Series Details ==
Series: drm/i915/selftests: Prevent selecting 0 for our random width/align
(rev3)
URL : https://patchwork.freedesktop.org/series/80348/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8848_full -> Patchwork_18315_full
===
On 2020-08-06 at 19:31:43 +0100, Chris Wilson wrote:
> As we are about to write into the mmap'ed pointer using memset, we need
> to specify PROT_WRITE [if we only say PROT_READ, then the memset should
> generate a SIGSEGV].
>
> Fixes: 897d21d14e99 ("i915/gem_caching: Remove libdrm dependency")
> S
As we are about to write into the mmap'ed pointer using memset, we need
to specify PROT_WRITE [if we only say PROT_READ, then the memset should
generate a SIGSEGV].
Fixes: 897d21d14e99 ("i915/gem_caching: Remove libdrm dependency")
Signed-off-by: Chris Wilson
Cc: Ramalingam C
Cc: Dominik Grzegor
On Wed, Aug 05, 2020 at 09:06:13PM +, Patchwork wrote:
> == Series Details ==
>
> Series: i915/tgl: Fix TC-cold block/unblock sequence
> URL : https://patchwork.freedesktop.org/series/80302/
> State : success
Pushed to -dinq, thanks for the review.
>
> == Summary ==
>
> CI Bug Log - chan
On Tue, Jul 21, 2020 at 01:16:40AM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/tgl: Make sure TC-cold is blocked before enabling TC AUX
> power wells
> URL : https://patchwork.freedesktop.org/series/79691/
> State : failure
Pushed to -dinq, thanks for the review.
The f
Re-reported.
-Original Message-
From: James Ausmus
Sent: Thursday, August 6, 2020 10:02 AM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Cc: Taylor, Clinton A
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/gt: Implement
WA_1406941453 (rev2)
On Thu, Aug 06,
== Series Details ==
Series: drm/i915/gt: Implement WA_1406941453 (rev2)
URL : https://patchwork.freedesktop.org/series/78243/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8846 -> Patchwork_18312
Summary
---
**SUCCE
On 06/08/2020 19:10, Chris Wilson wrote:
If dma_fence_chain_find_seqno() reports an error, it does so in its
preamable before it disposes of the input fence. On handling the
error, we need to drop the reference to the fence.
Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/2292
Signed-o
== Series Details ==
Series: drm/i915/gem: Free the fence after a fence-chain lookup failure
URL : https://patchwork.freedesktop.org/series/80358/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8849 -> Patchwork_18316
Summar
On Wed, 2020-08-05 at 18:00 +0300, Imre Deak wrote:
> The command register is the low PCODE MBOX low register not the high
> one as described by the spec. This left the system with the TC-cold
> power state being blocked all the time. Fix things by using the correct
> register.
>
> Also to make su
== Series Details ==
Series: drm/i915/gt: Implement WA_1406941453 (rev2)
URL : https://patchwork.freedesktop.org/series/78243/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8846 -> Patchwork_18312
Summary
---
**FAILU
== Series Details ==
Series: drm/i915/gem: Free the fence after a fence-chain lookup failure
URL : https://patchwork.freedesktop.org/series/80358/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.0
Fast mode used, each commit won't be checked separately.
On Thu, Aug 06, 2020 at 12:09:53AM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/gt: Implement WA_1406941453 (rev2)
> URL : https://patchwork.freedesktop.org/series/78243/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_8846 -> Patchwork_18312
> =
If dma_fence_chain_find_seqno() reports an error, it does so in its
preamable before it disposes of the input fence. On handling the
error, we need to drop the reference to the fence.
Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/2292
Signed-off-by: Chris Wilson
Cc: Lionel Landwerlin
Quoting George Spelvin (2020-03-25 19:24:29)
> igt_mm_config() calls ilog2() on the (pseudo)random 21-bit number
> s>>12. Once in 2 million seeds, this is zero and ilog2 summons
> the nasal demons.
I ran into a similar bug with random returning 0 and remembered this
patch sitting around.
Pushed,
== Series Details ==
Series: drm/i915/selftests: Prevent selecting 0 for our random width/align
(rev3)
URL : https://patchwork.freedesktop.org/series/80348/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8848 -> Patchwork_18315
=
== Series Details ==
Series: drm/i915/gem: Reduce context termination list iteration guard to RCU
URL : https://patchwork.freedesktop.org/series/80337/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8848_full -> Patchwork_18313_full
=
We want to recognise future devices (gen = -1u) and treat them as an
extension of the latest known device, which is typically true.
Signed-off-by: Chris Wilson
---
tests/i915/gem_bad_reloc.c| 2 +-
tests/i915/gem_ctx_create.c | 2 +-
tests/i915/gem_ctx_engines.c
On 06/08/2020 15:57, Chris Wilson wrote:
When igt_random_offset() is a given a range of [0, PAGE_SIZE], it is
allowed to return 0. However, attempting to use a size of 0 for the
igt_lmem_write_cpu() byte poking, leads to call igt_random_offset() with
a range of [offset, offset + 0] and ask it to
On 06/08/2020 18:19, Chris Wilson wrote:
32bits-limit waits for the thread to indicate it has started by busy
spinning on a common variable. The compiler is clever and knows that the
variable cannot change within the thread, and turns it into an infinite
loop!
Signed-off-by: Chris Wilson
Cc: Li
== Series Details ==
Series: drm/i915/selftests: Prevent selecting 0 for our random width/align
(rev3)
URL : https://patchwork.freedesktop.org/series/80348/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.0
Fast mode used, each commit won't be checked sep
32bits-limit waits for the thread to indicate it has started by busy
spinning on a common variable. The compiler is clever and knows that the
variable cannot change within the thread, and turns it into an infinite
loop!
Signed-off-by: Chris Wilson
Cc: Lionel Landwerlin
---
tests/syncobj_timelin
On Wed, 05 Aug 2020, Zhenyu Wang wrote:
> Hi,
>
> Here's to only include gvt fixes for 5.9-rc1. Two fixes to make
> guest suspend/resume working gracefully are included.
Pulled, thanks.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
___
When igt_random_offset() is a given a range of [0, PAGE_SIZE], it is
allowed to return 0. However, attempting to use a size of 0 for the
igt_lmem_write_cpu() byte poking, leads to call igt_random_offset() with
a range of [offset, offset + 0] and ask it to find a length of 4 within
it. This triggers
Quoting Chris Wilson (2020-08-06 15:35:36)
> When igt_random_offset() is a given a range of [0, PAGE_SIZE], it is
> allowed to return 0. However, attempting to use a size of 0 for the
> igt_lmem_write_cpu() byte poking, leads to call igt_random_offset() with
> a range of [offset, offset + 0] and as
Unknown, so future, gen are marked as -1 which we want to treat as -1u
so that always pass >= gen checks.
Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/2298
Signed-off-by: Chris Wilson
Cc: Zbigniew Kempczyński
---
lib/intel_batchbuffer.c | 10 +-
lib/intel_batchbuffer.h | 10
When igt_random_offset() is a given a range of [0, PAGE_SIZE], it is
allowed to return 0. However, attempting to use a size of 0 for the
igt_lmem_write_cpu() byte poking, leads to call igt_random_offset() with
a range of [offset, offset + 0] and ask it to find a length of 4 within
it. This triggers
When igt_random_offset() is a given a range of [0, PAGE_SIZE], it is
allowed to return 0. However, attempting to use a size of 0 for the
igt_lmem_write_cpu() byte poking, leads to call igt_random_offset() with
a range of [offset, offset + 0] and ask it to find a length of 4 within
it. This triggers
On 06/08/2020 12:55, Daniel Vetter wrote:
On Thu, Aug 6, 2020 at 11:21 AM Tvrtko Ursulin
wrote:
On 05/08/2020 17:22, Thomas Hellström (Intel) wrote:
Hi, Chris,
On 8/5/20 2:21 PM, Chris Wilson wrote:
Long story short, we need to manage evictions using dma_resv & dma_fence
tracking. The backin
== Series Details ==
Series: drm/i915/gt: Free stale request on destroying the virtual engine (rev2)
URL : https://patchwork.freedesktop.org/series/79398/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8848 -> Patchwork_18314
== Series Details ==
Series: drm/i915/gt: Free stale request on destroying the virtual engine (rev2)
URL : https://patchwork.freedesktop.org/series/79398/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.0
Fast mode used, each commit won't be checked separa
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip
head: f39035176cb854c6d620af7614a60a485ee26818
commit: ad11f45fae37631b0482ebf6543bdd013d3f9336 [6/10] Merge remote-tracking
branch 'drm-misc/drm-misc-next' into drm-tip
config: x86_64-randconfig-a015-20200806 (attached
== Series Details ==
Series: drm/i915/gem: Reduce context termination list iteration guard to RCU
URL : https://patchwork.freedesktop.org/series/80337/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8848 -> Patchwork_18313
S
On Thu, Aug 6, 2020 at 11:21 AM Tvrtko Ursulin
wrote:
>
>
> On 05/08/2020 17:22, Thomas Hellström (Intel) wrote:
> > Hi, Chris,
> >
> >
> > On 8/5/20 2:21 PM, Chris Wilson wrote:
> >> Long story short, we need to manage evictions using dma_resv & dma_fence
> >> tracking. The backing storage will t
== Series Details ==
Series: drm/i915/gem: Reduce context termination list iteration guard to RCU
URL : https://patchwork.freedesktop.org/series/80337/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.0
Fast mode used, each commit won't be checked separatel
== Series Details ==
Series: drm/i915/gem: Reduce context termination list iteration guard to RCU
URL : https://patchwork.freedesktop.org/series/80337/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
41b2ea22bde1 drm/i915/gem: Reduce context termination list iteration guard to
R
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip
head: f39035176cb854c6d620af7614a60a485ee26818
commit: ad11f45fae37631b0482ebf6543bdd013d3f9336 [6/10] Merge remote-tracking
branch 'drm-misc/drm-misc-next' into drm-tip
config: mips-allyesconfig (attached as .config)
compiler: mips-linux
Since preempt-to-busy, we may unsubmit a request while it is still on
the HW and completes asynchronously. That means it may be retired and in
the process destroy the virtual engine (as the user has closed their
context), but that engine may still be holding onto the unsubmitted
compelted request.
Quoting Chris Wilson (2020-08-06 11:59:54)
> As we now protect the timeline list using RCU, we can drop the
> timeline->mutex for guarding the list iteration during context close, as
> we are searching for an inflight request. Any new request will see the
> context is banned and not be submitted. I
As we now protect the timeline list using RCU, we can drop the
timeline->mutex for guarding the list iteration during context close, as
we are searching for an inflight request. Any new request will see the
context is banned and not be submitted. In doing so, pull the checks for
a concurrent submis
Quoting Tvrtko Ursulin (2020-08-05 16:05:28)
>
> On 05/08/2020 13:21, Chris Wilson wrote:
> > Since preempt-to-busy, we may unsubmit a request while it is still on
> > the HW and completes asynchronously. That means it may be retired and in
> > the process destroy the virtual engine (as the user h
Quoting Tvrtko Ursulin (2020-08-05 16:03:58)
>
> On 05/08/2020 13:21, Chris Wilson wrote:
> > Allow a brief period for continued access to a dead intel_context by
> > deferring the release of the struct until after an RCU grace period.
> > As we are using a dedicated slab cache for the contexts, w
On 05/08/2020 17:22, Thomas Hellström (Intel) wrote:
Hi, Chris,
On 8/5/20 2:21 PM, Chris Wilson wrote:
Long story short, we need to manage evictions using dma_resv & dma_fence
tracking. The backing storage will then be managed using the ww_mutex
borrowed from (and shared via) obj->base.resv,
On Tue, Aug 04, 2020 at 06:35:20AM +, Oleksandr Andrushchenko wrote:
>
> On 8/4/20 9:12 AM, Jürgen Groß wrote:
> > On 31.07.20 14:51, Oleksandr Andrushchenko wrote:
> >> From: Oleksandr Andrushchenko
> >>
> >> The patch c575b7eeb89f: "drm/xen-front: Add support for Xen PV
> >> display fronten
Looks great! Thanks.
Reviewed-by: Dan Carpenter
regards,
dan carpenter
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
As of commit 47ec5303d73ea344 ("Merge
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next") on linux.git ,
my VMware environment cannot boot. Do I need to bisect?
[9.314496][T1] vga16fb: mapped to 0x71050562
[9.467770][T1] Console: switching to colour frame buffe
54 matches
Mail list logo
