[lttng-dev] [PATCH] sched/tracing: fix __trace_sched_switch_state (5.18-rc7+)

2022-05-19 Thread Bruce Ashfield via lttng-dev
From: Bruce Ashfield The commit [fix: sched/tracing: Don't re-read p->state when emitting sched_switch event (v5.18)] was correct, but the kernel changed their mind with the following commit: commit 9c2136be0878c88c53dea26943ce40bb03ad8d8d Author: Delyan Kratunov Date: Wed May 11 18:

Re: [lttng-dev] [PATCH] sched/tracing: fix __trace_sched_switch_state (5.18-rc7+)

2022-05-19 Thread Bruce Ashfield via lttng-dev
On Thu, May 19, 2022 at 11:31 AM Mathieu Desnoyers wrote: > > > - On May 19, 2022, at 11:02 AM, Bruce Ashfield via lttng-dev > lttng-dev@lists.lttng.org wrote: > > > From: Bruce Ashfield > > > > The commit [fix: sched/tracing: Don't re-read p->s

[lttng-dev] [PATCH] compaction: make tracepoints condtional on CONFIG_COMPACTION

2022-08-03 Thread Bruce Ashfield via lttng-dev
From: Bruce Ashfield When building against a v5.19 mips kernel, the following errors were triggered: | lttng-modules-2.13.4/src/probes/../../include/instrumentation/events/compaction.h:105:42: note: expected 'struct compact_control *' but argument is of type 'struct compact_control *' |

Re: [lttng-dev] [PATCH] compaction: make tracepoints condtional on CONFIG_COMPACTION

2022-08-10 Thread Bruce Ashfield via lttng-dev
On Wed, Aug 10, 2022 at 11:20 AM Michael Jeanson wrote: > > On 2022-08-03 15 h 23, Bruce Ashfield via lttng-dev wrote: > > Hi all, > > > > This was found during the update of the yocto project reference > > kernel to 5.19. Out of all the supported architectures, o

[lttng-dev] [PATCH 1/3] statedump: adjust to v6.7 cpu topology struct

2023-11-23 Thread Bruce Ashfield via lttng-dev
From: Bruce Ashfield Adjusting the statedump to the following upstream commits: commit b9655e702dc5 [x86/cpu: Encapsulate topology information in cpuinfo_x86] commit e95256335d45 [x86/cpu: Move cpu_core_id into topology info] commit 02fb601d27a7 [x86/cpu: Move phys_proc_id into topology in

[lttng-dev] [PATCH 2/3] wrapper/fdtable: adjust fd lookup to v6.7+

2023-11-23 Thread Bruce Ashfield via lttng-dev
From: Bruce Ashfield commit 0ede61d8589cc2d93 [file: convert to SLAB_TYPESAFE_BY_RCU] renames lookup_fd_rcu to lookup_fdget_rcu, so we need to version adjust the fdtable wrapper accordingly. Signed-off-by: Bruce Ashfield --- Repeating the comment from patch 1 of this series: Someone else may

[lttng-dev] [PATCH 3/3] vmscan: drop isolate_mode (v6.7+)

2023-11-23 Thread Bruce Ashfield via lttng-dev
From: Bruce Ashfield commit 3dfbb555c98ac55b9 [mm, vmscan: remove ISOLATE_UNMAPPED] makes the isolate_mode parameter unused, so it is removed. This updates the event to match. Signed-off-by: Bruce Ashfield --- Repeating the comment from patch 1 & 2 of this series: Someone else may or may not

Re: [lttng-dev] [PATCH 3/3] vmscan: drop isolate_mode (v6.7+)

2023-11-23 Thread Bruce Ashfield via lttng-dev
e: > > Hi Bruce, > > thanks for the patches! There's a similar series waiting for review: > https://review.lttng.org/q/topic:%22fix-linux-6.7.0-rc1%22 > > thanks, > kienan > > On 2023-11-23 14:32, Bruce Ashfield via lttng-dev wrote: > > From: Bruce Ashfie