From: Thomas Huth <thuth@redhat.com>
To: Alexandr Moshkov <dtalexundeer@yandex-team.ru>, qemu-devel@nongnu.org
Cc: "Cleber Rosa" <crosa@redhat.com>,
"yc-core @ yandex-team . ru" <yc-core@yandex-team.ru>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v6 2/2] tests/functional: add memlock tests
Date: Wed, 21 May 2025 14:06:27 +0200 [thread overview]
Message-ID: <5f154235-5777-4349-971b-e9fdfecba065@redhat.com> (raw)
In-Reply-To: <20250417114008.169350-3-dtalexundeer@yandex-team.ru>
On 17/04/2025 13.40, Alexandr Moshkov wrote:
> Add new tests to check the correctness of the `-overcommit memlock`
> option (possible values: off, on, on-fault) by using
> `/proc/{qemu_pid}/smaps` file to check in Size, Rss and Locked fields of
> anonymous segments:
>
> * if `memlock=off`, then Locked = 0 on every anonymous smaps;
> * if `memlock=on`, then Size, Rss and Locked values must be equal for
> every anon smaps where Rss is not 0;
> * if `memlock=on-fault`, then Rss and Locked must be equal on every anon
> smaps and anonymous segment with Rss < Size must exists.
>
> Signed-off-by: Alexandr Moshkov <dtalexundeer@yandex-team.ru>
> ---
> tests/functional/meson.build | 1 +
> tests/functional/test_memlock.py | 104 +++++++++++++++++++++++++++++++
> 2 files changed, 105 insertions(+)
> create mode 100755 tests/functional/test_memlock.py
>
> diff --git a/tests/functional/meson.build b/tests/functional/meson.build
> index 0f8be30fe2..339af7835f 100644
> --- a/tests/functional/meson.build
> +++ b/tests/functional/meson.build
> @@ -61,6 +61,7 @@ tests_generic_system = [
> 'empty_cpu_model',
> 'info_usernet',
> 'version',
> + 'memlock',
> ]
>
> tests_generic_linuxuser = [
> diff --git a/tests/functional/test_memlock.py b/tests/functional/test_memlock.py
> new file mode 100755
> index 0000000000..eaf3d46dec
> --- /dev/null
> +++ b/tests/functional/test_memlock.py
> @@ -0,0 +1,104 @@
> +#!/usr/bin/env python3
> +#
> +# Functional test that check overcommit memlock options
> +#
> +# Copyright (c) Yandex Technologies LLC, 2025
> +#
> +# Author:
> +# Alexandr Moshkov <dtalexundeer@yandex-team.ru>
> +#
> +#
> +# This work is licensed under the terms of the GNU GPL, version 2 or
> +# later. See the COPYING file in the top-level directory.
> +
> +import re
> +
> +from typing import List, Dict
> +
> +from qemu_test import QemuSystemTest
> +from qemu_test import skipLockedMemoryTest
> +
> +
> +SMAPS_HEADER_PATTERN = re.compile(r'^\w+-\w+', re.MULTILINE)
> +SMAPS_VALUE_PATTERN = re.compile(r'^(\w+):\s+(\d+) kB', re.MULTILINE)
> +
> +
> +@skipLockedMemoryTest(2_097_152) # 2GB
> +class MemlockTest(QemuSystemTest):
> + """
> + Boots a Linux system with memlock options.
> + Then verify, that this options is working correctly
> + by checking the smaps of the QEMU proccess.
> + """
> +
> + def common_vm_setup_with_memlock(self, memlock):
> + self.vm.add_args('-overcommit', f'mem-lock={memlock}')
> + self.vm.launch()
> +
> + def get_anon_smaps_by_pid(self, pid):
> + smaps_raw = self._get_raw_smaps_by_pid(pid)
> + return self._parse_anonymous_smaps(smaps_raw)
> +
> + def test_memlock_off(self):
> + self.common_vm_setup_with_memlock('off')
> +
> + anon_smaps = self.get_anon_smaps_by_pid(self.vm.get_pid())
> +
> + # locked = 0 on every smap
> + for smap in anon_smaps:
> + self.assertEqual(smap['Locked'], 0)
> +
> + def test_memlock_on(self):
> + self.common_vm_setup_with_memlock('on')
> +
> + anon_smaps = self.get_anon_smaps_by_pid(self.vm.get_pid())
> +
> + # size = rss = locked on every smap where rss not 0
> + for smap in anon_smaps:
> + if smap['Rss'] == 0:
> + continue
> + self.assertTrue(smap['Size'] == smap['Rss'] == smap['Locked'])
> +
> + def test_memlock_onfault(self):
> + self.common_vm_setup_with_memlock('on-fault')
> +
> + anon_smaps = self.get_anon_smaps_by_pid(self.vm.get_pid())
> +
> + # rss = locked on every smap and segment with rss < size exists
> + exists = False
> + for smap in anon_smaps:
> + self.assertTrue(smap['Rss'] == smap['Locked'])
> + if smap['Rss'] < smap['Size']:
> + exists = True
> + self.assertTrue(exists)
> +
> + def _parse_anonymous_smaps(self, smaps_raw: str) -> List[Dict[str, int]]:
> + result_segments = []
> + current_segment = {}
> + is_anonymous = False
> +
> + for line in smaps_raw.split('\n'):
> + if SMAPS_HEADER_PATTERN.match(line):
> + if current_segment and is_anonymous:
> + result_segments.append(current_segment)
> + current_segment = {}
> + # anonymous segment header looks like this:
> + # 7f3b8d3f0000-7f3b8d3f3000 rw-s 00000000 00:0f 1052
> + # and non anonymous header looks like this:
> + # 7f3b8d3f0000-7f3b8d3f3000 rw-s 00000000 00:0f 1052 [stack]
> + is_anonymous = len(line.split()) == 5
> + elif m := SMAPS_VALUE_PATTERN.match(line):
> + current_segment[m.group(1)] = int(m.group(2))
> +
> + if current_segment and is_anonymous:
> + result_segments.append(current_segment)
> +
> + return result_segments
> +
> + def _get_raw_smaps_by_pid(self, pid: int) -> str:
> + with open(f'/proc/{pid}/smaps', 'r') as f:
> + return f.read()
The patch looks basically fine to me, but here you should consider that this
might be running on a non-Linux system, too, I think. So in case the open()
fails, just do a self.skipTest() ?
Thomas
next prev parent reply other threads:[~2025-05-21 12:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 11:40 [PATCH v6 0/2] tests/functional: add memlock tests Alexandr Moshkov
2025-04-17 11:40 ` [PATCH v6 1/2] tests/functional: add skipLockedMemoryTest decorator Alexandr Moshkov
2025-05-21 10:25 ` Thomas Huth
2025-04-17 11:40 ` [PATCH v6 2/2] tests/functional: add memlock tests Alexandr Moshkov
2025-05-21 12:06 ` Thomas Huth [this message]
2025-04-28 9:34 ` [PATCH v6 0/2] " Alexandr Moshkov
2025-05-21 8:52 ` Alexandr Moshkov
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=5f154235-5777-4349-971b-e9fdfecba065@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=dtalexundeer@yandex-team.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yc-core@yandex-team.ru \
/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;
as well as URLs for NNTP newsgroup(s).