22caf0ce33
Updating to the latest korg -stable release that comprises
the following commits:
de5f63612d16 Linux 5.10.189
2ae9a73819a7 x86: fix backwards merge of GDS/SRSO bit
f9167a2d6b94 xen/netback: Fix buffer overrun triggered by unusual packet
8457fb5740b1 x86/srso: Tie SBPB bit setting to microcode patch detection
4873939c0e1c x86/srso: Fix return thunks in generated code
384d41bea948 x86/srso: Add IBPB on VMEXIT
4acaea47e3bc x86/srso: Add IBPB
e47af0c255ae x86/srso: Add SRSO_NO support
df76a59feba5 x86/srso: Add IBPB_BRTYPE support
3f9b7101bea1 x86/srso: Add a Speculative RAS Overflow mitigation
34f23ba8a399 x86/cpu, kvm: Add support for CPUID_80000021_EAX
073a28a9b506 x86/bugs: Increase the x86 bugs vector size to two u32s
9b7fe7c6fbc0 tools headers cpufeatures: Sync with the kernel sources
437fa179f213 x86/cpufeatures: Assign dedicated feature word for CPUID_0x8000001F[EAX]
baf6d6c39e23 x86/cpu: Add VM page flush MSR availablility as a CPUID feature
675046878431 Documentation/x86: Fix backwards on/off logic about YMM support
79972c2b95ec x86/mm: Initialize text poking earlier
1ff14defdfc9 mm: Move mm_cachep initialization to mm_init()
6ee042fd240f x86/mm: Use mm_alloc() in poking_init()
f076d0817878 x86/mm: fix poking_init() for Xen PV guests
583016037a09 x86/xen: Fix secondary processors' FPU initialization
eb13cce48874 KVM: Add GDS_NO support to KVM
7db4ddcb8d8e x86/speculation: Add Kconfig option for GDS
363c98f9cfa8 x86/speculation: Add force option to GDS mitigation
288a2f6bc1ce x86/speculation: Add Gather Data Sampling mitigation
4ae1cbb730bd x86/fpu: Move FPU initialization into arch_cpu_finalize_init()
2462bc3ef061 x86/fpu: Mark init functions __init
7a2f42bce9ab x86/fpu: Remove cpuinfo argument from init functions
18fcd72da1ed init, x86: Move mem_encrypt_init() into arch_cpu_finalize_init()
09658b81d158 init: Invoke arch_cpu_finalize_init() earlier
bf2fa3a9d0e6 init: Remove check_bugs() leftovers
b05031c2bca7 um/cpu: Switch to arch_cpu_finalize_init()
2edb3b39ca79 sparc/cpu: Switch to arch_cpu_finalize_init()
3c45134b38b4 sh/cpu: Switch to arch_cpu_finalize_init()
75bb54c951e9 mips/cpu: Switch to arch_cpu_finalize_init()
1cd3fc18eb16 m68k/cpu: Switch to arch_cpu_finalize_init()
12d93c6c98d5 ia64/cpu: Switch to arch_cpu_finalize_init()
c0fff20d4efa ARM: cpu: Switch to arch_cpu_finalize_init()
e5eb18e164d0 x86/cpu: Switch to arch_cpu_finalize_init()
6e606e681873 init: Provide arch_cpu_finalize_init()
(From OE-Core rev: f674e44ff69a1e51c4b6929d195ce0a110577c12)
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.