The linux/arch MC aims to bring architecture maintainers in one room to discuss how can we improve architecture specific code and its integration with the generic kernel
There was a time when the Linux kernel was 32bit but hardware systems had much
more than 1GB of memory. A solution was developed to allow the use of high
memory (HIGHMEM). High memory was excluded from the kernel direct map and was
temporarily mapped into and out of the kernel as needed. These mappings were
made via kmap_*() calls.
With the prevalence of 64bit kernels the usefulness...
In this talk we will argue the case for adopting ASI in upstream Linux.
Speculative execution attacks, such as L1TF, MDS, LVI, (and many others) pose significant security risks to hypervisors and VMs, from neighboring malicious VMs. The sheer number of proposed patches/fixes is quite high, each with its own non-trivial impact on performance. A complete mitigation for these attacks...
We have several coarse representations of the physical memory consisting of
[start, end, flags] structures per memory region. There is memblock that
some architectures keep after boot, there is iomem_resource tree and
"System RAM" nodes in that tree, there are memory blocks exposed in sysfs
and then there are per-architecture structures, sometimes even several per
- cleaner way forward for compatibility with the "old-world" (the
earlier in-house MIPS-clone firmware and kernel ABI of LoongArch), if
- cleaner approach to support both standard UEFI and the Loongson-custom
boot protocols, if possible;
- way forward for supporting zboot in EFI stub boot flow.
An overview will be presented of recent work in the Linux/EFI
subsystem and associated projects (u-boot, Tianocore, systemd), with a
focus on generic support for the various new architectures that have
adopted EFI as a supported boot flow. This includes UEFI secure boot
and/or measured boot on non-Tianocore based EFI implementations,
generic decompressor support in Linux and early...
For the architecture that uses load-link/store-conditional to implement atomic semantics, ll/sc can effectively reduce the complexity and cost of embedded processors and is very attractive for products with up to two cores in a single cluster. However, compared with the AMO architecture, it may not have enough forward guarantee, causing the risk of livelock. Therefore, CPUs based on the ll/sc...