search for: trace_hardirqs_off_thunk

...39;ve found was; - The functions which can be ftraced look good. (see tracing/available_filter_functions) - following functions should not be able to be probed. - memcpy, memset - native_load_sp0 and some other native functions (need to be clear) - restore - trace_graph_return - trace_hardirqs_off_thunk, trace_hardirqs_on_thunk - This list still be not perfect. I just enabled/disabled kprobes one by one. There might be combined bugs (combination of several kprobes). - Some of them are hard to specify by NOKPROBE_SYMBOL because they are defined in assembly file. Anyway, to fix all...

...39;ve found was; - The functions which can be ftraced look good. (see tracing/available_filter_functions) - following functions should not be able to be probed. - memcpy, memset - native_load_sp0 and some other native functions (need to be clear) - restore - trace_graph_return - trace_hardirqs_off_thunk, trace_hardirqs_on_thunk - This list still be not perfect. I just enabled/disabled kprobes one by one. There might be combined bugs (combination of several kprobes). - Some of them are hard to specify by NOKPROBE_SYMBOL because they are defined in assembly file. Anyway, to fix all...

...d. >> (see tracing/available_filter_functions) >> - following functions should not be able to be probed. >> - memcpy, memset >> - native_load_sp0 and some other native functions (need to be clear) >> - restore >> - trace_graph_return >> - trace_hardirqs_off_thunk, trace_hardirqs_on_thunk >> - This list still be not perfect. I just enabled/disabled kprobes >> one by one. There might be combined bugs (combination of several >> kprobes). >> - Some of them are hard to specify by NOKPROBE_SYMBOL because they are >>...

...d. >> (see tracing/available_filter_functions) >> - following functions should not be able to be probed. >> - memcpy, memset >> - native_load_sp0 and some other native functions (need to be clear) >> - restore >> - trace_graph_return >> - trace_hardirqs_off_thunk, trace_hardirqs_on_thunk >> - This list still be not perfect. I just enabled/disabled kprobes >> one by one. There might be combined bugs (combination of several >> kprobes). >> - Some of them are hard to specify by NOKPROBE_SYMBOL because they are >>...

...;] __bad_area_nosemaphore+0x1d1/0x1f0 [ 100.973299] [<ffffffff8166707d>] bad_area_nosemaphore+0x13/0x15 [ 100.973304] [<ffffffff816763fb>] do_page_fault+0x35b/0x4f0 [ 100.973308] [<ffffffff814d6044>] ? __netdev_alloc_skb+0x24/0x50 [ 100.973313] [<ffffffff8129f75a>] ? trace_hardirqs_off_thunk+0x3a/0x6c [ 100.973318] [<ffffffff81672fa5>] page_fault+0x25/0x30 [ 100.973322] [<ffffffff81455f16>] ? xennet_alloc_rx_buffers+0x166/0x350 [ 100.973326] [<ffffffff8145699a>] xennet_poll+0x7ca/0xe80 [ 100.973330] [<ffffffff814e3e51>] net_rx_action+0x151/0x2b0 [ 100.9...

...hich can be ftraced look good. > (see tracing/available_filter_functions) > - following functions should not be able to be probed. > - memcpy, memset > - native_load_sp0 and some other native functions (need to be clear) > - restore > - trace_graph_return > - trace_hardirqs_off_thunk, trace_hardirqs_on_thunk > - This list still be not perfect. I just enabled/disabled kprobes > one by one. There might be combined bugs (combination of several > kprobes). > - Some of them are hard to specify by NOKPROBE_SYMBOL because they are > defined in assembly...

...ailable_filter_functions) > >> - following functions should not be able to be probed. > >> - memcpy, memset > >> - native_load_sp0 and some other native functions (need to be clear) > >> - restore > >> - trace_graph_return > >> - trace_hardirqs_off_thunk, trace_hardirqs_on_thunk > >> - This list still be not perfect. I just enabled/disabled kprobes > >> one by one. There might be combined bugs (combination of several > >> kprobes). > >> - Some of them are hard to specify by NOKPROBE_SYMBOL because t...

* Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: > (2013/11/21 2:36), Frank Ch. Eigler wrote: [ ... ] > > one needs to resort to something like: > > > > # cat /proc/kallsyms | grep ' [tT] ' | while read addr type symbol; do > > perf probe $symbol > > done > > > > then wait for a few hours for that to finish. Then, or

* Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: > (2013/11/21 2:36), Frank Ch. Eigler wrote: [ ... ] > > one needs to resort to something like: > > > > # cat /proc/kallsyms | grep ' [tT] ' | while read addr type symbol; do > > perf probe $symbol > > done > > > > then wait for a few hours for that to finish. Then, or

...[drm] [ 6253.341844] ? nouveau_gem_new+0x110/0x110 [nouveau] [ 6253.341849] ? preempt_count_sub+0x6a/0xe0 [ 6253.341872] nouveau_drm_ioctl+0x50/0xb0 [nouveau] [ 6253.341876] do_vfs_ioctl+0x93/0x6a0 [ 6253.341880] ? __sys_recvmsg+0x45/0x80 [ 6253.341882] ksys_ioctl+0x60/0x90 [ 6253.341886] ? trace_hardirqs_off_thunk+0x1a/0x1c [ 6253.341888] SyS_ioctl+0xa/0x10 [ 6253.341891] do_syscall_64+0x76/0x130 [ 6253.341895] entry_SYSCALL_64_after_hwframe+0x42/0xb7 [ 6253.341898] RIP: 0033:0x7f7dce046327 [ 6253.341900] RSP: 002b:00007ffd59826aa8 EFLAGS: 00003246 ORIG_RAX: 0000000000000010 [ 6253.341903] RAX: ffffffffff...

...[drm] [ 469.932099] ? nouveau_gem_ioctl_new+0xe0/0xe0 [nouveau] [ 469.932101] ? try_to_wake_up+0x53/0x5f0 [ 469.932120] nouveau_drm_ioctl+0x63/0xb0 [nouveau] [ 469.932122] do_vfs_ioctl+0x40e/0x670 [ 469.932124] ? do_futex+0x157/0x1d0 [ 469.932124] ksys_ioctl+0x5e/0x90 [ 469.932126] ? trace_hardirqs_off_thunk+0x1a/0x2e [ 469.932127] __x64_sys_ioctl+0x16/0x20 [ 469.932128] do_syscall_64+0x6e/0x1e0 [ 469.932129] entry_SYSCALL_64_after_hwframe+0x49/0xbe [ 469.932130] RIP: 0033:0x7f2e77a977c7 [ 469.932130] Code: 00 00 90 48 8b 05 d1 86 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 8...

