Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Catalin Marinas <catalin.marinas@arm.com>
To:     Kefeng Wang <wangkefeng.wang@huawei.com>,
        Will Deacon <will@kernel.org>
Cc:     linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
        Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH Resend] arm64: support huge vmalloc mappings
Date:   Fri, 16 Sep 2022 18:46:57 +0100
Message-Id: <166335041341.1745039.7832892375837792133.b4-ty@arm.com>
In-Reply-To: <20220911044423.139229-1-wangkefeng.wang@huawei.com>
References: <Yxt6HbbWEqnteYHb@arm.com> <20220911044423.139229-1-wangkefeng.wang@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Sun, 11 Sep 2022 12:44:23 +0800, Kefeng Wang wrote:
> As commit 559089e0a93d ("vmalloc: replace VM_NO_HUGE_VMAP with
> VM_ALLOW_HUGE_VMAP"), the use of hugepage mappings for vmalloc
> is an opt-in strategy, so it is saftly to support huge vmalloc
> mappings on arm64, for now, it is used in kvmalloc() and
> alloc_large_system_hash().
> 
> 
> [...]

Applied to arm64 (for-next/misc), thanks!

[1/1] arm64: support huge vmalloc mappings
      https://git.kernel.org/arm64/c/e92072237e6c

-- 
Catalin