| Message ID | CANeU7Q=+Jeuz41pDMVwqDNoCVj8C8bk=nx6+LY8uXcdP5pRiPw@mail.gmail.com (mailing list archive) |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
On Thu, Aug 17, 2017 at 12:42:19AM -0400, Christopher Li wrote: > Hi Luc, Hi, > Thank you so much for the patch. > > Here is the kernel full allmodconfig running ssa-mini-v1 on my new > compile server. On the new server the timing is very consistent. > The variance of run to run is under 0.1 second. > > ssa-mini-v1: > 1205.82user 463.65system 1:16.97elapsed 2168%CPU (0avgtext+0avgdata > 536216maxresident)k > 0inputs+12824outputs (0major+132162996minor)pagefaults 0swaps > 1206.35user 463.27system 1:16.95elapsed 2169%CPU (0avgtext+0avgdata > 536296maxresident)k > 0inputs+12824outputs (0major+132156314minor)pagefaults 0swaps > > > This is the rc5 as base line. > 1173.42user 453.56system 1:15.21elapsed 2163%CPU (0avgtext+0avgdata > 238072maxresident)k > 0inputs+12784outputs (0major+128858147minor)pagefaults 0swaps > 1172.86user 453.53system 1:15.14elapsed 2164%CPU (0avgtext+0avgdata > 238076maxresident)k > 0inputs+12784outputs (0major+128858804minor)pagefaults 0swaps > > So the ssa-mini-v1 is about 2% slower than the current rc5. I haven't measured myself, but I guess that is because this series also includes the removal of simplify_loads(). I wonder what would be these numbers if you measured: 1) r5 + removal of simplify_loads() 2) r5 + sssa-mini-v1 (which includes the removal). > BTW, how do you want your patches to be merged? Assume there is > some feed back. Do you want to come up with V2 V3 or have them merged > to master then come up with fix up on master? If there is some reasonable needed changes I can make a -v2 But I think that most changes can be done later as additional patches once it's already in master. > diff -ruN linux-checker/rc5/drivers/base/firmware_class.sp linux-checker/ssa/drivers/base/firmware_class.sp > --- linux-checker/rc5/drivers/base/firmware_class.sp 2017-08-17 > +++ linux-checker/ssa/drivers/base/firmware_class.sp 2017-08-17 > @@ -1 +1 @@ > -drivers/base/firmware_class.c:395:9: warning: context imbalance in fw_free_buf' - wrong count at exit > +drivers/base/firmware_class.c:391:13: warning: context imbalance in 'fw_free_buf' - wrong count at exit There are often a little bunch of such changes, I've learnt to not worry about them. Basically you have the same warning but at a different line:colonm, something even a different file (source file / include file). The cause is that the BBs are packed or merged differently and the context checking use the position of the BB and no the postion of a specific token. It's annoying, I would like to not have that, but nothing to worry about. > diff -ruN linux-checker/rc5/drivers/block/drbd/drbd_actlog.sp linux-checker/ssa/drivers/block/drbd/drbd_actlog.sp > --- linux-checker/rc5/drivers/block/drbd/drbd_actlog.sp 2017-08-17 > +++ linux-checker/ssa/drivers/block/drbd/drbd_actlog.sp 2017-08-17 > @@ -26,3 +26,4 @@ > drivers/block/drbd/drbd_int.h:1773:14: error: incompatible types in comparison expression (different address spaces) > drivers/block/drbd/drbd_actlog.c:469:44: error: incompatible types in comparison expression (different address spaces) > drivers/block/drbd/drbd_actlog.c:173:16: warning: context imbalance in '_drbd_md_sync_page_io' - different lock contexts for basic block > +drivers/block/drbd/drbd_actlog.c:1244:24: warning: context imbalance in 'drbd_rs_del_all' - different lock contexts for basic block This one is different, it's part of the 8 or so new 'bad context' I was talking about. I'll investigate about. I have also one such warning that was present in -rc5 and absent in sssa-mini-v1. -- Luc -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Aug 17, 2017 at 1:16 AM, Luc Van Oostenryck <luc.vanoostenryck@gmail.com> wrote: > On Thu, Aug 17, 2017 at 12:42:19AM -0400, Christopher Li wrote: >> Hi Luc, > > Hi, > >> Thank you so much for the patch. >> >> Here is the kernel full allmodconfig running ssa-mini-v1 on my new >> compile server. On the new server the timing is very consistent. >> The variance of run to run is under 0.1 second. >> >> ssa-mini-v1: >> 1205.82user 463.65system 1:16.97elapsed 2168%CPU (0avgtext+0avgdata >> 536216maxresident)k >> 0inputs+12824outputs (0major+132162996minor)pagefaults 0swaps >> 1206.35user 463.27system 1:16.95elapsed 2169%CPU (0avgtext+0avgdata >> 536296maxresident)k >> 0inputs+12824outputs (0major+132156314minor)pagefaults 0swaps >> >> >> This is the rc5 as base line. >> 1173.42user 453.56system 1:15.21elapsed 2163%CPU (0avgtext+0avgdata >> 238072maxresident)k >> 0inputs+12784outputs (0major+128858147minor)pagefaults 0swaps >> 1172.86user 453.53system 1:15.14elapsed 2164%CPU (0avgtext+0avgdata >> 238076maxresident)k >> 0inputs+12784outputs (0major+128858804minor)pagefaults 0swaps >> >> So the ssa-mini-v1 is about 2% slower than the current rc5. > > I haven't measured myself, but I guess that is because this series also > includes the removal of simplify_loads(). > > I wonder what would be these numbers if you measured: > 1) r5 + removal of simplify_loads() 1170.54user 453.61system 1:15.05elapsed 2164%CPU (0avgtext+0avgdata 238104maxresident)k 0inputs+12792outputs (0major+128794771minor)pagefaults 0swaps 1172.00user 452.53system 1:14.96elapsed 2166%CPU (0avgtext+0avgdata 238076maxresident)k 0inputs+12784outputs (0major+128795134minor)pagefaults 0swaps > 2) r5 + sssa-mini-v1 (which includes the removal). 1205.84user 463.12system 1:16.84elapsed 2171%CPU (0avgtext+0avgdata 536300maxresident)k 0inputs+12824outputs (0major+132152193minor)pagefaults 0swaps 1204.59user 462.09system 1:16.77elapsed 2170%CPU (0avgtext+0avgdata 536132maxresident)k 0inputs+12824outputs (0major+132160134minor)pagefaults 0swaps > >> BTW, how do you want your patches to be merged? Assume there is >> some feed back. Do you want to come up with V2 V3 or have them merged >> to master then come up with fix up on master? > > If there is some reasonable needed changes I can make a -v2 > But I think that most changes can be done later as additional > patches once it's already in master. Sure. Speaking of which, can you do me a favor bump the -rc5 to finial? Just drop the "-rc5" part in Makefile. Let's release the 0.5.1 and start merging patches :-) Thanks Chris -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Aug 17, 2017 at 7:16 AM, Luc Van Oostenryck <luc.vanoostenryck@gmail.com> wrote: > >> diff -ruN linux-checker/rc5/drivers/block/drbd/drbd_actlog.sp linux-checker/ssa/drivers/block/drbd/drbd_actlog.sp >> --- linux-checker/rc5/drivers/block/drbd/drbd_actlog.sp 2017-08-17 >> +++ linux-checker/ssa/drivers/block/drbd/drbd_actlog.sp 2017-08-17 >> @@ -26,3 +26,4 @@ >> drivers/block/drbd/drbd_int.h:1773:14: error: incompatible types in comparison expression (different address spaces) >> drivers/block/drbd/drbd_actlog.c:469:44: error: incompatible types in comparison expression (different address spaces) >> drivers/block/drbd/drbd_actlog.c:173:16: warning: context imbalance in '_drbd_md_sync_page_io' - different lock contexts for basic block >> +drivers/block/drbd/drbd_actlog.c:1244:24: warning: context imbalance in 'drbd_rs_del_all' - different lock contexts for basic block > > This one is different, it's part of the 8 or so new 'bad context' I was talking about. > I'll investigate about. I just took a quick look at this one. It's interesting. The IR seems correct, the locking is correct too. The problem seems that the 'correct' presence of phi-nodes make that some BB that were merged are not anymore. Nothing is wrong, just different code. But the context checking is quite limited and see now a path where the context could differ. I practice they won't differ and with previous code the context checking saw that because this patch was unexisting due to more aggressive merge of BB. One way to see at it is this is a false warning that appears because of a lack of BB optimizations. I've a vague idea of what can be done here. I'll look at it later, this evening. -- Luc -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Aug 17, 2017 at 2:09 AM, Luc Van Oostenryck <luc.vanoostenryck@gmail.com> wrote: > > I just took a quick look at this one. It's interesting. > The IR seems correct, the locking is correct too. > The problem seems that the 'correct' presence of phi-nodes make > that some BB that were merged are not anymore. Nothing is wrong, I assume you need the phi-node relocation similar to the one used in "dead code elimination using ssa". That will get merge the block with phi node in it. > just different code. But the context checking is quite limited and see now > a path where the context could differ. I practice they won't differ and with > previous code the context checking saw that because this patch was > unexisting due to more aggressive merge of BB. Interesting.Context checking is very sensitive and give a lot of false positives. > One way to see at it is this is a false warning that appears because > of a lack of BB optimizations. > I've a vague idea of what can be done here. I'll look at it later, this evening. Thanks. I will take a look at your patches series. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Chris, On 17 August 2017 at 05:42, Christopher Li <sparse@chrisli.org> wrote: > On Wed, Aug 16, 2017 at 11:34 AM, Luc Van Oostenryck > <luc.vanoostenryck@gmail.com> wrote: >> The goal of this series is to implement and integrate to sparse >> the method described in the paper: >> "Simple and Efficient Construction of Static Single Assignment Form" >> by Matthias Braun, Sebastian Buchwald, Sebastian Hack, >> Roland Leissa, Christoph Mallon and Andreas Zwinkau. >> cfr. http://www.cdl.uni-saarland.de/papers/bbhlmz13cc.pdf >> > BTW, how do you want your patches to be merged? Assume there is > some feed back. Do you want to come up with V2 V3 or have them merged > to master then come up with fix up on master? > Please could we avoid redoing the patch series unless there is something fundamentally wrong with the whole series such as missing log messages or signoffs? I would suggest that we simply apply fixes on top of the series if needed - and indeed if you want to change something that would enable you to apply the fix as well. This certainly makes downstream projects such as dmrC easier to maintain. Thanks and Regards Dibyendu -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Aug 17, 2017 at 7:58 AM, Christopher Li <sparse@chrisli.org> wrote: > > Speaking of which, can you do me a favor bump the -rc5 to finial? > Just drop the "-rc5" part in Makefile. Let's release the 0.5.1 and > start merging patches :-) Sure, just gives me a moment, please. Luc -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Aug 17, 2017 at 8:16 AM, Christopher Li <sparse@chrisli.org> wrote: > On Thu, Aug 17, 2017 at 2:09 AM, Luc Van Oostenryck wrote: > > I assume you need the phi-node relocation similar to the one used > in "dead code elimination using ssa". That will get merge the block > with phi node in it. No, it doesn't seems to be related. It's a miised opportunity of 'try_to_simplify_bb()'. One of the patches in my complete series solves it (and, it seems, the other differences too but I didn't yet checked it thoroughly). It's totally independent of the series, I can send it just after the series. >> just different code. But the context checking is quite limited and see now >> a path where the context could differ. I practice they won't differ and with >> previous code the context checking saw that because this patch was >> unexisting due to more aggressive merge of BB. > > Interesting.Context checking is very sensitive and give a lot of false > positives. Yes, but of course, the general case is impossible to have correctly. -- Luc -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Aug 17, 2017 at 7:58 AM, Christopher Li <sparse@chrisli.org> wrote: >>> ssa-mini-v1: >>> 1205.82user 463.65system 1:16.97elapsed 2168%CPU (0avgtext+0avgdata >>> 536216maxresident)k >>> 0inputs+12824outputs (0major+132162996minor)pagefaults 0swaps >>> 1206.35user 463.27system 1:16.95elapsed 2169%CPU (0avgtext+0avgdata >>> 536296maxresident)k >>> 0inputs+12824outputs (0major+132156314minor)pagefaults 0swaps >>> >>> This is the rc5 as base line. >>> 1173.42user 453.56system 1:15.21elapsed 2163%CPU (0avgtext+0avgdata >>> 238072maxresident)k >>> 0inputs+12784outputs (0major+128858147minor)pagefaults 0swaps >>> 1172.86user 453.53system 1:15.14elapsed 2164%CPU (0avgtext+0avgdata >>> 238076maxresident)k >>> 0inputs+12784outputs (0major+128858804minor)pagefaults 0swaps >>> >>> So the ssa-mini-v1 is about 2% slower than the current rc5. >> >> I wonder what would be these numbers if you measured: >> 1) r5 + removal of simplify_loads() > 1170.54user 453.61system 1:15.05elapsed 2164%CPU (0avgtext+0avgdata > 238104maxresident)k > 0inputs+12792outputs (0major+128794771minor)pagefaults 0swaps > 1172.00user 452.53system 1:14.96elapsed 2166%CPU (0avgtext+0avgdata > 238076maxresident)k > 0inputs+12784outputs (0major+128795134minor)pagefaults 0swaps > >> 2) r5 + sssa-mini-v1 (which includes the removal). > 1205.84user 463.12system 1:16.84elapsed 2171%CPU (0avgtext+0avgdata > 536300maxresident)k > 0inputs+12824outputs (0major+132152193minor)pagefaults 0swaps > 1204.59user 462.09system 1:16.77elapsed 2170%CPU (0avgtext+0avgdata > 536132maxresident)k > 0inputs+12824outputs (0major+132160134minor)pagefaults 0swaps Interesting and strange. This doesn't really correspond to the numbers I have here. Not at all, in fact, but I have only some rough measurements. I'll look at that tomorrow or so. -- Luc -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Aug 17, 2017 at 4:04 PM, Luc Van Oostenryck <luc.vanoostenryck@gmail.com> wrote: > > Interesting and strange. > This doesn't really correspond to the numbers I have here. > Not at all, in fact, but I have only some rough measurements. > Just let me know if you need to get more number. My new server is itchy to compile stuff :-) The good thing about this server is that it does not do CPU frequency scale due to CPU over heating. So the number is very consistent. I can kind of see why your patch is slightly slow now. It allocate more phi nodes and remove them later. Also there is the overhead of the ptrmap. Both of those cause extra memory allocation, as we learn in the ptrlist node size case, it can slow things down a bit. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff -ruN linux-checker/rc5/fs/btrfs/ctree.sp linux-checker/ssa/fs/btrfs/ctree.sp --- linux-checker/rc5/fs/btrfs/ctree.sp 2017-08-17 00:28:19.948449660 -0400 +++ linux-checker/ssa/fs/btrfs/ctree.sp 2017-08-17 00:19:45.049092155 -0400 @@ -1,3 +1,3 @@ fs/btrfs/ctree.c:154:22: error: incompatible types in comparison expression (different address spaces) -fs/btrfs/ctree.c:635:42: warning: context imbalance in 'tree_mod_log_insert_move' - unexpected unlock -fs/btrfs/ctree.c:864:42: warning: context imbalance in 'tree_mod_log_eb_copy' - unexpected unlock +fs/btrfs/ctree.c:354:9: warning: context imbalance in 'tree_mod_log_insert_move' - unexpected unlock +fs/btrfs/ctree.c:354:9: warning: context imbalance in 'tree_mod_log_eb_copy' - unexpected unlock diff -ruN linux-checker/rc5/fs/btrfs/dev-replace.sp linux-checker/ssa/fs/btrfs/dev-replace.sp --- linux-checker/rc5/fs/btrfs/dev-replace.sp 2017-08-17 00:28:20.029451761 -0400 +++ linux-checker/ssa/fs/btrfs/dev-replace.sp 2017-08-17 00:19:45.090093219 -0400 @@ -6,7 +6,7 @@ fs/btrfs/dev-replace.c:807:17: error: incompatible types in comparison expression (different address spaces) fs/btrfs/dev-replace.c:364:9: error: incompatible types in comparison expression (different address spaces) fs/btrfs/dev-replace.c:364:9: error: incompatible types in comparison expression (different address spaces) -fs/btrfs/dev-replace.c:866:9: warning: context imbalance in 'btrfs_dev_replace_lock' - wrong count at exit +fs/btrfs/dev-replace.c:864:6: warning: context imbalance in 'btrfs_dev_replace_lock' - wrong count at exit fs/btrfs/dev-replace.c:886:17: warning: context imbalance in 'btrfs_dev_replace_unlock' - unexpected unlock fs/btrfs/dev-replace.c:900:9: warning: context imbalance in 'btrfs_dev_replace_set_lock_blocking' - unexpected unlock fs/btrfs/dev-replace.c:911:9: warning: context imbalance in 'btrfs_dev_replace_clear_lock_blocking' - wrong count at exit diff -ruN linux-checker/rc5/fs/btrfs/extent-tree.sp linux-checker/ssa/fs/btrfs/extent-tree.sp --- linux-checker/rc5/fs/btrfs/extent-tree.sp 2017-08-17 00:28:19.860447377 -0400 +++ linux-checker/ssa/fs/btrfs/extent-tree.sp 2017-08-17 00:19:45.581105957 -0400 @@ -1,3 +1,3 @@ fs/btrfs/extent-tree.c:7412:39: warning: context imbalance in 'btrfs_lock_cluster' - wrong count at exit fs/btrfs/extent-tree.c:7688:44: warning: context imbalance in 'find_free_extent' - unexpected unlock -fs/btrfs/extent-tree.c:9764:9: warning: context imbalance in 'btrfs_put_block_group_cache' - wrong count at exit +fs/btrfs/extent-tree.c:9759:6: warning: context imbalance in 'btrfs_put_block_group_cache' - wrong count at exit diff -ruN linux-checker/rc5/fs/ceph/caps.sp linux-checker/ssa/fs/ceph/caps.sp --- linux-checker/rc5/fs/ceph/caps.sp 2017-08-17 00:28:20.364460452 -0400 +++ linux-checker/ssa/fs/ceph/caps.sp 2017-08-17 00:19:45.554105256 -0400 @@ -1,3 +1,3 @@ fs/ceph/caps.c:2036:9: warning: context imbalance in 'try_flush_caps' - wrong count at exit -fs/ceph/caps.c:3155:9: warning: context imbalance in 'handle_cap_grant' - wrong count at exit +fs/ceph/caps.c:2909:13: warning: context imbalance in 'handle_cap_grant' - wrong count at exit fs/ceph/caps.c:3739:17: warning: context imbalance in 'ceph_handle_caps' - unexpected unlock diff -ruN linux-checker/rc5/fs/ntfs/compress.sp linux-checker/ssa/fs/ntfs/compress.sp --- linux-checker/rc5/fs/ntfs/compress.sp 2017-08-17 00:28:24.202560020 -0400 +++ linux-checker/ssa/fs/ntfs/compress.sp 2017-08-17 00:19:49.671212062 -0400 @@ -1,3 +1,3 @@ fs/ntfs/compress.c:195:58: warning: Variable length array is used. fs/ntfs/compress.c:220:28: warning: context imbalance in 'ntfs_decompress' - unexpected unlock -fs/ntfs/compress.c:886:16: warning: context imbalance in 'ntfs_read_compressed_block' - different lock contexts for basic block +fs/ntfs/compress.c:785:16: warning: context imbalance in 'ntfs_read_compressed_block' - different lock contexts for basic block diff -ruN linux-checker/rc5/ipc/sem.sp linux-checker/ssa/ipc/sem.sp --- linux-checker/rc5/ipc/sem.sp 2017-08-17 00:28:27.519646071 -0400 +++ linux-checker/ssa/ipc/sem.sp 2017-08-17 00:19:53.227304314 -0400 @@ -1,5 +1,5 @@ ipc/sem.c:521:9: warning: context imbalance in 'newary' - unexpected unlock -ipc/sem.c:1132:17: warning: context imbalance in 'freeary' - unexpected unlock +ipc/sem.c:446:9: warning: context imbalance in 'freeary' - unexpected unlock ipc/sem.c:1585:9: warning: context imbalance in 'semctl_down' - different lock contexts for basic block ipc/sem.c:1690:24: warning: context imbalance in 'find_alloc_undo' - wrong count at exit ./include/linux/rcupdate.h:663:9: warning: context imbalance in 'SyS_semtimedop' - unexpected unlock diff -ruN linux-checker/rc5/ipc/util.sp linux-checker/ssa/ipc/util.sp --- linux-checker/rc5/ipc/util.sp 2017-08-17 00:28:27.471644826 -0400 +++ linux-checker/ssa/ipc/util.sp 2017-08-17 00:19:53.161302602 -0400 @@ -3,5 +3,5 @@ ipc/util.c:373:27: warning: context imbalance in 'ipcget_public' - unexpected unlock ipc/util.c:518:22: warning: context imbalance in 'ipc_lock' - different lock contexts for basic block ipc/util.c:687:29: warning: context imbalance in 'sysvipc_find_ipc' - different lock contexts for basic block -ipc/util.c:725:27: warning: context imbalance in 'sysvipc_proc_next' - unexpected unlock -ipc/util.c:769:27: warning: context imbalance in 'sysvipc_proc_stop' - unexpected unlock +ipc/util.h:162:20: warning: context imbalance in 'sysvipc_proc_next' - unexpected unlock +ipc/util.h:162:20: warning: context imbalance in 'sysvipc_proc_stop' - unexpected unlock diff -ruN linux-checker/rc5/kernel/cgroup/cgroup.sp linux-checker/ssa/kernel/cgroup/cgroup.sp --- linux-checker/rc5/kernel/cgroup/cgroup.sp 2017-08-17 00:28:27.999658524 -0400 +++ linux-checker/ssa/kernel/cgroup/cgroup.sp 2017-08-17 00:19:53.705316715 -0400 @@ -1 +1 @@ -kernel/cgroup/cgroup.c:2656:9: warning: context imbalance in 'cgroup_lock_and_drain_offline' - wrong count at exit +kernel/cgroup/cgroup.c:2645:6: warning: context imbalance in 'cgroup_lock_and_drain_offline' - wrong count at exit diff -ruN linux-checker/rc5/kernel/debug/debug_core.sp linux-checker/ssa/kernel/debug/debug_core.sp --- linux-checker/rc5/kernel/debug/debug_core.sp 2017-08-17 00:28:27.883655514 -0400 +++ linux-checker/ssa/kernel/debug/debug_core.sp 2017-08-17 00:19:53.626314665 -0400 @@ -1 +1 @@ -./arch/x86/include/asm/paravirt.h:809:16: warning: context imbalance in 'kgdb_cpu_enter' - different lock contexts for basic block +kernel/debug/debug_core.c:495:9: warning: context imbalance in 'kgdb_cpu_enter' - different lock contexts for basic block diff -ruN linux-checker/rc5/kernel/events/core.sp linux-checker/ssa/kernel/events/core.sp --- linux-checker/rc5/kernel/events/core.sp 2017-08-17 00:28:28.175663090 -0400 +++ linux-checker/ssa/kernel/events/core.sp 2017-08-17 00:19:53.907321955 -0400 @@ -136,9 +136,9 @@ kernel/events/core.c:149:16: warning: incorrect type in initializer (different address spaces) kernel/events/core.c:11016:26: warning: incorrect type in initializer (different address spaces) kernel/events/core.c:11044:26: warning: incorrect type in initializer (different address spaces) -kernel/events/core.c:156:9: warning: context imbalance in 'perf_ctx_lock' - wrong count at exit +kernel/events/core.c:152:13: warning: context imbalance in 'perf_ctx_lock' - wrong count at exit kernel/events/core.c:164:17: warning: context imbalance in 'perf_ctx_unlock' - unexpected unlock -./include/linux/rcupdate.h:661:9: warning: context imbalance in 'perf_lock_task_context' - different lock contexts for basic block +kernel/events/core.c:1331:17: warning: context imbalance in 'perf_lock_task_context' - different lock contexts for basic block kernel/events/core.c:1358:17: warning: context imbalance in 'perf_pin_task_context' - unexpected unlock kernel/events/core.c:2363:9: warning: context imbalance in '__perf_install_in_context' - wrong count at exit kernel/events/core.c:3862:17: warning: context imbalance in 'find_get_context' - unexpected unlock diff -ruN linux-checker/rc5/net/irda/irqueue.sp linux-checker/ssa/net/irda/irqueue.sp --- linux-checker/rc5/net/irda/irqueue.sp 2017-08-17 00:28:30.494723251 -0400 +++ linux-checker/ssa/net/irda/irqueue.sp 2017-08-17 00:19:56.477388628 -0400 @@ -1,4 +1,4 @@ -net/irda/irqueue.c:405:25: warning: context imbalance in 'hashbin_delete' - different lock contexts for basic block +net/irda/irqueue.c:414:33: warning: context imbalance in 'hashbin_delete' - different lock contexts for basic block net/irda/irqueue.c:445:6: warning: context imbalance in