20c319e388
Updating to the latest korg -stable release that comprises
the following commits:
c275eaaaa342 Linux 5.15.125
754e0c7c4a30 x86: fix backwards merge of GDS/SRSO bit
b14a3924c267 xen/netback: Fix buffer overrun triggered by unusual packet
153f9a7b02d4 x86/srso: Tie SBPB bit setting to microcode patch detection
df4c3823cba5 x86/srso: Fix return thunks in generated code
0071b17eb66b x86/srso: Add IBPB on VMEXIT
5398faac76a6 x86/srso: Add IBPB
c24aaa7dde5f x86/srso: Add SRSO_NO support
4e9115e194a8 x86/srso: Add IBPB_BRTYPE support
b35087763a44 x86/srso: Add a Speculative RAS Overflow mitigation
c3b4c644525e x86/cpu, kvm: Add support for CPUID_80000021_EAX
236dd7133394 x86/bugs: Increase the x86 bugs vector size to two u32s
0242a8bdef56 Documentation/x86: Fix backwards on/off logic about YMM support
27a72e350869 x86/mm: Initialize text poking earlier
d0317b9502ea mm: Move mm_cachep initialization to mm_init()
8e4c2530879d x86/mm: Use mm_alloc() in poking_init()
13ec5cb4c113 x86/mm: fix poking_init() for Xen PV guests
3e90080d5665 x86/xen: Fix secondary processors' FPU initialization
348741a9e4d3 KVM: Add GDS_NO support to KVM
59d78655f808 x86/speculation: Add Kconfig option for GDS
0cc5643b63ae x86/speculation: Add force option to GDS mitigation
348a89e20184 x86/speculation: Add Gather Data Sampling mitigation
a094d3b30967 x86/fpu: Move FPU initialization into arch_cpu_finalize_init()
59f2739111ca x86/fpu: Mark init functions __init
bb9c20d903f6 x86/fpu: Remove cpuinfo argument from init functions
de8b7ce4c533 x86/init: Initialize signal frame size late
041d929233bb init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init()
8ae795ed6115 init: Invoke arch_cpu_finalize_init() earlier
7e270cebaffd init: Remove check_bugs() leftovers
285384ac24c3 um/cpu: Switch to arch_cpu_finalize_init()
6ea421786426 sparc/cpu: Switch to arch_cpu_finalize_init()
21a1fc8d13d8 sh/cpu: Switch to arch_cpu_finalize_init()
dfeb371a2707 mips/cpu: Switch to arch_cpu_finalize_init()
4baf46a3ba00 m68k/cpu: Switch to arch_cpu_finalize_init()
8c8165cd25cf ia64/cpu: Switch to arch_cpu_finalize_init()
de8c592cc5a1 ARM: cpu: Switch to arch_cpu_finalize_init()
75da6209d3ba x86/cpu: Switch to arch_cpu_finalize_init()
0774fc2177c3 init: Provide arch_cpu_finalize_init()
(From OE-Core rev: 50889a1a67a33d1d42f4095d323e4c73ca22c2c8)
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
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.