[PATCH v9 2/2] tests/functional: add memlock tests

2025-06-05 Thread Alexandr Moshkov
is resident; * if `memlock=on-fault`, then VmLck > 0 and only few memory is resident. Signed-off-by: Alexandr Moshkov --- tests/functional/meson.build | 1 + tests/functional/test_memlock.py | 79 2 files changed, 80 insertions(+) create mode 100755 tests/func

[PATCH v9 0/2] tests/functional: add memlock tests

2025-06-05 Thread Alexandr Moshkov
n (v2) So i resend previous patch with version specified. Alexandr Moshkov (2): tests/functional: add skipLockedMemoryTest decorator tests/functional: add memlock tests tests/functional/meson.build | 1 + tests/functional/qemu_test/__init__.py | 2 +- tests/functional/qemu_te

[PATCH v9 1/2] tests/functional: add skipLockedMemoryTest decorator

2025-06-05 Thread Alexandr Moshkov
Used in future commit to skipping execution of a tests if the system's locked memory limit is below the required threshold. Signed-off-by: Alexandr Moshkov Reviewed-by: Thomas Huth --- tests/functional/qemu_test/__init__.py | 2 +- tests/functional/qemu_test/decorators.py

Re: [PULL 00/27] Functional tests, Microblaze endianness & pc/q35 cleanups

2025-06-04 Thread Alexandr Moshkov
lated code ---- Alexandr Moshkov (2):    tests/functional: add skipLockedMemoryTest decorator    tests/functional: add memlock tests Hi Thomas and Alexandr, The memlock tests are failing: https://gitlab.com/qemu-project/qemu/-/jobs/10181084830#L5421 https://gitla

Re: [PATCH v8 2/2] tests/functional: add memlock tests

2025-05-26 Thread Alexandr Moshkov
On 5/27/25 11:13, Thomas Huth wrote: On 25/05/2025 09.07, 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}/status` file to check in VmSize, VmRSS and VmLck values: * if `memlock

[PATCH v8 0/2] tests/functional: add memlock tests

2025-05-25 Thread Alexandr Moshkov
hased out. v2 was [PATCH v2] tests/avocado: add memlock tests. Supersedes: <20250414075702.9248-1-dtalexund...@yandex-team.ru> v1 -> v2: In the previous send, i forgot to specify new patch version (v2) So i resend previous patch with version specified. Alexandr Moshkov (2): tests/functional:

[PATCH v8 1/2] tests/functional: add skipLockedMemoryTest decorator

2025-05-25 Thread Alexandr Moshkov
Used in future commit to skipping execution of a tests if the system's locked memory limit is below the required threshold. Signed-off-by: Alexandr Moshkov Reviewed-by: Thomas Huth --- tests/functional/qemu_test/__init__.py | 2 +- tests/functional/qemu_test/decorators.py

[PATCH v8 2/2] tests/functional: add memlock tests

2025-05-25 Thread Alexandr Moshkov
is resident; * if `memlock=on-fault`, then VmLck > 0 and only few memory is resident. Signed-off-by: Alexandr Moshkov --- tests/functional/meson.build | 1 + tests/functional/test_memlock.py | 79 2 files changed, 80 insertions(+) create mode 100755 tests/func

Re: [PATCH v7 2/2] tests/functional: add memlock tests

