Change memory size according to case update #5915
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: liang-cong-red-hat <[email protected]>
chloerh
approved these changes
Sep 26, 2024
nanli1
approved these changes
Sep 27, 2024
Yingshun
approved these changes
Sep 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
test results for other archs:
x86
(1/5) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.default_page_size: PASS (116.40 s)
(2/5) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.default_hugepage_size: PASS (109.78 s)
(3/5) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.1G: PASS (114.96 s)
(4/5) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.0: PASS (24.76 s)
(5/5) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.scarce_mem: PASS (38.21 s)
aarch 64 4k:
(1/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.default_page_size: PASS (103.16 s)
(2/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.default_hugepage_size: PASS (96.01 s)
(3/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.1G: PASS (107.18 s)
(4/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.2M: CANCEL: 2M is the default huge page size and tested in another test scenario (9.33 s)
(5/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.16G: SKIP: The hugepage size '16777216' is not supported on current arch (support: [2048, 32768, 64, 1048576])
(6/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.64K: PASS (99.05 s)
(7/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.32M: PASS (104.32 s)
(8/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.0: PASS (18.69 s)
(9/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.scarce_mem: PASS (20.26 s)
64k:
(1/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.default_page_size: PASS (89.62 s)
(2/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.default_hugepage_size: PASS (97.46 s)
(3/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.1G: SKIP: The hugepage size '1048576' is not supported on current arch (support: [16777216, 2048, 524288])
(4/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.2M: PASS (88.72 s)
(5/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.16G: PASS (118.23 s)
(6/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.64K: SKIP: The hugepage size '64' is not supported on current arch (support: [16777216, 2048, 524288])
(7/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.32M: SKIP: The hugepage size '32768' is not supported on current arch (support: [16777216, 2048, 524288])
(8/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.0: PASS (16.52 s)
(9/9) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.scarce_mem: PASS (18.69 s)
s390:
(1/3) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.1M: PASS (43.80 s)
(2/3) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.0: PASS (5.56 s)
(3/3) type_specific.io-github-autotest-libvirt.memory.backing.lifecycle.memory_hugepage.scarce_mem: PASS (6.36 s)