(In reply to Jiri Slaby from comment #6) > (In reply to Mel Gorman from comment #5) > > I don't blame you, my question made no sense. I meant -- are there > > kernel-source.git branches with any modifications necessary made? That way, > > I could use the minimal SLE patches against mainline as the baseline, then > > LTO disabled, then LTO enabled. > > OK, so I pushed: > origin/users/jslaby/stable/lto > origin/users/jslaby/stable/lto-base > origin/users/jslaby/stable/lto-disabled > > lto-base is base for both, lto-disabled is the same as lto, but config. > Thanks. > Then I compiled the lto one on 15sp3 using gcc-12 and booted successfully on > 15sp4. > > > That way, I could use the minimal SLE patches against mainline as the baseline, then LTO disabled, then LTO enabled. > > The patches are not that easy backportable, so using them on anything older > (like 15sp4 kernel) creates a lot of conflicts. I.e. all the above is based > on the stable branch (5.18). I was not expecting a backport, the confusion may be that I wanted SLE userspace so the risk of change over time. The first of the tests have started on one machine (2-socket broadwell) and gcc-12 was used to build the kernel. Linux version 5.18.4-lto-baseline (root@hardy3) (gcc-12 (SUSE Linux) 12.1.1 20220517 [revision 325d82b08696da17fb26bd2e1b6ba607649357fb], GNU ld (GNU Binutils; SUSE Linux Enterprise 15) 2.37.20211103-150100.7.29) #1 SMP PREEMPT_DYNAMIC Fri Jun 17 17:30:35 CEST 2022