host_numa_info: add case #5136
host_numa_info: add case #5136
Conversation
dzhengfy
force-pushed
the
host_numa_info
branch
2 times, most recently
from
072fae1
to
91a828a
Compare
dzhengfy
force-pushed
the
host_numa_info
branch
from
91a828a
to
4e7d117
Compare
|
(1/1) type_specific.io-github-autotest-libvirt.host_numa.numa_info.default: PASS (45.78 s) libvirt-9.5.0 |
dzhengfy
force-pushed
the
host_numa_info
branch
4 times, most recently
from
bf997d2
to
9fac762
Compare
dzhengfy
force-pushed
the
host_numa_info
branch
from
9fac762
to
44b1d55
Compare
|
Result on RHEL 8.x (1/1) type_specific.io-github-autotest-libvirt.host_numa.numa_info.default: WARN: Test passed but there were warnings during execution. Check the log for details. (4.74 s) (1/1) type_specific.io-github-autotest-libvirt.guest_numa_node_tuning.change_numa_tuning.mem_mode_strict: WARN: Test passed but there were warnings during execution. Check the log for details. (35.16 s) libvirt-8.0.0 |
dzhengfy
force-pushed
the
host_numa_info
branch
3 times, most recently
from
85525fd
to
38e4250
Compare
|
@hs0210 Could you help check if it can pass on aarch64? Thanks |
| - default: | ||
| allocate_dict = {2048: 200, 1048576: 2} | ||
| aarch64: | ||
| allocate_dict = {2048: 200, 524288: 4, 16777216: 2} |
There was a problem hiding this comment.
It is enough to test 2M and 512M on kernel 64K machine. 16G is too large to allocate on most machines.
From xxxx-9.3 aarch64 support two serials huge pagesize according to the kernel pagesize.
For xxxx-9 kernel 4K, the supported huge pagesizes are 64K, 2M, 32M, 1G and default to 2M.
For xxxx-9 kernel 64K, the supported huge pagesizes are 2M, 512M, 16G and default to 512M, same with xxxx-8 aarch64.
Please adapt the test cases according to the above info.
There was a problem hiding this comment.
As we discussed, 4k will be enabled later. 16G has a problem now. I removed it.
| verify_node_mem_by_freepages(test_obj) | ||
| verify_node_mem_by_freepages_various_unit(test_obj) | ||
| verify_node_distance_by_capabilities(test_obj) | ||
| verify_node_cpus_by_capabilities(test_obj) |
There was a problem hiding this comment.
Please skip verify_node_cpus_by_capabilities verification for aach64 as aarch64 does not have dies.
dzhengfy
force-pushed
the
host_numa_info
branch
from
38e4250
to
2759fd5
Compare
|
(1/1) type_specific.io-github-autotest-libvirt.host_numa.numa_info.default: PASS (8.69 s) |
| aarch64: | ||
| allocate_dict = {2048: 200, 524288: 4} | ||
|
|
||
|
|
Test scenario: allocate hugepages using supported hugepage size, check numa information by virsh commands, like capabilities, freepages... Signed-off-by: Dan Zheng <[email protected]>
dzhengfy
force-pushed
the
host_numa_info
branch
from
2759fd5
to
07c257c
Compare
Case ID: xxx-297812
Test scenarios: Verify numa related info could be achieved by allocating hugepages using supported hugepage size,
check numa information by virsh commands, like capabilities, freepages...
Signed-off-by: Dan Zheng [email protected]