mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Lukas Bulwahn <lbulwahn@redhat.com>
Cc: <dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Concurrent Kconfig renaming, impacting your commit "drm/pagemap: Guard HPAGE_PMD_ORDER use with CONFIG_ARCH_ENABLE_THP_MIGRATION"
Date: Thu, 23 Jul 2026 12:42:55 -0700	[thread overview]
Message-ID: <amJuv+Icq1fs2wym@gsse-cloud1.jf.intel.com> (raw)
In-Reply-To: <CAOc5a3NBcpJnjB=Tv3+tjFoD5aJe4dUTH7qmTFom2z7-eDQiqw@mail.gmail.com>

On Thu, Jul 23, 2026 at 09:12:26AM +0200, Lukas Bulwahn wrote:
> Hi Matthew,
> 
> I noticed that the commit 0b6b1bb28482 ("mm: rename
> ARCH_ENABLE_THP_MIGRATION to ARCH_HAS_PMD_SOFTLEAVES") on linux-next
> renames the config option ARCH_ENABLE_THP_MIGRATION, which is referred
> to in this recent commit 04b177544a040 ("drm/pagemap: Guard
> HPAGE_PMD_ORDER use with CONFIG_ARCH_ENABLE_THP_MIGRATION").
> 
> You might want to have a look at that.
> 

Thanks, I saw some discussion on a linux-next merge conflict about this.

I think I can just do this in DRM to avoid the conflict + work with and
without 0b6b1bb28482.

-#if IS_ENABLED(CONFIG_ARCH_ENABLE_THP_MIGRATION)
+#if IS_ENABLED(CONFIG_PGTABLE_HAS_HUGE_LEAVES)
#define DRM_PAGEMAP_PMD_ORDER        HPAGE_PMD_ORDER
#else
#define DRM_PAGEMAP_PMD_ORDER        (-1)

Need to  look at linux-next or core MM branches to confirm before I
post anything though to confirm.

Matt

> Best regards,
> 
> Lukas
> 

      reply	other threads:[~2026-07-23 19:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23  7:12 Lukas Bulwahn
2026-07-23 19:42 ` Matthew Brost [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=amJuv+Icq1fs2wym@gsse-cloud1.jf.intel.com \
    --to=matthew.brost@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lbulwahn@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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
all inboxes | Powered by JetHome®