<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in access_memory.c</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>34ec4344 - selftests/damon/access_memory: use user-defined region size</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/damon/access_memory.c#34ec4344</link>
        <description>selftests/damon/access_memory: use user-defined region sizePatch series &quot;selftests/damon: test DAMOS tried regions and{min,max}_nr_regions&quot;.This patch series fix a minor issue in a program for DAMON selftest, andimplement new functionality selftests for DAMOS tried regions and{min,max}_nr_regions.  The test for max_nr_regions also test the recoveryfrom online tuning-caused limit violation, which was fixed by a previouspatch [1] titled &quot;mm/damon/core: merge regions aggressively whenmax_nr_regions is unmet&quot;.The first patch fixes a minor problem in the articial memory accesspattern generator for tests.  Following 3 patches (2-4) implement schemestried regions test.  Then a couple of patches (5-6) implementing staticsetup based {min,max}_nr_regions functionality test follows.  Final twopatches (7-8) implement dynamic max_nr_regions update test.[1] https://lore.kernel.org/20240624210650.53960C2BBFC@smtp.kernel.orgThis patch (of 8):&apos;access_memory&apos; is an artificial memory access pattern generator for DAMONtests.  It creates and accesses memory regions that the user specified thenumber and size via the command line.  However, real access part of theprogram ignores the user-specified size of each region.  Instead, it usesa hard-coded value, 10 MiB.  Fix it to use user-defined size.Note that all existing &apos;access_memory&apos; users are setting the region sizeas 10 MiB.  Hence no real problem has happened so far.Link: https://lkml.kernel.org/r/20240625180538.73134-1-sj@kernel.orgLink: https://lkml.kernel.org/r/20240625180538.73134-2-sj@kernel.orgFixes: b5906f5f7359 (&quot;selftests/damon: add a test for update_schemes_tried_regions sysfs command&quot;)Signed-off-by: SeongJae Park &lt;sj@kernel.org&gt;Cc: Shuah Khan &lt;shuah@kernel.org&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/damon/access_memory.c</description>
        <pubDate>Tue, 25 Jun 2024 18:05:31 +0000</pubDate>
        <dc:creator>SeongJae Park &lt;sj@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>b5906f5f - selftests/damon: add a test for update_schemes_tried_regions sysfs command</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/selftests/damon/access_memory.c#b5906f5f</link>
        <description>selftests/damon: add a test for update_schemes_tried_regions sysfs commandAdd a selftest for verifying the accuracy of DAMON&apos;s access monitoringfunctionality.  The test starts a program of artificial access pattern,monitor the access pattern using DAMON, and check if DAMON finds expectedamount of hot data region (working set size) with only acceptable errorrate.Note that the acceptable error rate is set with only naive assumptions andsmall number of tests.  Hence failures of the test may not always meanDAMON is broken.  Rather than that, those could be a signal to betterunderstand the real accuracy level of DAMON in wider environments.  Basedon further finding, we could optimize DAMON or adjust the expectation ofthe test.Link: https://lkml.kernel.org/r/20231212194810.54457-5-sj@kernel.orgSigned-off-by: SeongJae Park &lt;sj@kernel.org&gt;Cc: Shuah Khan &lt;shuah@kernel.org&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

            List of files:
            /linux-6.15/tools/testing/selftests/damon/access_memory.c</description>
        <pubDate>Tue, 12 Dec 2023 19:48:09 +0000</pubDate>
        <dc:creator>SeongJae Park &lt;sj@kernel.org&gt;</dc:creator>
    </item>
</channel>
</rss>
