summaryrefslogtreecommitdiffstats
path: root/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@gmail.com>2024-02-26 17:34:49 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2024-02-27 14:31:36 +0000
commitc95aa38d24e467649038aa2b7dbbadaed6c86c99 (patch)
treed421120d39c132a244f0ab9533c5eb4720e75580 /meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
parenteb54ef787d84e630faf96728138dd76c775c7e94 (diff)
downloadpoky-c95aa38d24e467649038aa2b7dbbadaed6c86c99.tar.gz
linux-yocto/6.6: config: x86 tidy & consolidation
Integrating the following commit(s) to linux-yocto/.: 1/3 [ Author: Paul Gortmaker Email: paul.gortmaker@windriver.com Subject: BSP: remove from all - latencytop feature inclusion Date: Thu, 30 Nov 2023 14:07:48 -0500 Consider this 5+ year old commit commit bcbc7bbc4fb967d8d4ae6333f71b73491a80b94e Author: Alexander Kanavin <alexander.kanavin@linux.intel.com> Date: Thu Mar 1 16:00:41 2018 +0200 latencytop: remove recipe Last commit and release were in 2009; website is down; it's a dead project. (From OE-Core rev: 36aae56e7f86a4d5ce93e4528e7dcc42f60c705e) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Given that, it seems sensible to drop it from default inclusion across the BSPs. I've left the feature itself, so anyone who still cares can easily manually add it still. Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> ] 2/3 [ Author: Paul Gortmaker Email: paul.gortmaker@windriver.com Subject: x86-64: separate out the NUMA features to our existing NUMA scc/cfg Date: Thu, 30 Nov 2023 14:07:45 -0500 A user reported getting NUMA warnings like the ones reported here: https://www.suse.com/support/kb/doc/?id=000021040 "Fail to get numa node for CPU:0 bus:0 dev:0 fn:1" ...and repeated for every core on the platform. Distracting. When I asked if it was a crazy big server system with multiple CPU sockets and localized RAM near each socket - the answer was "no". Turns out they didn't choose NUMA support - rather we did it for them. Yocto has been and still remains more "embedded leaning". That is not to say we can't support NUMA. We just shouldn't be enabling it by default in the base x86-64 config fragment that everyone uses. Move the two NUMA settings that were not in our existing numa.cfg feature out of the BSP and into the feature. Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> ] 3/3 [ Author: Paul Gortmaker Email: paul.gortmaker@windriver.com Subject: x86-64: consolidate crypto options Date: Thu, 30 Nov 2023 14:07:44 -0500 No functional change - just makes further reorganizations and refactoring more easy to review/parse. Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> ] (From OE-Core rev: e8ffc63f3ed61cc31c3077741f3f96dae9baa3fb) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-kernel/kern-tools/kern-tools-native_git.bb')
0 files changed, 0 insertions, 0 deletions