=== chris14_ is now known as chris14
[03:53] <bambinone> hi folks, trying to build linux-tools from mainline. `LANG=C fakeroot debian/rules binary` gets me linux-tools-common, linux-tools-host, and linux-cloud-tools-common, but no linux-tools 
[03:53] <bambinone> hoping I'm missing something silly. thanks in advance 
[04:44] <juergh> bambinone, which source are your using?
[04:48] <bambinone> juergh: git://kernel.ubuntu.com/virgin/testing/crack.git, cod/mainline/v6.5-rc7
[05:54] <juergh> bambinone, that looks broken. it shouldn't produce any tools packages for mainline builds.
[05:55] <juergh> ./debian/rules printenv | grep mainline
[05:55] <juergh> do_mainline_build         = true
[05:55] <juergh> and
[05:56] <juergh> grep -A 6 mainline debian/rules
[05:56] <juergh> # Being used to build a mainline build -- turn off things which do not work.
[05:56] <juergh> ifeq ($(do_mainline_build),true)
[05:56] <juergh> 	do_extras_package=false
[05:56] <juergh> 	do_tools=false
[05:56] <juergh> 	no_dumpfile=1
[05:56] <juergh> $(foreach _m,$(all_dkms_modules),$(eval do_$(_m) = false))
[05:56] <juergh> 	do_skip_checks=true
[05:56] <juergh> endif
[06:06] <bambinone> juergh: wamp wamp. thank you. maybe I can just build cpupower in the tree
[06:17] <juergh> bambinone, you could comment out 'do_tools=false' in debian/rules and see what you get. try 'debian/rules printenv' to get some idea about the settings.
[06:18] <juergh> or drop 'do_mainline_build' from debian.master/rules.d/hooks.mk altogether...
[06:19] <juergh> but that will likely explode
=== lexandrop_ is now known as lexandrop
[16:47] <bambinone> juergh: thank you!
[18:19] <atmark> hello, how can I recompile the latest 20.04 HWE kernel ( 5.15.0.79 as of this writing ) using kernel the config of 5.15.0-25 ? 
[18:20] <joseogando_> @atmark Maybe it would be easier to just add the options to 5.15.0.79 . Do you know what options you want to change.
[18:21] <atmark> I know how to compile the latest HWE Kernel but I couldn't find a option to specify a different kernel config 
[18:23] <joseogando_> A whole different config would be more difficult and I wouldn't know an easy way, but if you want to add or modify configurations you can do so in the annotations format that Ubuntu has. It would be under your debian.*/config/annotations file
[18:24] <atmark> The thing is, I don't know the options to change. 5.15.0-25 is the version that KVM live migration has no issues. 
[18:25] <joseogando_> Then I would compare /boot/config-5.15.0.76 vs /boot/config-5.15.0-25 and add those options to the annotations file mentioned.
[18:25] <atmark> > 5.15.0-25  -  I'm hitting live migration on CPUs running EPYC3 
[18:26] <joseogando_> And I am not aware of the particular issue... I'm just giving you general guidelines
[18:27] <atmark> 5.15.0.79 is mapped to 5.15.111. I compiled 5.15.111 from source and didn't hit any live migration issue. 
[18:28] <atmark> I created bug report but no ack https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2024500
[18:28] -ubottu:#ubuntu-kernel- Launchpad bug 2024500 in linux-hwe-5.15 (Ubuntu) "KVM: after upgrading the kernel to 5.15.0-75, VM hangs after migration." [Undecided, Confirmed]
[18:35] <atmark> joseogando_: if you are interested, here's the diff https://clbin.com/LVg8z. 
[18:35] <atmark> I'll try annotations that you mentioned 
[18:35] <atmark> Thanks for the pointers 
[18:38] <joseogando_> I see. I am not an expert debugging this kind of issues. If you go by the premise that it is a config option, then you can try what I suggested. In the surface none of the +/- changes seem to be relevant or specific for kvm scenarios.
[19:02] <atmark> Yeah. I'll update launchpad for any findings.