| commit | 421954f43b938bc48eb4ebad0d9953490cb4bfcc | |
| author | Philippe Mathieu-Daudé <f4bug@amsat.org> | |
| Fri, 5 Feb 2021 14:43:39 +0000 (5 15:43 +0100) | ||
| committer | Thomas Huth <thuth@redhat.com> | |
| Fri, 19 Feb 2021 05:29:04 +0000 (19 06:29 +0100) | ||
| tree | 034821fd8319770ff3628dd29997cc72087e2991 | treesnapshot (tar.gz zip) |
| parent | c79f01c9450bcf90c08a77f13fbf67bdba59a316 | commitdiff |
tests/qtest/boot-serial-test: Test Virt machine with 'max'
When using KVM, using a specific cpu type will only work if the
host CPU really is that exact CPU type.
During testing we can simply use the 'max' CPU which will select
all the features available from the host.
This allow running this test on a Cavium CN8890 (ThunderX cores).
Suggested-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-Id: <20210205144345.2068758-4-f4bug@amsat.org>
Reviewed-by: Andrew Jones <drjones@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
When using KVM, using a specific cpu type will only work if the
host CPU really is that exact CPU type.
During testing we can simply use the 'max' CPU which will select
all the features available from the host.
This allow running this test on a Cavium CN8890 (ThunderX cores).
Suggested-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-Id: <20210205144345.2068758-4-f4bug@amsat.org>
Reviewed-by: Andrew Jones <drjones@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
| tests/qtest/boot-serial-test.c | diffblobblamehistory |