2025-05-22 Thread Alexandr Moshkov
On 5/22/25 16:13, Daniel P. Berrangé wrote: On Thu, May 22, 2025 at 01:51:44PM +0500, Alexandr Moshkov wrote: On 5/22/25 12:49, Thomas Huth wrote: On 21/05/2025 15.55, Alexandr Moshkov wrote: Add new tests to check the correctness of the `-overcommit memlock` option (possible values: off

Re: [PATCH v7 2/2] tests/functional: add memlock tests

2025-05-22 Thread Alexandr Moshkov
On 5/22/25 14:16, Thomas Huth wrote: On 22/05/2025 10.51, Alexandr Moshkov wrote: On 5/22/25 12:49, Thomas Huth wrote: On 21/05/2025 15.55, Alexandr Moshkov wrote: Add new tests to check the correctness of the `-overcommit memlock` option (possible values: off, on, on-fault) by using

Re: [PATCH v7 2/2] tests/functional: add memlock tests

2025-05-22 Thread Alexandr Moshkov
On 5/22/25 12:49, Thomas Huth wrote: On 21/05/2025 15.55, 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

[PATCH v7 1/2] tests/functional: add skipLockedMemoryTest decorator

2025-05-21 Thread Alexandr Moshkov
Used in future commit to skipping execution of a tests if the system's locked memory limit is below the required threshold. Signed-off-by: Alexandr Moshkov Reviewed-by: Thomas Huth --- tests/functional/qemu_test/__init__.py | 2 +- tests/functional/qemu_test/decorators.py

[PATCH v7 2/2] tests/functional: add memlock tests

2025-05-21 Thread Alexandr Moshkov
`, 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 --- tests/functional/meson.build |

[PATCH v7 0/2] tests/functional: add memlock tests

2025-05-21 Thread Alexandr Moshkov
.@yandex-team.ru> v1 -> v2: In the previous send, i forgot to specify new patch version (v2) So i resend previous patch with version specified. Alexandr Moshkov (2): tests/functional: add skipLockedMemoryTest decorator tests/functional: add memlock tests tests/functional/meson.build

Re: [PATCH v6 0/2] tests/functional: add memlock tests

2025-05-21 Thread Alexandr Moshkov
On 4/17/25 16: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

Re: [PATCH v6 0/2] tests/functional: add memlock tests

2025-04-28 Thread Alexandr Moshkov
On 4/17/25 16: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

[PATCH v6 2/2] tests/functional: add memlock tests

2025-04-17 Thread Alexandr Moshkov
`, 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 --- tests/functional/meson.build |

[PATCH v6 1/2] tests/functional: add skipLockedMemoryTest decorator

2025-04-17 Thread Alexandr Moshkov
Used in future commit to skipping execution of a tests if the system's locked memory limit is below the required threshold. Signed-off-by: Alexandr Moshkov --- tests/functional/qemu_test/__init__.py | 2 +- tests/functional/qemu_test/decorators.py | 18 ++ 2 files change

[PATCH v6 0/2] tests/functional: add memlock tests

2025-04-17 Thread Alexandr Moshkov
y new patch version (v2) So i resend previous patch with version specified. Alexandr Moshkov (2): tests/functional: add skipLockedMemoryTest decorator tests/functional: add memlock tests tests/functional/meson.build | 1 + tests/functional/qemu_test/__init__.py | 2 +

[PATCH v5 2/2] tests/functional: add memlock tests

2025-04-17 Thread Alexandr Moshkov
`, 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 --- tests/functional/meson.build |

[PATCH v5 0/2] tests/functional: add memlock tests

2025-04-17 Thread Alexandr Moshkov
dir, as the tests/avocado dir is being phased out. v2 was [PATCH v2] tests/avocado: add memlock tests. Supersedes: <20250414075702.9248-1-dtalexund...@yandex-team.ru> v1 -> v2: In the previous send, i forgot to specify new patch version (v2) So i resend previous patch with version specif

[PATCH v5 1/2] tests/functional: add skipLockedMemoryTest decorator

2025-04-17 Thread Alexandr Moshkov
Used in future commit to skipping execution of a tests if the system's locked memory limit is below the required threshold. Signed-off-by: Alexandr Moshkov --- tests/functional/qemu_test/__init__.py | 2 +- tests/functional/qemu_test/decorators.py | 18 ++ 2 files change

[PATCH v4 1/2] tests/functional: add skipLockedMemoryTest decorator

2025-04-17 Thread Alexandr Moshkov
Used in future commit to skipping execution of a tests if the system's locked memory limit is below the required threshold. Signed-off-by: Alexandr Moshkov --- tests/functional/qemu_test/__init__.py | 2 +- tests/functional/qemu_test/decorators.py | 19 +++ 2 files ch

[PATCH v4 2/2] tests/functional: add memlock tests

2025-04-17 Thread Alexandr Moshkov
`, 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 --- tests/functional/meson.build |

[PATCH v4 0/2] tests/functional: add memlock tests

2025-04-17 Thread Alexandr Moshkov
0414075702.9248-1-dtalexund...@yandex-team.ru> v1 -> v2: In the previous send, i forgot to specify new patch version (v2) So i resend previous patch with version specified. Alexandr Moshkov (2): tests/functional: add skipLockedMemoryTest decorator tests/functional: add memlock t

[PATCH v3] tests/functional: add memlock tests

2025-04-15 Thread Alexandr Moshkov
dir is being phased out. v2 was [PATCH v2] tests/avocado: add memlock tests. Supersedes: <20250414075702.9248-1-dtalexund...@yandex-team.ru> v1 -> v2: In the previous send, i forgot to specify new patch version (v2) So i resend previous patch with version specified. Signed-off-by: A

Re: [PATCH v3] tests/functional: add memlock tests

2025-04-15 Thread Alexandr Moshkov
On 4/15/25 14:20, Daniel P. Berrangé wrote: On Tue, Apr 15, 2025 at 02:08:55PM +0500, 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

Re: [PATCH v2] tests/avocado: add memlock tests

2025-04-14 Thread Alexandr Moshkov
On 4/14/25 14:14, Paolo Bonzini wrote: On 4/14/25 09:57, 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

[PATCH v2] tests/avocado: add memlock tests

2025-04-14 Thread Alexandr Moshkov
v2) So i resend previous patch with version specified. Signed-off-by: Alexandr Moshkov --- tests/avocado/memlock.py | 98 1 file changed, 98 insertions(+) create mode 100644 tests/avocado/memlock.py diff --git a/tests/avocado/memlock.py b/tests/a

[PATCH] tests/avocado: add memlock tests

2025-04-10 Thread Alexandr Moshkov
`, 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 --- tests/avocado/memlock.py |

[PATCH] tests/avocado: add memlock tests

2025-04-10 Thread Alexandr Moshkov
`, 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 --- tests/avocado/memlock.py |

Re: [PATCH 00/97] Patch Round-up for stable 4.0.1, freeze on 2019-10-10

2019-10-07 Thread Alexandr Iarygin
Michael Roth writes: > Hi everyone, > > > The following new patches are queued for QEMU stable v4.0.1: > > https://github.com/mdroth/qemu/commits/stable-4.0-staging > > The release is planned for 2019

Re: [Qemu-devel] [PATCH v5 4/9] i386: Add new property to control cache info

2018-04-09 Thread Alexandr Iarygin
Hello, Babu Moger writes: > This will be used to control the cache information. > By default new information will be displayed. If user > passes "-cpu legacy-cache" then older information will > be displayed even if the hardware supports new information. > > Signed-off-by: Babu Moger > --- > i

[Qemu-devel] [Bug 986770] Re: Oops: spice configured but not active

2012-04-23 Thread Alexandr
thx, this solves problem, but patches failed, i have to edit code manually -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/986770 Title: Oops: spice configured but not active Status in QEMU: New

[Qemu-devel] [Bug 986770] [NEW] Oops: spice configured but not active

2012-04-22 Thread Alexandr
Public bug reported: with latest qemu-kvm from git i have following problem: /usr/bin/kvm -daemonize -smp 4 -cpu host -vga qxl -enable-kvm -m 4096 -localtime -drive file=/home/sss/vm/win_xp/tmp_sys.img,if=virtio,media=disk,cache=none -drive file=/home/sss/vm/data.img,if=virtio,media=disk,cach