[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251119054428.GC19925@lst.de>
Date: Wed, 19 Nov 2025 06:44:28 +0100
From: Christoph Hellwig <hch@....de>
To: Nathan Chancellor <nathan@...nel.org>
Cc: "Vishal Moola (Oracle)" <vishal.moola@...il.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
bpf@...r.kernel.org, Uladzislau Rezki <urezki@...il.com>,
Christoph Hellwig <hch@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Christoph Hellwig <hch@....de>, kvmarm@...ts.linux.dev
Subject: Re: [PATCH v3 1/4] mm/vmalloc: warn on invalid vmalloc gfp flags
On Tue, Nov 18, 2025 at 03:44:48PM -0700, Nathan Chancellor wrote:
> where kvm_arch_alloc_vm() from arch/arm64/kvm/arm.c is
>
> struct kvm *kvm_arch_alloc_vm(void)
> {
> size_t sz = sizeof(struct kvm);
>
> if (!has_vhe())
> return kzalloc(sz, GFP_KERNEL_ACCOUNT);
>
> return __vmalloc(sz, GFP_KERNEL_ACCOUNT | __GFP_HIGHMEM | __GFP_ZERO);
> }
>
> Should __GFP_HIGHMEM be dropped from the call to __vmalloc?
Yes. vmalloc uses highmem internally where useful (on arm64 it won't be
useful of course).
Powered by blists - more mailing lists