lockdep: finer-grained completion key for kthread
PATCH 1/2 lockdep: finer-grained completion key for kthread
Ideally we'd create the key through a macro at the real callers and pass it all the way down. This would give us better coverage for cases where a bunch of kthreads are created for the same thing. But this gets the job done meanwhile and unblocks our CI. Refining later on is always possible.
v2:
- make it compile
- use the right map (Tvrtko)
v3:
lockdep insist on a static key, so the cheap way didn't work. Wire 2 keys through all the callers.
I didn't extend this up to alloc_workqueue because the lockdep_invariant_state() call should separate the work functions from the workqueue kthread logic and prevent cross-release state from leaking between unrelated work queues that happen to reuse the same kthreads.
Cc: Tvrtko Ursulin <[email protected]>
Cc: Marta Lofstedt <[email protected]>
References: https://bugs.freedesktop.org/show_bug.cgi?id=103950
--- include/linux/kthread.h | 48 ++++++++++++++++++++++++++++----- kernel/kthread.c | 70 ++++++++++++++++++++++++++++++++++--------------- 2 files changed, 90 insertions(+), 28 deletions(-)
include/linux/kthread.h +41 -7
@@ -6,10 +6,12 @@#include <linux/sched.h> #include <linux/cgroup.h> -__printf(4, 5) -struct task_struct *kthread_create_on_node (int (*threadfn)(void *data), +__printf(6, 7) +struct task_struct *_kthread_create_on_node (int (*threadfn)(void *data),void *data,int node, +struct lock_class_key *exited_key, +struct lock_class_key *parked_key,const char namefmt[], ...);/**
@@ -25,12 +27,27 @@ struct task_struct *kthread_create_on_node(int (*threadfn)(void *data),*/ #define kthread_create(threadfn, data, namefmt, arg...) \ kthread_create_on_node(threadfn, data, NUMA_NO_NODE, namefmt, ##arg) +#define kthread_create_on_node(threadfn, data, node, namefmt, arg...) \ +({ \ + static struct lock_class_key __exited_key, __parked_key; \ + _kthread_create_on_node(threadfn, data, node, &__exited_key, \ + &__parked_key, namefmt, ##arg); \ +}) -struct task_struct *kthread_create_on_cpu (int (*threadfn)(void *data), +struct task_struct *_kthread_create_on_cpu (int (*threadfn)(void *data),void *data,unsigned int cpu, +struct lock_class_key *exited_key, +struct lock_class_key *parked_key,const char *namefmt); +#define kthread_create_on_cpu (threadfn, data, cpu, namefmt) \ +({ \ + static struct lock_class_key __exited_key, __parked_key; \ + _kthread_create_on_cpu(threadfn, data, cpu, &__exited_key,\ + &__parked_key, namefmt); \ +}) +/** * kthread_run - create and wake a thread.
@@ -171,13 +188,30 @@ extern void __kthread_init_worker(struct kthread_worker *worker,int kthread_worker_fn (void *worker_ptr); -__printf(2, 3) +__printf(4, 5)struct kthread_worker * -kthread_create_worker (unsigned int flags,const char namefmt[], ...); +_kthread_create_worker (unsigned int flags, +struct lock_class_key *exited_key, +struct lock_class_key *parked_key, +const char namefmt[], ...); +#define kthread_create_worker(flags, namefmt...) \ +({ \ + static struct lock_class_key __exited_key, __parked_key; \ + _kthread_create_worker(flags, &__exited_key, &__parked_key, \ + ##namefmt); \ +}) -__printf(3, 4) struct kthread_worker * -kthread_create_worker_on_cpu (int cpu,unsigned int flags, +__printf(5, 6) struct kthread_worker * +_kthread_create_worker_on_cpu (int cpu,unsigned int flags, +struct lock_class_key *exited_key, +struct lock_class_key *parked_key,const char namefmt[], ...); +#define kthread_create_worker_on_cpu(cpu, flags, namefmt...) \ +({ \ + static struct lock_class_key __exited_key, __parked_key; \ + _kthread_create_worker(cpu, flags, &__exited_key, &__parked_key,\ + ##namefmt); \ +})bool kthread_queue_work (struct kthread_worker *worker,struct kthread_work *work);
kernel/kthread.c +49 -21
166 lines not on this page · raw message
Signature · 6 lines
2.15.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 2/2 lockdep: Up MAX_LOCKDEP_CHAINS
cross-release ftl
From Chris:
"Fwiw, this isn't cross-release but us reloading the module many times, creating a whole host of new lockclasses. Even more fun is when the module gets a slightly different address and the new lock address hashes into an old lock...
"I did think about a module-hook to revoke the stale lockclasses, but that still leaves all the hashed chains.
"This particular nuisance was temporarily pushed back by teaching igt not to reload i915.ko on a whim."
Cc: Tvrtko Ursulin <[email protected]>
Cc: Marta Lofstedt <[email protected]>
References: https://bugs.freedesktop.org/show_bug.cgi?id=103707
--- kernel/locking/lockdep_internals.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/locking/lockdep_internals.h +1 -1
@@ -69,7 +69,7 @@ enum {#else #define MAX_LOCKDEP_ENTRIES 32768UL -#define MAX_LOCKDEP_CHAINS_BITS 16 +#define MAX_LOCKDEP_CHAINS_BITS 17/* * Stack-trace: tightly packed array of stack backtrace
Signature · 6 lines
2.15.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 2/2] lockdep: Up MAX_LOCKDEP_CHAINS
Quoting Daniel Vetter (2017-11-29 09:46:36)
Quoted 12 lines
cross-release ftl
From Chris:
"Fwiw, this isn't cross-release but us reloading the module many times, creating a whole host of new lockclasses. Even more fun is when the module gets a slightly different address and the new lock address hashes into an old lock...
"I did think about a module-hook to revoke the stale lockclasses, but that still leaves all the hashed chains.
Quoted 7 lines
"This particular nuisance was temporarily pushed back by teaching igt not to reload i915.ko on a whim."
Cc: Tvrtko Ursulin <[email protected]>
Cc: Marta Lofstedt <[email protected]>
References: https://bugs.freedesktop.org/show_bug.cgi?id=103707Signed-off-by Daniel Vetter <[email protected]>
Yes, I think we need to carry this for CI. cross-release will add many more chains, and since we already exhausted the previous array we will need more (and just reducing the number of module reloads only gives a temporary respite). Doubling the array doesn't seem like it'll buy us much time though? Could we afford 20 bits? Might we not also need to expand the lockclasses array? That we could just double?
In principle acked-by for core-for-CI, I think we need a bit surer ground before saying that in general lockdep needs a larger array. -Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 2/2] lockdep: Up MAX_LOCKDEP_CHAINS
Quoting Chris Wilson (2017-11-29 09:57:14)
Quoted 16 lines
Quoting Daniel Vetter (2017-11-29 09:46:36)
Quoted 15 lines
cross-release ftl
From Chris:
"Fwiw, this isn't cross-release but us reloading the module many times, creating a whole host of new lockclasses. Even more fun is when the module gets a slightly different address and the new lock address hashes into an old lock...
"I did think about a module-hook to revoke the stale lockclasses, but that still leaves all the hashed chains.
"This particular nuisance was temporarily pushed back by teaching igt not to reload i915.ko on a whim."
Quoted 7 lines
Quoted 4 lines
Cc: Tvrtko Ursulin <[email protected]>
Cc: Marta Lofstedt <[email protected]>
References: https://bugs.freedesktop.org/show_bug.cgi?id=103707Signed-off-by Daniel Vetter <[email protected]>In principle acked-by for core-for-CI, I think we need a bit surer ground before saying that in general lockdep needs a larger array.
For upstreaming, I wonder if we could sell them on a kconfig? That way Tomi could adjust it more easily in his kconfig.git than having us provide a patch.
-Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 2/2] lockdep: Up MAX_LOCKDEP_CHAINS
Quoted 22 lines · Chris Wilson
Quoting Chris Wilson (2017-11-29 09:57:14)
Quoted 21 lines
Quoting Daniel Vetter (2017-11-29 09:46:36)
Quoted 19 lines
cross-release ftl
From Chris:
"Fwiw, this isn't cross-release but us reloading the module many times, creating a whole host of new lockclasses. Even more fun is when the module gets a slightly different address and the new lock address hashes into an old lock...
"I did think about a module-hook to revoke the stale lockclasses, but that still leaves all the hashed chains.
"This particular nuisance was temporarily pushed back by teaching igt not to reload i915.ko on a whim."
Cc: Tvrtko Ursulin <[email protected]>
Cc: Marta Lofstedt <[email protected]>
References: https://bugs.freedesktop.org/show_bug.cgi?id=103707Signed-off-by Daniel Vetter <[email protected]>
Quoted 6 lines
Quoted 2 lines
In principle acked-by for core-for-CI, I think we need a bit surer ground before saying that in general lockdep needs a larger array.
For upstreaming, I wonder if we could sell them on a kconfig? That way Tomi could adjust it more easily in his kconfig.git than having us provide a patch.
I'll submit both (once CI is taken care of) to lockdep folks and hear what they think about this issue. Maybe fixing module reload is already on their plans, maybe not.
Same really for the kthread fix, lockdep code (and maintainers) are funky enough that I don't really dwell too much in there ... -Daniel
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✗ Fi.CI.BAT: failure for series starting with [1/2] lockdep: finer-grained completion key for kthread
In reply to Daniel Vetter== Series Details ==
== Series Details ==
Series: series starting with [1/2] lockdep: finer-grained completion key for kthread
URL : https://patchwork.freedesktop.org/series/34603/
State : failure
== Summary ==
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
CHK include/generated/bounds.h
CHK include/generated/timeconst.h
CHK include/generated/asm-offsets.h
CALL scripts/checksyscalls.sh
DESCEND objtool
CHK scripts/mod/devicetable-offsets.h
CHK include/generated/compile.h
CHK kernel/config_data.h
CC [M] drivers/thermal/intel_powerclamp.o
In file included from drivers/thermal/intel_powerclamp.c:45:0:
drivers/thermal/intel_powerclamp.c: In function ‘start_power_clamp_worker’:
./include/linux/kthread.h:212:52: error: passing argument 4 of ‘_kthread_create_worker’ from incompatible pointer type [-Werror=incompatible-pointer-types]
_kthread_create_worker(cpu, flags, &__exited_key, &__parked_key,\
^
drivers/thermal/intel_powerclamp.c:497:11: note: in expansion of macro ‘kthread_create_worker_on_cpu’
worker = kthread_create_worker_on_cpu(cpu, 0, "kidle_inject/%ld", cpu);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~./include/linux/kthread.h:193:1: note: expected ‘const char *’ but argument is of type ‘struct lock_class_key *’
_kthread_create_worker(unsigned int flags,
^~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errorsscripts/Makefile.build:316: recipe for target 'drivers/thermal/intel_powerclamp.o' failed make[2]: *** [drivers/thermal/intel_powerclamp.o] Error 1scripts/Makefile.build:569: recipe for target 'drivers/thermal' failed
make[1]: *** [drivers/thermal] Error 2
Makefile:1012: recipe for target 'drivers' failed
make: *** [drivers] Error 2
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 1/1 lockdep: finer-grained completion key for kthread
In reply to Daniel VetterIdeally we'd create the key through a macro at the real callers and pass it all the way down. This would give us better coverage for cases where a bunch of kthreads are created for the same thing. But this gets the job done meanwhile and unblocks our CI. Refining later on is always possible.
v2:
- make it compile
- use the right map (Tvrtko)
v3:
lockdep insist on a static key, so the cheap way didn't work. Wire 2 keys through all the callers.
I didn't extend this up to alloc_workqueue because the lockdep_invariant_state() call should separate the work functions from the workqueue kthread logic and prevent cross-release state from leaking between unrelated work queues that happen to reuse the same kthreads.
v4: CI found more compile fail :-/
Cc: Tvrtko Ursulin <[email protected]>
Cc: Marta Lofstedt <[email protected]>
References: https://bugs.freedesktop.org/show_bug.cgi?id=103950
--- include/linux/kthread.h | 48 ++++++++++++++++++++++++++++----- kernel/kthread.c | 70 ++++++++++++++++++++++++++++++++++--------------- 2 files changed, 90 insertions(+), 28 deletions(-)
include/linux/kthread.h +41 -7
@@ -6,10 +6,12 @@#include <linux/sched.h> #include <linux/cgroup.h> -__printf(4, 5) -struct task_struct *kthread_create_on_node (int (*threadfn)(void *data), +__printf(6, 7) +struct task_struct *_kthread_create_on_node (int (*threadfn)(void *data),void *data,int node, +struct lock_class_key *exited_key, +struct lock_class_key *parked_key,const char namefmt[], ...);/**
@@ -25,12 +27,27 @@ struct task_struct *kthread_create_on_node(int (*threadfn)(void *data),*/ #define kthread_create(threadfn, data, namefmt, arg...) \ kthread_create_on_node(threadfn, data, NUMA_NO_NODE, namefmt, ##arg) +#define kthread_create_on_node(threadfn, data, node, namefmt, arg...) \ +({ \ + static struct lock_class_key __exited_key, __parked_key; \ + _kthread_create_on_node(threadfn, data, node, &__exited_key, \ + &__parked_key, namefmt, ##arg); \ +}) -struct task_struct *kthread_create_on_cpu (int (*threadfn)(void *data), +struct task_struct *_kthread_create_on_cpu (int (*threadfn)(void *data),void *data,unsigned int cpu, +struct lock_class_key *exited_key, +struct lock_class_key *parked_key,const char *namefmt); +#define kthread_create_on_cpu (threadfn, data, cpu, namefmt) \ +({ \ + static struct lock_class_key __exited_key, __parked_key; \ + _kthread_create_on_cpu(threadfn, data, cpu, &__exited_key,\ + &__parked_key, namefmt); \ +}) +/** * kthread_run - create and wake a thread.
@@ -171,13 +188,30 @@ extern void __kthread_init_worker(struct kthread_worker *worker,int kthread_worker_fn (void *worker_ptr); -__printf(2, 3) +__printf(4, 5)struct kthread_worker * -kthread_create_worker (unsigned int flags,const char namefmt[], ...); +_kthread_create_worker (unsigned int flags, +struct lock_class_key *exited_key, +struct lock_class_key *parked_key, +const char namefmt[], ...); +#define kthread_create_worker(flags, namefmt...) \ +({ \ + static struct lock_class_key __exited_key, __parked_key; \ + _kthread_create_worker(flags, &__exited_key, &__parked_key, \ + ##namefmt); \ +}) -__printf(3, 4) struct kthread_worker * -kthread_create_worker_on_cpu (int cpu,unsigned int flags, +__printf(5, 6) struct kthread_worker * +_kthread_create_worker_on_cpu (int cpu,unsigned int flags, +struct lock_class_key *exited_key, +struct lock_class_key *parked_key,const char namefmt[], ...); +#define kthread_create_worker_on_cpu(cpu, flags, namefmt...) \ +({ \ + static struct lock_class_key __exited_key, __parked_key; \ + _kthread_create_worker_on_cpu(cpu, flags, &__exited_key, &__parked_key,\ + ##namefmt); \ +})bool kthread_queue_work (struct kthread_worker *worker,struct kthread_work *work);
kernel/kthread.c +49 -21
166 lines not on this page · raw message
Signature · 6 lines
2.15.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✓ Fi.CI.BAT: success for series starting with lockdep: finer-grained completion key for kthread (rev2)
In reply to Daniel Vetter== Series Details ==
== Series Details ==
Series: series starting with lockdep: finer-grained completion key for kthread (rev2)
URL : https://patchwork.freedesktop.org/series/34603/
State : success
== Summary ==
Series 34603v2 series starting with lockdep: finer-grained completion key for kthread
https://patchwork.freedesktop.org/api/1.0/series/34603/revisions/2/mbox/
Test debugfs_test:
Subgroup read_all_entries:
dmesg-warn -> PASS (fi-bdw-gvtdvm) fdo#103938 +1
Test kms_pipe_crc_basic:
Subgroup read-crc-pipe-b:
fail -> PASS (fi-skl-6700k) fdo#103191
Subgroup suspend-read-crc-pipe-b:
incomplete -> PASS (fi-snb-2520m) fdo#103713fdo#103938 https://bugs.freedesktop.org/show_bug.cgi?id=103938
fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
fdo#103713 https://bugs.freedesktop.org/show_bug.cgi?id=103713
fi-bdw-5557u total:288 pass:267 dwarn:0 dfail:0 fail:0 skip:21 time:444s fi-bdw-gvtdvm total:288 pass:264 dwarn:0 dfail:0 fail:0 skip:24 time:445s fi-blb-e6850 total:288 pass:223 dwarn:1 dfail:0 fail:0 skip:64 time:384s fi-bsw-n3050 total:288 pass:242 dwarn:0 dfail:0 fail:0 skip:46 time:516s fi-bwr-2160 total:288 pass:183 dwarn:0 dfail:0 fail:0 skip:105 time:283s fi-bxt-dsi total:288 pass:258 dwarn:0 dfail:0 fail:0 skip:30 time:505s fi-bxt-j4205 total:288 pass:259 dwarn:0 dfail:0 fail:0 skip:29 time:508s fi-byt-j1900 total:288 pass:253 dwarn:0 dfail:0 fail:0 skip:35 time:492s fi-byt-n2820 total:288 pass:249 dwarn:0 dfail:0 fail:0 skip:39 time:474s fi-elk-e7500 total:288 pass:229 dwarn:0 dfail:0 fail:0 skip:59 time:430s fi-gdg-551 total:288 pass:178 dwarn:1 dfail:0 fail:1 skip:108 time:272s fi-glk-1 total:288 pass:260 dwarn:0 dfail:0 fail:0 skip:28 time:540s fi-hsw-4770 total:288 pass:261 dwarn:0 dfail:0 fail:0 skip:27 time:363s fi-hsw-4770r total:288 pass:224 dwarn:0 dfail:0 fail:0 skip:64 time:264s fi-ivb-3520m total:288 pass:259 dwarn:0 dfail:0 fail:0 skip:29 time:486s fi-kbl-7500u total:288 pass:263 dwarn:1 dfail:0 fail:0 skip:24 time:484s fi-kbl-7560u total:288 pass:269 dwarn:0 dfail:0 fail:0 skip:19 time:528s fi-kbl-7567u total:288 pass:268 dwarn:0 dfail:0 fail:0 skip:20 time:478s fi-kbl-r total:288 pass:261 dwarn:0 dfail:0 fail:0 skip:27 time:534s fi-pnv-d510 total:288 pass:222 dwarn:1 dfail:0 fail:0 skip:65 time:598s fi-skl-6260u total:288 pass:268 dwarn:0 dfail:0 fail:0 skip:20 time:463s fi-skl-6600u total:288 pass:261 dwarn:0 dfail:0 fail:0 skip:27 time:540s fi-skl-6700hq total:288 pass:262 dwarn:0 dfail:0 fail:0 skip:26 time:569s fi-skl-6700k total:288 pass:264 dwarn:0 dfail:0 fail:0 skip:24 time:521s fi-skl-6770hq total:288 pass:268 dwarn:0 dfail:0 fail:0 skip:20 time:503s fi-skl-gvtdvm total:288 pass:265 dwarn:0 dfail:0 fail:0 skip:23 time:453s fi-snb-2520m total:288 pass:249 dwarn:0 dfail:0 fail:0 skip:39 time:557s fi-snb-2600 total:288 pass:248 dwarn:0 dfail:0 fail:0 skip:40 time:419s
Blacklisted hosts:
fi-cfl-s2 total:288 pass:262 dwarn:0 dfail:0 fail:0 skip:26 time:611s
c544c30501259c15ced047e547e787d546c24a43 drm-tip: 2017y-11m-29d-08h-19m-47s UTC integration manifest c7410e9c26c2 lockdep: Up MAX_LOCKDEP_CHAINS68049d7ef928 lockdep: finer-grained completion key for kthread
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7338/
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: ✓ Fi.CI.BAT: success for series starting with lockdep: finer-grained completion key for kthread (rev2)
Quoted 20 lines · Patchwork
== Series Details ==
Series: series starting with lockdep: finer-grained completion key for kthread (rev2)
URL : https://patchwork.freedesktop.org/series/34603/
State : success== Summary ==
Series 34603v2 series starting with lockdep: finer-grained completion key for kthread
https://patchwork.freedesktop.org/api/1.0/series/34603/revisions/2/mbox/Test
debugfs_test:Subgroup read_all_entries: dmesg-warn -> PASS (fi-bdw-gvtdvm) fdo#103938 +1 Test kms_pipe_crc_basic: Subgroup read-crc-pipe-b: fail -> PASS (fi-skl-6700k) fdo#103191 Subgroup suspend-read-crc-pipe-b: incomplete -> PASS (fi-snb-2520m) fdo#103713
Quoted 3 lines
fdo#103938 https://bugs.freedesktop.org/show_bug.cgi?id=103938
fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
fdo#103713 https://bugs.freedesktop.org/show_bug.cgi?id=103713
This indeed seems to fix the perf_pmu lockdep splat, so put into topic/core-for-CI with Chris' and Tvrtko's acks. -Daniel
Quoted 39 lines
fi-bdw-5557u total:288 pass:267 dwarn:0 dfail:0 fail:0 skip:21 time:444s fi-bdw-gvtdvm total:288 pass:264 dwarn:0 dfail:0 fail:0 skip:24 time:445s fi-blb-e6850 total:288 pass:223 dwarn:1 dfail:0 fail:0 skip:64 time:384s fi-bsw-n3050 total:288 pass:242 dwarn:0 dfail:0 fail:0 skip:46 time:516s fi-bwr-2160 total:288 pass:183 dwarn:0 dfail:0 fail:0 skip:105 time:283s fi-bxt-dsi total:288 pass:258 dwarn:0 dfail:0 fail:0 skip:30 time:505s fi-bxt-j4205 total:288 pass:259 dwarn:0 dfail:0 fail:0 skip:29 time:508s fi-byt-j1900 total:288 pass:253 dwarn:0 dfail:0 fail:0 skip:35 time:492s fi-byt-n2820 total:288 pass:249 dwarn:0 dfail:0 fail:0 skip:39 time:474s fi-elk-e7500 total:288 pass:229 dwarn:0 dfail:0 fail:0 skip:59 time:430s fi-gdg-551 total:288 pass:178 dwarn:1 dfail:0 fail:1 skip:108 time:272s fi-glk-1 total:288 pass:260 dwarn:0 dfail:0 fail:0 skip:28 time:540s fi-hsw-4770 total:288 pass:261 dwarn:0 dfail:0 fail:0 skip:27 time:363s fi-hsw-4770r total:288 pass:224 dwarn:0 dfail:0 fail:0 skip:64 time:264s fi-ivb-3520m total:288 pass:259 dwarn:0 dfail:0 fail:0 skip:29 time:486s fi-kbl-7500u total:288 pass:263 dwarn:1 dfail:0 fail:0 skip:24 time:484s fi-kbl-7560u total:288 pass:269 dwarn:0 dfail:0 fail:0 skip:19 time:528s fi-kbl-7567u total:288 pass:268 dwarn:0 dfail:0 fail:0 skip:20 time:478s fi-kbl-r total:288 pass:261 dwarn:0 dfail:0 fail:0 skip:27 time:534s fi-pnv-d510 total:288 pass:222 dwarn:1 dfail:0 fail:0 skip:65 time:598s fi-skl-6260u total:288 pass:268 dwarn:0 dfail:0 fail:0 skip:20 time:463s fi-skl-6600u total:288 pass:261 dwarn:0 dfail:0 fail:0 skip:27 time:540s fi-skl-6700hq total:288 pass:262 dwarn:0 dfail:0 fail:0 skip:26 time:569s fi-skl-6700k total:288 pass:264 dwarn:0 dfail:0 fail:0 skip:24 time:521s fi-skl-6770hq total:288 pass:268 dwarn:0 dfail:0 fail:0 skip:20 time:503s fi-skl-gvtdvm total:288 pass:265 dwarn:0 dfail:0 fail:0 skip:23 time:453s fi-snb-2520m total:288 pass:249 dwarn:0 dfail:0 fail:0 skip:39 time:557s fi-snb-2600 total:288 pass:248 dwarn:0 dfail:0 fail:0 skip:40 time:419sBlacklisted hosts:
fi-cfl-s2 total:288 pass:262 dwarn:0 dfail:0 fail:0 skip:26 time:611s
c544c30501259c15ced047e547e787d546c24a43drm-tip: 2017y-11m-29d-08h-19m-47s UTC integration manifestc7410e9c26c2lockdep: UpMAX_LOCKDEP_CHAINS68049d7ef928lockdep: finer-grained completion key for kthread== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7338/
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✓ Fi.CI.IGT: success for series starting with lockdep: finer-grained completion key for kthread (rev2)
In reply to Daniel Vetter== Series Details ==
== Series Details ==
Series: series starting with lockdep: finer-grained completion key for kthread (rev2)
URL : https://patchwork.freedesktop.org/series/34603/
State : success
== Summary ==
Blacklisted hosts:
shard-apl total:2476 pass:1560 dwarn:10 dfail:8 fail:14 skip:879 time:12836s shard-hsw total:2661 pass:1534 dwarn:1 dfail:0 fail:9 skip:1117 time:9575s shard-kbl total:2448 pass:1601 dwarn:49 dfail:11 fail:17 skip:764 time:9121s shard-snb total:2539 pass:1236 dwarn:8 dfail:8 fail:6 skip:1277 time:7128s
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7338/shards.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx