linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: "Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>,
	Shuah Khan <shuah@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: willy@infradead.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, gost.dev@samsung.com, mcgrof@kernel.org,
	linux-kselftest@vger.kernel.org, Zi Yan <zi.yan@sent.com>,
	Pankaj Raghav <p.raghav@samsung.com>
Subject: Re: [PATCH] selftests/mm: use volatile keyword to not optimize mmap read variable
Date: Thu, 6 Jun 2024 17:57:21 +0200	[thread overview]
Message-ID: <f199d120-2347-4bc0-8940-155c3c465de9@redhat.com> (raw)
In-Reply-To: <5b4e7ef2-3ced-4d4a-989c-e99b06598d32@redhat.com>

On 06.06.24 17:56, David Hildenbrand wrote:
> On 06.06.24 15:58, Pankaj Raghav (Samsung) wrote:
>> From: Pankaj Raghav <p.raghav@samsung.com>
>>
>> create_pagecache_thp_and_fd() in split_huge_page_test.c used the
>> variable dummy to perform mmap read.
>>
>> However, this test was skipped even on XFS which has large folio
>> support. The issue was compiler (gcc 13.2.0) was optimizing out the
>> dummy variable, therefore, not creating huge page in the page cache.
>>
>> Add volatile keyword to force compiler not to optimize out the loop
>> where we read from the mmaped addr.
>>
>> Signed-off-by: Pankaj Raghav <p.raghav@samsung.com>
>> ---
>>    tools/testing/selftests/mm/split_huge_page_test.c | 2 +-
>>    1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tools/testing/selftests/mm/split_huge_page_test.c b/tools/testing/selftests/mm/split_huge_page_test.c
>> index d3c7f5fb3e7b..c573a58f80ab 100644
>> --- a/tools/testing/selftests/mm/split_huge_page_test.c
>> +++ b/tools/testing/selftests/mm/split_huge_page_test.c
>> @@ -300,7 +300,7 @@ int create_pagecache_thp_and_fd(const char *testfile, size_t fd_size, int *fd,
>>    		char **addr)
>>    {
>>    	size_t i;
>> -	int __attribute__((unused)) dummy = 0;
>> +	volatile int __attribute__((unused)) dummy = 0;
>>    
>>    	srand(time(NULL));
>>    
>>
>> base-commit: d97496ca23a2d4ee80b7302849404859d9058bcd
> 
> The rick we do in some other tests is:
> 
> char *tmp;
> 
> tmp = *whatever;
> asm volatile("" : "+r" (tmp));

char tmp; of course. See cow.c as an example.

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2024-06-06 15:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 13:58 Pankaj Raghav (Samsung)
2024-06-06 14:21 ` Zi Yan
2024-06-06 14:35 ` Matthew Wilcox
2024-06-06 15:19   ` Zi Yan
2024-06-06 15:28   ` Pankaj Raghav (Samsung)
2024-06-06 15:56 ` David Hildenbrand
2024-06-06 15:57   ` David Hildenbrand [this message]
2024-06-06 20:18     ` Pankaj Raghav (Samsung)
2024-06-06 20:21       ` David Hildenbrand
2024-06-06 20:30         ` Pankaj Raghav (Samsung)

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=f199d120-2347-4bc0-8940-155c3c465de9@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=gost.dev@samsung.com \
    --cc=kernel@pankajraghav.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mcgrof@kernel.org \
    --cc=p.raghav@samsung.com \
    --cc=shuah@kernel.org \
    --cc=willy@infradead.org \
    --cc=zi.yan@sent.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