Le 04/07/2022 à 09:55, Christophe Leroy a écrit :
Le 04/07/2022 à 09:45, Aneesh Kumar K V a écrit :
On 7/4/22 12:43 PM, Christophe Leroy wrote:
Le 04/07/2022 à 08:39, Aneesh Kumar K.V a écrit :
Instead of high_memory use is_vmalloc_addr to validate that the
address is
not in the vmallo
Le 04/07/2022 à 09:45, Aneesh Kumar K V a écrit :
> On 7/4/22 12:43 PM, Christophe Leroy wrote:
>>
>>
>> Le 04/07/2022 à 08:39, Aneesh Kumar K.V a écrit :
>>> Instead of high_memory use is_vmalloc_addr to validate that the address is
>>> not in the vmalloc range.
>>
>>
>> Do we really need even m
On 7/4/22 12:43 PM, Christophe Leroy wrote:
>
>
> Le 04/07/2022 à 08:39, Aneesh Kumar K.V a écrit :
>> Instead of high_memory use is_vmalloc_addr to validate that the address is
>> not in the vmalloc range.
>
>
> Do we really need even more extra checks, and a function that is not
> inlined an
Le 04/07/2022 à 08:39, Aneesh Kumar K.V a écrit :
> Instead of high_memory use is_vmalloc_addr to validate that the address is
> not in the vmalloc range.
Do we really need even more extra checks, and a function that is not
inlined anymore ?
virt_addr_valid() used to be pretty simple. Some ex
Instead of high_memory use is_vmalloc_addr to validate that the address is
not in the vmalloc range.
Cc: Kefeng Wang
Cc: Christophe Leroy
Signed-off-by: Aneesh Kumar K.V
-
---
arch/powerpc/include/asm/page.h | 10 --
arch/powerpc/mm/mem.c | 11 +++
2 files changed, 15