...:732) [...] [ 37.788715] ksys_ioctl (linux/./include/linux/file.h:43 linux/fs/ioctl.c:750) [...] [ 37.801595] irq event stamp: 829986 [ 37.802060] hardirqs last enabled at (829985): trace_hardirqs_on_thunk (linux/arch/x86/entry/thunk_64.S:41) [ 37.803168] hardirqs last disabled at (829986): trace_hardirqs_off_thunk (linux/arch/x86/entry/thunk_64.S:42) [ 37.804277] softirqs last enabled at (829984): __do_softirq (linux/./arch/x86/include/asm/preempt.h:26 linux/kernel/softirq.c:320) [ 37.805293] softirqs last disabled at (829969): irq_exit (linux/kernel/softirq.c:373 linux/kernel/softirq.c:413) [ 37.80625...

...wq_pool_ids_show+0x140/0x140 > ? kthread_create_on_node+0x60/0x60 > ret_from_fork+0x3a/0x50 > irq event stamp: 22490 > hardirqs last enabled at (22489): [<ffffffff8113281d>] > console_unlock+0x44d/0x5f0 > hardirqs last disabled at (22490): [<ffffffff81001c03>] > trace_hardirqs_off_thunk+0x1a/0x1c > softirqs last enabled at (22486): [<ffffffff81c00330>] > __do_softirq+0x330/0x44d > softirqs last disabled at (22479): [<ffffffff810c3105>] > irq_exit+0xe5/0xf0 > WARNING: CPU: 0 PID: 12 at > drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxgf100.c:1547 > gf10...

..._do_page_fault+0xc90/0xc90 [ 36.171615] ? trace_hardirqs_on_thunk+0x1a/0x1c [ 36.176338] ? syscall_return_slowpath+0x550/0x550 [ 36.181233] ? syscall_return_slowpath+0x2ac/0x550 [ 36.186128] ? prepare_exit_to_usermode+0x350/0x350 [ 36.191113] ? retint_user+0x18/0x18 [ 36.194799] ? trace_hardirqs_off_thunk+0x1a/0x1c [ 36.199613] entry_SYSCALL_64_after_hwframe+0x42/0xb7 [ 36.204772] RIP: 0033:0x43ff09 [ 36.207934] RSP: 002b:00007ffe94d57fc8 EFLAGS: 00000207 ORIG_RAX: 0000000000000010 [ 36.215608] RAX: ffffffffffffffda RBX: 00000000004002c8 RCX: 000000000043ff09 [ 36.222847] RDX: 0000000020d...

...> ? kthread_create_on_node+0x60/0x60 > > ret_from_fork+0x3a/0x50 > > irq event stamp: 22490 > > hardirqs last enabled at (22489): [<ffffffff8113281d>] > > console_unlock+0x44d/0x5f0 > > hardirqs last disabled at (22490): [<ffffffff81001c03>] > > trace_hardirqs_off_thunk+0x1a/0x1c > > softirqs last enabled at (22486): [<ffffffff81c00330>] > > __do_softirq+0x330/0x44d > > softirqs last disabled at (22479): [<ffffffff810c3105>] > > irq_exit+0xe5/0xf0 > > WARNING: CPU: 0 PID: 12 at > > drivers/gpu/drm/nouveau/nvkm/engin...

On Tue, Aug 11, 2020 at 11:20:54AM +0200, peterz at infradead.org wrote: > On Tue, Aug 11, 2020 at 10:38:50AM +0200, J?rgen Gro? wrote: > > In case you don't want to do it I can send the patch for the Xen > > variants. > > I might've opened a whole new can of worms here. I'm not sure we > can/want to fix the entire fallout this release :/ > > Let me

On Tue, Aug 11, 2020 at 11:20:54AM +0200, peterz at infradead.org wrote: > On Tue, Aug 11, 2020 at 10:38:50AM +0200, J?rgen Gro? wrote: > > In case you don't want to do it I can send the patch for the Xen > > variants. > > I might've opened a whole new can of worms here. I'm not sure we > can/want to fix the entire fallout this release :/ > > Let me

...+0x44/0x3a0 kthread+0x12b/0x150 ? wq_pool_ids_show+0x140/0x140 ? kthread_create_on_node+0x60/0x60 ret_from_fork+0x3a/0x50 irq event stamp: 22490 hardirqs last enabled at (22489): [<ffffffff8113281d>] console_unlock+0x44d/0x5f0 hardirqs last disabled at (22490): [<ffffffff81001c03>] trace_hardirqs_off_thunk+0x1a/0x1c softirqs last enabled at (22486): [<ffffffff81c00330>] __do_softirq+0x330/0x44d softirqs last disabled at (22479): [<ffffffff810c3105>] irq_exit+0xe5/0xf0 WARNING: CPU: 0 PID: 12 at drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxgf100.c:1547 gf100_grctx_generate+0x7b2/0x850 [nouve...

...+0x60/0x60 > > > ret_from_fork+0x3a/0x50 > > > irq event stamp: 22490 > > > hardirqs last enabled at (22489): [<ffffffff8113281d>] > > > console_unlock+0x44d/0x5f0 > > > hardirqs last disabled at (22490): [<ffffffff81001c03>] > > > trace_hardirqs_off_thunk+0x1a/0x1c > > > softirqs last enabled at (22486): [<ffffffff81c00330>] > > > __do_softirq+0x330/0x44d > > > softirqs last disabled at (22479): [<ffffffff810c3105>] > > > irq_exit+0xe5/0xf0 > > > WARNING: CPU: 0 PID: 12 at > > > driv...

Hi folks, Here is the result of the latest work on the pvops front, after the x86 arch merge. From the functionality point of view, almost nothing was changed, except for proper vsmp support - which was discussed, but not implemented before - and the introduction of smp_ops in x86_64, which eased the merging of the smp header. Speaking of the merge, a significant part (although not majority) of