In D59872#1373978, @kib wrote:

BTW, there is almost always a blank line after each code line in cuse.c. It eats the screen space without giving any clarity.

BTW, there is almost always a blank line after each code line in cuse.c. It eats the screen space without giving any clarity.

In D59519#1373948, @pkubaj wrote:

It looks like you're still missing one patch mentioned previously:

--- src/hotspot/os_cpu/bsd_ppc/prefetch_bsd_ppc.inline.hpp.orig 2026-09-03 11:42:54 UTC
+++ src/hotspot/os_cpu/bsd_ppc/prefetch_bsd_ppc.inline.hpp
@@ -26,8 +26,6 @@
 #ifndef OS_CPU_BSD_PPC_VM_PREFETCH_BSD_PPC_INLINE_HPP
 #define OS_CPU_BSD_PPC_VM_PREFETCH_BSD_PPC_INLINE_HPP

-#include "runtime/prefetch.hpp"
-

 inline void Prefetch::read(const void *loc, intx interval) {
   __asm__ __volatile__ (

Bump.

In D59424#1373884, @sjg wrote:

Q why 10 ? mktemp(1) on netbsd uses 8 in its examples, mktemp(1) on freebsd uses 6

It looks like you're still missing one patch mentioned previously:

@pkubaj Could you please check if this is ok now? Thanks!

Thanks, LGTM.
Approved for commit.

Sure. It's a 34-byte multiboot kernel that GRUB loads; no guest OS involved:

Add links with mentors

In D54881#1372525, @ziaee wrote:

There is no spite or resentment behind my frustrated comment, please do not read into it too deeply.

I forgot about it yesterday. At worst, you can use .cfi_escape + DW_CFA_val_expression to select proper LR and SP directly in debugger.

In exec_splitlock(), do not call disable_splitlock() if hw does not support it.
Remove oldtd != td check in context switch.

In D59815#1373855, @markj wrote:

I wonder if it should be a procctl feature instead of sysarch()? If your intent is to set ia32_splitlock_force = 1 by default, then it would be nice if proccontrol could be used to override application settings without having to modify the program or change the global default. Hmm, but I guess this wouldn't work if the policy is to reset the splitlock setting upon exec.

Q why 10 ? mktemp(1) on netbsd uses 8 in its examples, mktemp(1) on freebsd uses 6

Rebase onto head

@fuz I created D59867 for follow-up to implement optional items mentioned

Yes, this should be addressed in upstream

I wonder if it should be a procctl feature instead of sysarch()? If your intent is to set ia32_splitlock_force = 1 by default, then it would be nice if proccontrol could be used to override application settings without having to modify the program or change the global default. Hmm, but I guess this wouldn't work if the policy is to reset the splitlock setting upon exec.