c734aad7ce
Updating to the latest korg -stable release that comprises
the following commits:
0a4a7855302d Linux 6.1.44
dd5f2ef16e3c x86: fix backwards merge of GDS/SRSO bit
fa5b932b77c8 xen/netback: Fix buffer overrun triggered by unusual packet
4f25355540ad x86/srso: Tie SBPB bit setting to microcode patch detection
77cf32d0dbfb x86/srso: Add a forgotten NOENDBR annotation
c7f2cd045542 x86/srso: Fix return thunks in generated code
c9ae63d773ca x86/srso: Add IBPB on VMEXIT
79c8091888ef x86/srso: Add IBPB
98f62883e751 x86/srso: Add SRSO_NO support
9139f4b6dd4f x86/srso: Add IBPB_BRTYPE support
ac41e90d8daa x86/srso: Add a Speculative RAS Overflow mitigation
dec3b91f2c4b x86/cpu, kvm: Add support for CPUID_80000021_EAX
dfede4cb8ef7 x86/bugs: Increase the x86 bugs vector size to two u32s
dacb0bac2edb Documentation/x86: Fix backwards on/off logic about YMM support
051f5dcf144a x86/mm: Initialize text poking earlier
e0fd83a193c5 mm: Move mm_cachep initialization to mm_init()
9ae15aaff39c x86/mm: Use mm_alloc() in poking_init()
d972c8c08f96 x86/mm: fix poking_init() for Xen PV guests
7f3982de36c6 x86/xen: Fix secondary processors' FPU initialization
baa7b7501e41 x86/mem_encrypt: Unbreak the AMD_MEM_ENCRYPT=n build
b6fd07c41b4c KVM: Add GDS_NO support to KVM
c04579e95492 x86/speculation: Add Kconfig option for GDS
92fc27c79bc7 x86/speculation: Add force option to GDS mitigation
c66ebe070d96 x86/speculation: Add Gather Data Sampling mitigation
f25ad76d9217 x86/fpu: Move FPU initialization into arch_cpu_finalize_init()
e26932942b2c x86/fpu: Mark init functions __init
9e8d9d399094 x86/fpu: Remove cpuinfo argument from init functions
c956807d8462 x86/init: Initialize signal frame size late
b0837880fa65 init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init()
8183a89caf67 init: Invoke arch_cpu_finalize_init() earlier
a3342c60dcc5 init: Remove check_bugs() leftovers
8beabde0ed8d um/cpu: Switch to arch_cpu_finalize_init()
ce97072e10cc sparc/cpu: Switch to arch_cpu_finalize_init()
84f585542ec6 sh/cpu: Switch to arch_cpu_finalize_init()
6a90583dbd9b mips/cpu: Switch to arch_cpu_finalize_init()
489ae02c8993 m68k/cpu: Switch to arch_cpu_finalize_init()
08e86d42e2c9 loongarch/cpu: Switch to arch_cpu_finalize_init()
403e4cc67e4c ia64/cpu: Switch to arch_cpu_finalize_init()
e2e06240ae47 ARM: cpu: Switch to arch_cpu_finalize_init()
7918a3555a25 x86/cpu: Switch to arch_cpu_finalize_init()
d5501f2ff80d init: Provide arch_cpu_finalize_init()
(From OE-Core rev: c8b669d53b3444191c83f171768b03f96913f4eb)
(From OE-Core rev: ee0f9bb134ed2167bd014aaa0fafa551215a6f28)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
The project works using a mailing list patch submission process. Patches should be sent to the mailing list for the repository the components originate from (see below). Throughout the Yocto Project, the README files in the component in question should detail where to send patches, who the maintainers are and where bugs should be reported.
A guide to submitting patches to OpenEmbedded is available at:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
There is good documentation on how to write/format patches at:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.