Messages in this thread | | | From | Aneesh Kumar K.V <> | Subject | Re: [PATCH 10/13] powerpc: Define KMSAN metadata address ranges for vmalloc and ioremap | Date | Fri, 15 Dec 2023 14:57:42 +0530 |
| |
Nicholas Miehlbradt <nicholas@linux.ibm.com> writes:
> Splits the vmalloc region into four. The first quarter is the new > vmalloc region, the second is used to store shadow metadata and the > third is used to store origin metadata. The fourth quarter is unused. >
Do we support KMSAN for both hash and radix? If hash is not supported can we then using radix.h for these changes?
> Do the same for the ioremap region. > > Module data is stored in the vmalloc region so alias the modules > metadata addresses to the respective vmalloc metadata addresses. Define > MODULES_VADDR and MODULES_END to the start and end of the vmalloc > region. > > Since MODULES_VADDR was previously only defined on ppc32 targets checks > for if this macro is defined need to be updated to include > defined(CONFIG_PPC32).
-aneesh
| |