Search
231 results for “kernellogger”
-
'"Many #profiling tools on #Linux have previously been limited by their reliance on stack unwinding algorithms that require commonly-used frame pointer optimizations to be disabled. This article introduces eu-stacktrace, a prototype tool that uses the #elfutils toolkit’s unwinding libraries to support a sampling profiler to unwind frame pointer-less stack sample data."'
https://developers.redhat.com/articles/2024/06/11/get-system-wide-profiles-binaries-without-frame-pointers (from Serhei Makarov)
-
The Input Stack on Linux – An End-To-End Architecture Overview
https://venam.net/blog/unix/2025/11/27/input_devices_linux.html
Patrick Louis writes: ""Let’s explore and deobfuscate the input stack on #Linux. Our aim is to understand its components and what each does. Input handling can be divided into two parts, separated by a common layer:
#Kernel-level handling: It deals with what happens in the kernel and how events are exposed to user-space
[…]
Exposed layer (middle)
[…]
User-space handling:
[…]
The Widgets, #XServer, #X11 window managers, and #Wayland compositors, which rely on everything elseWe’ll try to make sense of all this, one thing at a time, with a logical and coherent approach.""
-
Really wondering what "upstream" actually refers to in "built-in #Debian #Linux environment with upstream support"
* Qualcomm?
* Debian? [Edit: stable or testing?]
* Upstream #LinuxKernel, #Mesa, et. al.?
Screenshot from https://docs.arduino.cc/hardware/uno-q/
-
'"the Trusted Platform Module (TPM) […] allows an unattended auto-unlock, providing a pass is no longer required. That completely fits to secure disks that have been put in a machine in a safe location. With FDE [Full Disk Encryption] and TPM, your data becomes protected and cannot be read outside of your machine."'
https://www.suse.com/c/full-disk-encryption-grub2-tpm/ #grub #tpm #FullDiskEncryption
-
"An explanation of how #Linux handles system calls on x86-64 and why they show up as expensive operations in performance profiles
https://blog.codingconfessions.com/p/what-makes-system-calls-expensive – from Abhinav Upadhyay
-
GNU #Binutils 2.44 is out:
https://lists.gnu.org/archive/html/info-gnu/2025-02/msg00001.html
Some highlights:
* Assembler:
- Support for new architecture extensions for AArch64, Risc-V and x86.* Linker:
- This now supports mixed LTO and non-LTO object files in relocatable output.
- The ELF forms of the linker support a --image-base=<ADDR> option for compatibility with LLD.[…] does not contain the sources for the gold linker […] now deprecated and will eventually be removed unless volunteers step forward […]
-
Sebastian Aaltonen writes:
""[…]Modern graphics API have improved gradually in the past 10 years. […] As of today, there’s no single API that meets all our requirements, but if we combine their best bits together, we can build the perfect API for modern hardware.
10 years ago, modern APIs were designed for CPU-driven binding models. New bindless features were presented as optional features and extensions. A clean break would improve the usability and reduce the API bloat and driver complexity significantly. It’s extremely difficult to get the whole industry behind a brand new API. I am hoping that vendors are willing to drop backwards compatibility in their new major API versions (Vulkan 2.0, DirectX 13) to embrace the fully bindless GPU architecture we have today. […]
-
These two @lwn articles are prime examples of why good journalism matters and why you should pay money to make sure it thrives:
They both look beyond the shiny statements from the different parties involved and outside commentators such as @torvalds in this case and explain just how it is from a mostly neutral[1] point of view so that you can make your own judgments.
* GPLv2 and installation requirements – https://lwn.net/Articles/1052842/
* SFC v. VIZIO: who can enforce the GPL? – https://lwn.net/Articles/1052734/
[1] We are humans, and even if we try, we are never completely neutral – and a publication like #LWN that targets the FLOSS community obviously will somewhat look at things from the view of its target audience.
-
#Memtest86+ 7.0.0 is out: https://github.com/memtest86plus/memtest86plus/releases/tag/v7.00
"'"This release adds support for IMC (Integrated Memory Controller) polling to get live RAM settings on Intel Core 1st to 14th Gen and AMD Ryzen CPUs, and preliminary ECC polling support for selected AMD Ryzen CPUs.
Complete changelog:
IMC polling for live DRAM settings
Preliminary support for ECC polling
Add support for MMIO UART
Add debugging options
Bug fixes & optimizations"'" -
""The name sure sounds like “mutex”, and that is where the name comes from: “fast, user space mutex”. But, it isn’t really, it’s a building block for concurrency primitives that ushered in a modern world of concurrent performance […]
t was immediately clear that the futex was a huge improvement in highly concurrent environments. Just in that original paper, their tests with 1000 parallel tasks ran 20-120 times faster than sysv locks..🤯
Needless to say, other common operating systems followed suit, including Windows in 2012 and macOS by 2016.
These days, any good locking primitive is going to be based on a futex. […]""
-
Have you heard the claim "Changing 30 lines of code in the #Linux #kernel could cut energy use at some data centers by up to 30 percent" that made the news two or three weeks ago?
Did you wonder if it is really that simple as it sounds in many stories? Then you want to read the following article from @LWN. It describes things in a more nuanced and technical way, as yes, it is not that simple:
https://lwn.net/Articles/1008399/ #LinuxKernel #networking #powerefficiency
-
And with that, #Itanium aka #IA64/IA-64 support is gone from the #Linux #kernel:
https://git.kernel.org/torvalds/c/1e0c505e13162a2abe7c984309cfe2ae976b428d
https://git.kernel.org/torvalds/c/cf8e8658100d4eae80ce9b21f7a81cb024dd5057 (that's the main removal patch, which is about ~2 MByte big)
Bye bye!
-
A nearly 2 MByte big patch to remove #Itanium (#IA64) architecture support from the #LinuxKernel is now in #Linux-next and thus (for now) slated for #kernel 6.7:
Before it hit that tree, it was discussed on #LKML a week ago:
https://lore.kernel.org/all/2023091116[email protected]/ -
Ard Biesheuvel posted an RFC patch series to remove the #IA64/#Itanium support from the #Linux #kernel:
https://lore.kernel.org/all/2023021510[email protected]/ #LinuxKernel
```The IA64 port of Linux has no maintainer, and according to a report from its only remaining user [0], it has been broken for a month and nobody cares.
Given that keeping a complex but unused architecture alive uses up valuable developer bandwidth, let's just get rid of it. […] ```
-
Wanna know what's in store for Linux 6.13, which is expected to be released on January 19 or 26?
Then check out these articles from #LWNnet now freely available:
* The beginning of the 6.13 merge window – https://lwn.net/Articles/998623/
* The rest of the 6.13 merge window – https://lwn.net/Articles/998990/
-
Some highlights from a #F2FS merge for #Linux #kernel 6.2:
https://git.kernel.org/torvalds/c/041fae9c105ae342a4245cf1e0dc56a23fbb9d3c #LinuxKernel```In this round, we've added two features: F2FS_IOC_START_ATOMIC_REPLACE and a per-block age-based extent cache.
F2FS_IOC_START_ATOMIC_REPLACE […] guarantees a per-file atomicity […] more efficient […]
The per-block age-based extent cache […] keeps the per-block age in a file, so that block allocator could split the hot and cold data blocks more accurately.``` -
Using machine learning to optimize/fine-tune the #Linux #kernel at runtime to the needs of the workload – this is something I guess we'll see way more often in the future.
The recent #ossna25 talk "Improve Load Balancing With Machine Learning Techniques Based on the #sched_ext Framework" from Ching-Chun ("Jim") Huang gives a glimpse into such a future.
@lwn write-up: https://lwn.net/Articles/1027096/
Recording: https://www.youtube.com/watch?v=5VXemIXAOrI
-
#sched_ext, which allows scheduling policies to be implemented as #BPF programs, has been merged for #Linux 6.12:
https://git.kernel.org/torvalds/c/88264981f2082248e892a706b2c5004650faac54
See https://lwn.net/Articles/922405/ for a description of what it does and https://lwn.net/Articles/972710/ for the controversy it caused that is the reason why it took so long to land in mainline.
-
FWIW, the PR with the BPF extensible scheduler class aka #sched_ext for #Linux 6.11 is out for 10 days now, but Linus did not merge it yet. Peterz and @qyousef also raised a few issues in between. Remains to be seen if Linus nevertheless will merge sched_ext in the next few days.
For details, see:
https://lore.kernel.org/all/2024072316[email protected]/t/#u
https://lore.kernel.org/all/20240725011907.3f5ropfai3xoy3l3@airbuntu/t/#u
-
The @LWN article about the latest push of the #BPF extensible scheduler class (or "#sched_ext") for #Linux is now freely available: https://lwn.net/Articles/972710/
"'[…] Despite having attracted a fair amount of interest from the development community, sched_ext has run into considerable opposition and seems far from acceptance into the mainline. The posting by Tejun Heo of a new version of the sched_ext series at the beginning of May has restarted this long-running discussion[…]'" #kernel #LinuxKernel
-
Another step closer for #PREEMPT_RT support in the upstream #LinuxKernel:
The #printk patch series "wire up write_atomic() printing"[1] is now in #linux-next[2] and thus slated for inclusion in #kernel 6.11. 🥳
Note, that series does _not_ include threaded printing or nbcon
drivers. Those features will be added in separate follow-up
series.[1] https://lore.kernel.org/all/2024052706[email protected]/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/?qt=grep&q=Ogness
-
Another small step to get #RT aka #Realtime aka #PREEMPT_RT support mainlined was taken, as more preparations for introducing #printk kthreads were merged for #Linux #kernel 6.7: https://git.kernel.org/torvalds/c/2a80532c0745e140852e6b579bbe8371332bb45d
That work comes from this series:
https://lore.kernel.org/all/2023091619[email protected]/#tBut some more work is needed to finally make the #LinuxKernel printk stack be rt capable, as threaded printing, atomic printing regions, or nbcon drivers are still missing afaics.
-
Merged for #LinuxKernel 6.2: #printk patches to reduce the console_lock scope.
They prepare printk for threaded/atomic
printing, which is needed to finally make printk #PREEMPT_RT (aka #REALTIME) safe: https://git.kernel.org/torvalds/c/98d0052d0d9dcd5323833482712b5799ed0bbb0bMore details in the cover letter of the submission of those patches: https://lore.kernel.org/lkml/202211161[email protected]/ #Linux #kernel
-
'"[…] The default dialect in #GCC 15 is still -std=gnu++17. You can use the -std=c++23 or -std=gnu++23 command-line options to enable C++23 features, and similarly for C++26 and others. […] C++26 features in #GCC15 include pack indexing, attributes for structured bindings, enhanced support for functions whose definition consists of =delete, and more. […] A number of defect reports were resolved in GCC 15. A few examples follow. […] C++11 attributes in C++98 […]"'
https://developers.redhat.com/articles/2025/04/24/new-c-features-gcc-15
-
"[…] Let's take a look at 6 improvements to look forward to in the upcoming #GCC 15.
1. Prettier execution paths
2. A new look for C++ template errors
3. Machine-readable diagnostics
4. An easier transition to C23
5. A revamped color scheme
6. libgdiagnostics
We're still fixing bugs, but we hope that GCC 15 will be ready to officially release (as 15.1) sometime later this month. […]"'
https://developers.redhat.com/articles/2025/04/10/6-usability-improvements-gcc-15 – by David Malcolm #gcc15
-
"#drgn is a powerful and flexible [#Linux #kernel] debugger. With drgn, one can write scripts in python to analyze either a live system or a vmcore or a program. […] With drgn, the vmcore analysis seems like natural coding. Having the extensive collection of python libraries also helps, as we can use complex algorithms and data structures to aid with system analysis."
https://blogs.oracle.com/linux/post/enter-the-drgn #LinuxKernel
-
And with "reiserfs: The last commit", #reiserfs is now gone from #Linux for 6.13:
https://git.kernel.org/torvalds/c/fb6f20ecb121cef4d7946f834a6ee867c4e21b4a
63 files changed, 12 insertions, 32804 deletions
Bye bye! 👋
-
Jan plans to remove #reiserfs with #LinuxKernel 6.13:
"Deprecation period of reiserfs ends with the end of this year so it is time to remove it from the #kernel."
63 files changed, 12 insertions, 32804 deletions
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=7f571dbace211fd7a8d679f61ff9fbee46687b6b #Linux
-
And with that we are in the 80s of the #epochalypse[1] – at least percentage wise.
@countdownY2K38 / https://botsin.space/@countdownY2K38/112589990747088252
-
Enjoy it while it lasts, as soon we will have made 80 percent of the way to #epochalypse[1]: https://botsin.space/@countdownY2K38/112575916930985643