linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Ryan Roberts <ryan.roberts@arm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH v1] mm/debug_vm_pgtable: Test pmd_leaf() behavior with pmd_mkinvalid()
Date: Thu, 2 May 2024 13:33:09 +0530	[thread overview]
Message-ID: <2128d3d7-0dc4-4e81-a1e2-a8a67f0d36ed@arm.com> (raw)
In-Reply-To: <c0225698-27aa-4c2a-928d-e3d919437ab2@arm.com>



On 5/2/24 13:00, Ryan Roberts wrote:
> On 02/05/2024 03:43, Anshuman Khandual wrote:
>> Hello Ryan,
>>
>> On 5/1/24 20:14, Ryan Roberts wrote:
>>> An invalidated pmd should still cause pmd_leaf() to return true. Let's
>>> test for that to ensure all arches remain consistent.
>>
>> This test definitely makes sense.
>>
>>>
>>> Signed-off-by: Ryan Roberts <ryan.roberts@arm.com>
>>> ---
>>>
>>> Hi Andrew,
>>>
>>> This applies on top of v6.9-rc5. It came out of a discussion with Catalin around
>>> the pmd_mkinvalid() bug (the fix for which I just posted). I've run the new test
>>> on both arm64 and x86_64.
>>
>> Right, works on arm64.
>>
>>>
>>> Thanks,
>>> Ryan
>>>
>>>  mm/debug_vm_pgtable.c | 1 +
>>>  1 file changed, 1 insertion(+)
>>>
>>> diff --git a/mm/debug_vm_pgtable.c b/mm/debug_vm_pgtable.c
>>> index 65c19025da3d..57e9cb0820ab 100644
>>> --- a/mm/debug_vm_pgtable.c
>>> +++ b/mm/debug_vm_pgtable.c
>>> @@ -981,6 +981,7 @@ static void __init pmd_thp_tests(struct pgtable_debug_args *args)
>>>  #ifndef __HAVE_ARCH_PMDP_INVALIDATE
>>>  	WARN_ON(!pmd_trans_huge(pmd_mkinvalid(pmd_mkhuge(pmd))));
>>>  	WARN_ON(!pmd_present(pmd_mkinvalid(pmd_mkhuge(pmd))));
>>> +	WARN_ON(!pmd_leaf(pmd_mkinvalid(pmd_mkhuge(pmd))));
>>>  #endif /* __HAVE_ARCH_PMDP_INVALIDATE */
>>>  }
>>
>> Should not we update descriptions in Documentation/mm/arch_pgtable_helpers.rst
>> asserting that pmd_mkinvalid() also preserves pmd_leaf() ?
> 
> Thanks for the review!
> 
> We don't document that pmd_mkinvalid() preserves pmd_present() and
> pmd_trans_huge() so I wasn't sure how much detail was appropriate in that
> document - its pretty light at the moment.

For all other helpers documentation has been light but pxd_mkinvalid() is turning
out to be a special case though.

> 
> If you think this is valuable (and isn't clear enough from the test) then I can
> add something. But as you say in the other patch, it would then start
> conflicting with that. I'd prefer to just put this in as-is to avoid the mess.

Sure, fair enough. I will try and update how pmd_mkinvalid() preserves pmd_leaf(),
pmd_present(), and pmd_trans_huge() at a later point. Otherwise this patch itself
LGTM and runs fine on arm64.

Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>


  reply	other threads:[~2024-05-02  8:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01 14:44 Ryan Roberts
2024-05-02  2:43 ` Anshuman Khandual
2024-05-02  7:30   ` Ryan Roberts
2024-05-02  8:03     ` Anshuman Khandual [this message]
2024-05-02  8:20       ` Ryan Roberts
2024-05-02 13:10 ` David Hildenbrand

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=2128d3d7-0dc4-4e81-a1e2-a8a67f0d36ed@arm.com \
    --to=anshuman.khandual@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-mm@kvack.org \
    --cc=ryan.roberts@arm.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