Fixing up a messed up Debian upgrade where I needed to reinstall, I had to hit “Select this only if you know what you are doing”. I don’t know what I’m doing, but I had to hit it to do what I needed to get done 😛

Another useful email to the Linux Plumbers mailing list!

Kernel Recipes (which is always held in Paris) is thinking of changing their logo.

@monsieuricon @pavel @kernellogger
And we are very nervous about that possibility!

Last night at the real-time celebration, Thomas Gleixner handed Linus Torvalds his official pull request of the real-time patch on paper "wrapped in gold with a ribbon around it''

@cas

Yes it does affect non-RT kernels. Like all other RT features added to upstream, it improves vanilla Linux. The graphics developers wanted this change. It will allow for things like a blue screen of death where you can see an oops from a graphical interface.

THIS IS IT!!!

The last hurdle for PREEMPT_RT being merged into mainline has just removed by this pull request. Leaving the door open for PREEMPT_RT to be added to 6.12!

@ljs @oleksandr what do you call it when compiled with LLVM? 🤔

@ljs @oleksandr technically that's not C but the C pre-processor (CPP).

@vegard @kernellogger my own experience is that after I add a new feature during the merge window, I'll get a bug report that was actually from an older change before the merge window. Why did this happen? Because the new feature started stressing code paths that were not stressed before and uncovered bugs that existed for a long time. Hence you may see more bug fixes for old bugs early in the rc releases.

@kernellogger Kent's interactions reminds me of another file system creator from long ago, whose name I will not mention.

@a3f yep. The biggest difference is the interface. It shows up as another instance in the tracefs file system that can be enabled or read pretty much like any other instance. You can even use `trace-cmd` to start it, read it and even extract it. Although it will need some tweaks for extraction.

With my new persistent memory mapped ring buffer, were I can retrieve the tracing buffer from the previous boot that crashed, I was able to debug a recent issue. To do this, I added code to allow trace_printk() to be directed to the persistent ring buffer, along with enabling the printk console trace event (writes all printk()s to the tracing ring buffer), I was able to get the perfect idea of what was happening that lead up to the crash!

https://lore.kernel.org/lkml/20240823013902.135036960@goodmis.org/

ANNOUNCE Just released:

trace-cmd v3.3 and libtracecmd 1.5.2

libtracefs v1.8.1

libtraceevent v1.8.3

A tribute to Daniel Bristot de Oliveira from Linux Plumbers. https://lpc.events/blog/current/index.php/2024/07/06/in-memory-of-daniel-bristot-de-oliveira/

Daniel Bristot de Oliveira passed away on Monday, June 24th at the age of 37. Another sad loss for the Linux kernel developer community, Daniel will be sorely missed.

In memory of Daniel: https://t.co/kQCQyTCo1a

Mourning Daniel Bristot de Oliveira

https://lwn.net/Articles/979912/ #LWN

https://lwn.net/Articles/979912/

@andree Actually, the issue is the opposite. What we have is a one size scheduler that fits everyone. But I think it’s more like all season tires. Where they suck in all seasons, but suck equally. The issue I found most frustrating with making changes to the scheduler, is that you may make a change that helps your specific workload, but will cause regressions in someone else’s workload, and your change much be reverted. Now you are stuck with either our of tree patches, or your workflow suffers.

I’m not a big fan of BPF, but I have been a long advocate for pluggable schedulers. My preference would have been true kernel modules, or config options (like file systems), as BPF programs are IMO harder to collaborate on.

"And you get a scheduler, and you get a scheduler, and you get a scheduler"

[ stolen from a colleague ]