linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
	linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, kernel-team@android.com,
	Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
	rcampbell@nvidia.com, akpm@linux-foundation.org,
	Mark Rutland <mark.rutland@arm.com>,
	Jonathan.Cameron@Huawei.com, linux-kernel@vger.kernel.org,
	Suzuki Poulose <suzuki.poulose@arm.com>,
	ziy@nvidia.com
Subject: Re: [PATCH V2 0/2] arm64/mm: Enable THP migration
Date: Fri, 11 Sep 2020 16:31:48 +0100	[thread overview]
Message-ID: <159983265112.1321153.11672723276282744978.b4-ty@kernel.org> (raw)
In-Reply-To: <1599627183-14453-1-git-send-email-anshuman.khandual@arm.com>

On Wed, 9 Sep 2020 10:23:01 +0530, Anshuman Khandual wrote:
> This series enables THP migration on arm64 via ARCH_ENABLE_THP_MIGRATION.
> But first this modifies all existing THP helpers like pmd_present() and
> pmd_trans_huge() etc per expected generic memory semantics as concluded
> from a previous discussion here.
> 
> https://lkml.org/lkml/2018/10/9/220
> 
> [...]

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

[1/2] arm64/mm: Change THP helpers to comply with generic MM semantics
      https://git.kernel.org/arm64/c/b65399f6111b
[2/2] arm64/mm: Enable THP migration
      https://git.kernel.org/arm64/c/53fa117bb33c

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev


      parent reply	other threads:[~2020-09-11 15:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09  4:53 Anshuman Khandual
2020-09-09  4:53 ` [PATCH V2 1/2] arm64/mm: Change THP helpers to comply with generic MM semantics Anshuman Khandual
2020-09-09  4:53 ` [PATCH V2 2/2] arm64/mm: Enable THP migration Anshuman Khandual
2020-09-11 15:31 ` Will Deacon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=159983265112.1321153.11672723276282744978.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=Jonathan.Cameron@Huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=rcampbell@nvidia.com \
    --cc=suzuki.poulose@arm.com \
    --cc=ziy@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox