All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <ljs@kernel.org>
To: Dev Jain <dev.jain@arm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	 David Hildenbrand <david@kernel.org>, Zi Yan <ziy@nvidia.com>,
	 Baolin Wang <baolin.wang@linux.alibaba.com>,
	"Liam R . Howlett" <liam@infradead.org>,
	 Nico Pache <npache@redhat.com>,
	Ryan Roberts <ryan.roberts@arm.com>,
	 Barry Song <baohua@kernel.org>,
	Lance Yang <lance.yang@linux.dev>, SeongJae Park <sj@kernel.org>,
	 Balbir Singh <balbirs@nvidia.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH mm-hotfixes] mm/huge_memory: use correct flags for device private PMD entry
Date: Fri, 5 Jun 2026 11:07:26 +0100	[thread overview]
Message-ID: <aiKficIP-akvSQAf@lucifer> (raw)
In-Reply-To: <73762983-d48d-486f-ad5f-78015e6f95ee@arm.com>

By the way,

I think maybe the reason you didn't hit this in your work on the spurious
warning stuff for hmm-tests is that I also had to set CONFIG_DEVICE_PRIVATE
(as well as CONFIG_TEST_HMM) to get this to trigger.

I think the reason others maybe didn't see it is because the self tests
will just skip the hmm tests if CONFIG_TEST_HMM is not set.

Cheers, Lorenzo


  reply	other threads:[~2026-06-05 10:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01  8:30 [PATCH mm-hotfixes] mm/huge_memory: use correct flags for device private PMD entry Lorenzo Stoakes
2026-06-01  8:55 ` Lorenzo Stoakes
2026-06-01 12:17   ` David Hildenbrand (Arm)
2026-06-01 15:50 ` Dev Jain
2026-06-01 15:56   ` David Hildenbrand (Arm)
2026-06-01 16:03     ` Lorenzo Stoakes
2026-06-01 16:01   ` Lorenzo Stoakes
2026-06-01 16:27     ` Dev Jain
2026-06-01 16:44 ` Dev Jain
2026-06-05 10:07   ` Lorenzo Stoakes [this message]
2026-06-05 13:22     ` Dev Jain
2026-06-01 20:30 ` Balbir Singh
2026-06-02  9:17   ` Lorenzo Stoakes
2026-06-02  3:29 ` Baolin Wang
2026-06-02  4:09 ` Oscar Salvador (SUSE)
2026-06-02  4:38 ` Barry Song
2026-06-02  6:32 ` Lance Yang
2026-06-02 14:40 ` Zi Yan
2026-06-02 17:26   ` Lorenzo Stoakes

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=aiKficIP-akvSQAf@lucifer \
    --to=ljs@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=balbirs@nvidia.com \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=lance.yang@linux.dev \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npache@redhat.com \
    --cc=ryan.roberts@arm.com \
    --cc=sj@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.