On 09.08.2019 15:42, Andrew Cooper wrote:
On 09/08/2019 13:32, Jan Beulich wrote:
Insert explicit alignment such that the result is safe even with objects
shorter than a page in length. The POINTER_ALIGN for __bss_end is to
cover
the lack of SMP_CACHE_BYTES alignment, as the loops which zero th
On 09/08/2019 13:32, Jan Beulich wrote:
> Insert explicit alignment such that the result is safe even with objects
> shorter than a page in length. The POINTER_ALIGN for __bss_end is to
> cover
> the lack of SMP_CACHE_BYTES alignment, as the loops which zero the BSS
> use
> pointer-sized stores on
From: Andrew Cooper
Future changes are going to need to page align some percpu data.
Shuffle the exact link order of items within the BSS to give
.bss.percpu.page_aligned appropriate alignment, even on CPU0, which uses
.bss.percpu itself.
Insert explicit alignment such that the result is safe
