2019-10-31 17:27:27 +03:00
|
|
|
/*
|
|
|
|
* Arm CPU feature test cases
|
|
|
|
*
|
|
|
|
* Copyright (c) 2019 Red Hat Inc.
|
|
|
|
* Authors:
|
|
|
|
* Andrew Jones <drjones@redhat.com>
|
|
|
|
*
|
|
|
|
* This work is licensed under the terms of the GNU GPL, version 2 or later.
|
|
|
|
* See the COPYING file in the top-level directory.
|
|
|
|
*/
|
|
|
|
#include "qemu/osdep.h"
|
target/arm/cpu64: max cpu: Introduce sve<N> properties
Introduce cpu properties to give fine control over SVE vector lengths.
We introduce a property for each valid length up to the current
maximum supported, which is 2048-bits. The properties are named, e.g.
sve128, sve256, sve384, sve512, ..., where the number is the number of
bits. See the updates to docs/arm-cpu-features.rst for a description
of the semantics and for example uses.
Note, as sve-max-vq is still present and we'd like to be able to
support qmp_query_cpu_model_expansion with guests launched with e.g.
-cpu max,sve-max-vq=8 on their command lines, then we do allow
sve-max-vq and sve<N> properties to be provided at the same time, but
this is not recommended, and is why sve-max-vq is not mentioned in the
document. If sve-max-vq is provided then it enables all lengths smaller
than and including the max and disables all lengths larger. It also has
the side-effect that no larger lengths may be enabled and that the max
itself cannot be disabled. Smaller non-power-of-two lengths may,
however, be disabled, e.g. -cpu max,sve-max-vq=4,sve384=off provides a
guest the vector lengths 128, 256, and 512 bits.
This patch has been co-authored with Richard Henderson, who reworked
the target/arm/cpu64.c changes in order to push all the validation and
auto-enabling/disabling steps into the finalizer, resulting in a nice
LOC reduction.
Signed-off-by: Andrew Jones <drjones@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Tested-by: Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>
Reviewed-by: Beata Michalska <beata.michalska@linaro.org>
Message-id: 20191031142734.8590-5-drjones@redhat.com
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
2019-10-31 17:27:29 +03:00
|
|
|
#include "qemu/bitops.h"
|
2022-03-30 12:39:05 +03:00
|
|
|
#include "libqtest.h"
|
2019-10-31 17:27:27 +03:00
|
|
|
#include "qapi/qmp/qdict.h"
|
|
|
|
#include "qapi/qmp/qjson.h"
|
|
|
|
|
target/arm/cpu64: max cpu: Introduce sve<N> properties
Introduce cpu properties to give fine control over SVE vector lengths.
We introduce a property for each valid length up to the current
maximum supported, which is 2048-bits. The properties are named, e.g.
sve128, sve256, sve384, sve512, ..., where the number is the number of
bits. See the updates to docs/arm-cpu-features.rst for a description
of the semantics and for example uses.
Note, as sve-max-vq is still present and we'd like to be able to
support qmp_query_cpu_model_expansion with guests launched with e.g.
-cpu max,sve-max-vq=8 on their command lines, then we do allow
sve-max-vq and sve<N> properties to be provided at the same time, but
this is not recommended, and is why sve-max-vq is not mentioned in the
document. If sve-max-vq is provided then it enables all lengths smaller
than and including the max and disables all lengths larger. It also has
the side-effect that no larger lengths may be enabled and that the max
itself cannot be disabled. Smaller non-power-of-two lengths may,
however, be disabled, e.g. -cpu max,sve-max-vq=4,sve384=off provides a
guest the vector lengths 128, 256, and 512 bits.
This patch has been co-authored with Richard Henderson, who reworked
the target/arm/cpu64.c changes in order to push all the validation and
auto-enabling/disabling steps into the finalizer, resulting in a nice
LOC reduction.
Signed-off-by: Andrew Jones <drjones@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Tested-by: Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>
Reviewed-by: Beata Michalska <beata.michalska@linaro.org>
Message-id: 20191031142734.8590-5-drjones@redhat.com
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
2019-10-31 17:27:29 +03:00
|
|
|
/*
|
|
|
|
* We expect the SVE max-vq to be 16. Also it must be <= 64
|
|
|
|
* for our test code, otherwise 'vls' can't just be a uint64_t.
|
|
|
|
*/
|
|
|
|
#define SVE_MAX_VQ 16
|
|
|
|
|
2019-11-13 12:10:47 +03:00
|
|
|
#define MACHINE "-machine virt,gic-version=max -accel tcg "
|
2023-02-13 23:29:22 +03:00
|
|
|
#define MACHINE_KVM "-machine virt,gic-version=max -accel kvm "
|
2019-10-31 17:27:27 +03:00
|
|
|
#define QUERY_HEAD "{ 'execute': 'query-cpu-model-expansion', " \
|
|
|
|
" 'arguments': { 'type': 'full', "
|
|
|
|
#define QUERY_TAIL "}}"
|
|
|
|
|
|
|
|
static QDict *do_query_no_props(QTestState *qts, const char *cpu_type)
|
|
|
|
{
|
|
|
|
return qtest_qmp(qts, QUERY_HEAD "'model': { 'name': %s }"
|
|
|
|
QUERY_TAIL, cpu_type);
|
|
|
|
}
|
|
|
|
|
2022-12-19 16:02:04 +03:00
|
|
|
G_GNUC_PRINTF(3, 4)
|
2019-10-31 17:27:27 +03:00
|
|
|
static QDict *do_query(QTestState *qts, const char *cpu_type,
|
|
|
|
const char *fmt, ...)
|
|
|
|
{
|
|
|
|
QDict *resp;
|
|
|
|
|
|
|
|
if (fmt) {
|
|
|
|
QDict *args;
|
|
|
|
va_list ap;
|
|
|
|
|
|
|
|
va_start(ap, fmt);
|
|
|
|
args = qdict_from_vjsonf_nofail(fmt, ap);
|
|
|
|
va_end(ap);
|
|
|
|
|
|
|
|
resp = qtest_qmp(qts, QUERY_HEAD "'model': { 'name': %s, "
|
|
|
|
"'props': %p }"
|
|
|
|
QUERY_TAIL, cpu_type, args);
|
|
|
|
} else {
|
|
|
|
resp = do_query_no_props(qts, cpu_type);
|
|
|
|
}
|
|
|
|
|
|
|
|
return resp;
|
|
|
|
}
|
|
|
|
|
|
|
|
static const char *resp_get_error(QDict *resp)
|
|
|
|
{
|
|
|
|
QDict *qdict;
|
|
|
|
|
|
|
|
g_assert(resp);
|
|
|
|
|
|
|
|
qdict = qdict_get_qdict(resp, "error");
|
|
|
|
if (qdict) {
|
|
|
|
return qdict_get_str(qdict, "desc");
|
|
|
|
}
|
|
|
|
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
#define assert_error(qts, cpu_type, expected_error, fmt, ...) \
|
|
|
|
({ \
|
|
|
|
QDict *_resp; \
|
|
|
|
const char *_error; \
|
|
|
|
\
|
|
|
|
_resp = do_query(qts, cpu_type, fmt, ##__VA_ARGS__); \
|
|
|
|
g_assert(_resp); \
|
|
|
|
_error = resp_get_error(_resp); \
|
|
|
|
g_assert(_error); \
|
2024-03-05 17:59:15 +03:00
|
|
|
g_assert_cmpstr(_error, ==, expected_error); \
|
2019-10-31 17:27:27 +03:00
|
|
|
qobject_unref(_resp); \
|
|
|
|
})
|
|
|
|
|
|
|
|
static bool resp_has_props(QDict *resp)
|
|
|
|
{
|
|
|
|
QDict *qdict;
|
|
|
|
|
|
|
|
g_assert(resp);
|
|
|
|
|
|
|
|
if (!qdict_haskey(resp, "return")) {
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
qdict = qdict_get_qdict(resp, "return");
|
|
|
|
|
|
|
|
if (!qdict_haskey(qdict, "model")) {
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
qdict = qdict_get_qdict(qdict, "model");
|
|
|
|
|
|
|
|
return qdict_haskey(qdict, "props");
|
|
|
|
}
|
|
|
|
|
|
|
|
static QDict *resp_get_props(QDict *resp)
|
|
|
|
{
|
|
|
|
QDict *qdict;
|
|
|
|
|
|
|
|
g_assert(resp);
|
|
|
|
g_assert(resp_has_props(resp));
|
|
|
|
|
|
|
|
qdict = qdict_get_qdict(resp, "return");
|
|
|
|
qdict = qdict_get_qdict(qdict, "model");
|
|
|
|
qdict = qdict_get_qdict(qdict, "props");
|
|
|
|
|
|
|
|
return qdict;
|
|
|
|
}
|
|
|
|
|
2019-10-31 17:27:33 +03:00
|
|
|
static bool resp_get_feature(QDict *resp, const char *feature)
|
|
|
|
{
|
|
|
|
QDict *props;
|
|
|
|
|
|
|
|
g_assert(resp);
|
|
|
|
g_assert(resp_has_props(resp));
|
|
|
|
props = resp_get_props(resp);
|
|
|
|
g_assert(qdict_get(props, feature));
|
|
|
|
return qdict_get_bool(props, feature);
|
|
|
|
}
|
|
|
|
|
2019-10-31 17:27:27 +03:00
|
|
|
#define assert_has_feature(qts, cpu_type, feature) \
|
|
|
|
({ \
|
|
|
|
QDict *_resp = do_query_no_props(qts, cpu_type); \
|
|
|
|
g_assert(_resp); \
|
|
|
|
g_assert(resp_has_props(_resp)); \
|
|
|
|
g_assert(qdict_get(resp_get_props(_resp), feature)); \
|
|
|
|
qobject_unref(_resp); \
|
|
|
|
})
|
|
|
|
|
|
|
|
#define assert_has_not_feature(qts, cpu_type, feature) \
|
|
|
|
({ \
|
|
|
|
QDict *_resp = do_query_no_props(qts, cpu_type); \
|
|
|
|
g_assert(_resp); \
|
|
|
|
g_assert(!resp_has_props(_resp) || \
|
|
|
|
!qdict_get(resp_get_props(_resp), feature)); \
|
|
|
|
qobject_unref(_resp); \
|
|
|
|
})
|
|
|
|
|
2020-06-23 12:06:21 +03:00
|
|
|
#define resp_assert_feature(resp, feature, expected_value) \
|
2020-01-30 19:02:06 +03:00
|
|
|
({ \
|
2020-06-23 12:06:21 +03:00
|
|
|
QDict *_props; \
|
2020-01-30 19:02:06 +03:00
|
|
|
\
|
|
|
|
g_assert(_resp); \
|
|
|
|
g_assert(resp_has_props(_resp)); \
|
|
|
|
_props = resp_get_props(_resp); \
|
|
|
|
g_assert(qdict_get(_props, feature)); \
|
|
|
|
g_assert(qdict_get_bool(_props, feature) == (expected_value)); \
|
2020-06-23 12:06:21 +03:00
|
|
|
})
|
|
|
|
|
|
|
|
#define assert_feature(qts, cpu_type, feature, expected_value) \
|
|
|
|
({ \
|
|
|
|
QDict *_resp; \
|
|
|
|
\
|
|
|
|
_resp = do_query_no_props(qts, cpu_type); \
|
|
|
|
g_assert(_resp); \
|
|
|
|
resp_assert_feature(_resp, feature, expected_value); \
|
|
|
|
qobject_unref(_resp); \
|
|
|
|
})
|
|
|
|
|
|
|
|
#define assert_set_feature(qts, cpu_type, feature, value) \
|
|
|
|
({ \
|
|
|
|
const char *_fmt = (value) ? "{ %s: true }" : "{ %s: false }"; \
|
|
|
|
QDict *_resp; \
|
|
|
|
\
|
|
|
|
_resp = do_query(qts, cpu_type, _fmt, feature); \
|
|
|
|
g_assert(_resp); \
|
|
|
|
resp_assert_feature(_resp, feature, value); \
|
2020-01-30 19:02:06 +03:00
|
|
|
qobject_unref(_resp); \
|
|
|
|
})
|
|
|
|
|
|
|
|
#define assert_has_feature_enabled(qts, cpu_type, feature) \
|
|
|
|
assert_feature(qts, cpu_type, feature, true)
|
|
|
|
|
|
|
|
#define assert_has_feature_disabled(qts, cpu_type, feature) \
|
|
|
|
assert_feature(qts, cpu_type, feature, false)
|
|
|
|
|
2019-10-31 17:27:27 +03:00
|
|
|
static void assert_type_full(QTestState *qts)
|
|
|
|
{
|
|
|
|
const char *error;
|
|
|
|
QDict *resp;
|
|
|
|
|
|
|
|
resp = qtest_qmp(qts, "{ 'execute': 'query-cpu-model-expansion', "
|
|
|
|
"'arguments': { 'type': 'static', "
|
|
|
|
"'model': { 'name': 'foo' }}}");
|
|
|
|
g_assert(resp);
|
|
|
|
error = resp_get_error(resp);
|
|
|
|
g_assert(error);
|
2024-03-05 17:59:15 +03:00
|
|
|
g_assert_cmpstr(error, ==,
|
|
|
|
"The requested expansion type is not supported");
|
2019-10-31 17:27:27 +03:00
|
|
|
qobject_unref(resp);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void assert_bad_props(QTestState *qts, const char *cpu_type)
|
|
|
|
{
|
|
|
|
const char *error;
|
|
|
|
QDict *resp;
|
|
|
|
|
|
|
|
resp = qtest_qmp(qts, "{ 'execute': 'query-cpu-model-expansion', "
|
|
|
|
"'arguments': { 'type': 'full', "
|
|
|
|
"'model': { 'name': %s, "
|
|
|
|
"'props': false }}}",
|
|
|
|
cpu_type);
|
|
|
|
g_assert(resp);
|
|
|
|
error = resp_get_error(resp);
|
|
|
|
g_assert(error);
|
2024-03-05 17:59:15 +03:00
|
|
|
g_assert_cmpstr(error, ==,
|
target: Improve error reporting for CpuModelInfo member @props
query-cpu-model-comparison, query-cpu-model-baseline, and
query-cpu-model-expansion take CpuModelInfo arguments. Errors in
@props members of these arguments are reported for 'props', without
further context. For instance, s390x rejects
{"execute": "query-cpu-model-comparison", "arguments": {"modela": {"name": "z13", "props": {}}, "modelb": {"name": "z14", "props": []}}}
with
{"error": {"class": "GenericError", "desc": "Invalid parameter type for 'props', expected: object"}}
This is unusual; the common QAPI unmarshaling machinery would complain
about 'modelb.props'. Our hand-written code to visit the @props
member neglects to provide the context.
Tweak it so it provides it. The command above now fails with
{"error": {"class": "GenericError", "desc": "Invalid parameter type for 'modelb.props', expected: dict"}}
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-ID: <20240305145919.2186971-4-armbru@redhat.com>
Acked-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
2024-03-05 17:59:17 +03:00
|
|
|
"Invalid parameter type for 'model.props',"
|
|
|
|
" expected: object");
|
2019-10-31 17:27:27 +03:00
|
|
|
qobject_unref(resp);
|
|
|
|
}
|
|
|
|
|
target/arm/cpu64: max cpu: Introduce sve<N> properties
Introduce cpu properties to give fine control over SVE vector lengths.
We introduce a property for each valid length up to the current
maximum supported, which is 2048-bits. The properties are named, e.g.
sve128, sve256, sve384, sve512, ..., where the number is the number of
bits. See the updates to docs/arm-cpu-features.rst for a description
of the semantics and for example uses.
Note, as sve-max-vq is still present and we'd like to be able to
support qmp_query_cpu_model_expansion with guests launched with e.g.
-cpu max,sve-max-vq=8 on their command lines, then we do allow
sve-max-vq and sve<N> properties to be provided at the same time, but
this is not recommended, and is why sve-max-vq is not mentioned in the
document. If sve-max-vq is provided then it enables all lengths smaller
than and including the max and disables all lengths larger. It also has
the side-effect that no larger lengths may be enabled and that the max
itself cannot be disabled. Smaller non-power-of-two lengths may,
however, be disabled, e.g. -cpu max,sve-max-vq=4,sve384=off provides a
guest the vector lengths 128, 256, and 512 bits.
This patch has been co-authored with Richard Henderson, who reworked
the target/arm/cpu64.c changes in order to push all the validation and
auto-enabling/disabling steps into the finalizer, resulting in a nice
LOC reduction.
Signed-off-by: Andrew Jones <drjones@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Tested-by: Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>
Reviewed-by: Beata Michalska <beata.michalska@linaro.org>
Message-id: 20191031142734.8590-5-drjones@redhat.com
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
2019-10-31 17:27:29 +03:00
|
|
|
static uint64_t resp_get_sve_vls(QDict *resp)
|
|
|
|
{
|
|
|
|
QDict *props;
|
|
|
|
const QDictEntry *e;
|
|
|
|
uint64_t vls = 0;
|
|
|
|
int n = 0;
|
|
|
|
|
|
|
|
g_assert(resp);
|
|
|
|
g_assert(resp_has_props(resp));
|
|
|
|
|
|
|
|
props = resp_get_props(resp);
|
|
|
|
|
|
|
|
for (e = qdict_first(props); e; e = qdict_next(props, e)) {
|
|
|
|
if (strlen(e->key) > 3 && !strncmp(e->key, "sve", 3) &&
|
|
|
|
g_ascii_isdigit(e->key[3])) {
|
|
|
|
char *endptr;
|
|
|
|
int bits;
|
|
|
|
|
|
|
|
bits = g_ascii_strtoll(&e->key[3], &endptr, 10);
|
|
|
|
if (!bits || *endptr != '\0') {
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (qdict_get_bool(props, e->key)) {
|
|
|
|
vls |= BIT_ULL((bits / 128) - 1);
|
|
|
|
}
|
|
|
|
++n;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
g_assert(n == SVE_MAX_VQ);
|
|
|
|
|
|
|
|
return vls;
|
|
|
|
}
|
|
|
|
|
|
|
|
#define assert_sve_vls(qts, cpu_type, expected_vls, fmt, ...) \
|
|
|
|
({ \
|
|
|
|
QDict *_resp = do_query(qts, cpu_type, fmt, ##__VA_ARGS__); \
|
|
|
|
g_assert(_resp); \
|
|
|
|
g_assert(resp_has_props(_resp)); \
|
|
|
|
g_assert(resp_get_sve_vls(_resp) == expected_vls); \
|
|
|
|
qobject_unref(_resp); \
|
|
|
|
})
|
|
|
|
|
|
|
|
static void sve_tests_default(QTestState *qts, const char *cpu_type)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* With no sve-max-vq or sve<N> properties on the command line
|
|
|
|
* the default is to have all vector lengths enabled. This also
|
|
|
|
* tests that 'sve' is 'on' by default.
|
|
|
|
*/
|
|
|
|
assert_sve_vls(qts, cpu_type, BIT_ULL(SVE_MAX_VQ) - 1, NULL);
|
|
|
|
|
|
|
|
/* With SVE off, all vector lengths should also be off. */
|
|
|
|
assert_sve_vls(qts, cpu_type, 0, "{ 'sve': false }");
|
|
|
|
|
|
|
|
/* With SVE on, we must have at least one vector length enabled. */
|
|
|
|
assert_error(qts, cpu_type, "cannot disable sve128", "{ 'sve128': false }");
|
|
|
|
|
|
|
|
/* Basic enable/disable tests. */
|
|
|
|
assert_sve_vls(qts, cpu_type, 0x7, "{ 'sve384': true }");
|
|
|
|
assert_sve_vls(qts, cpu_type, ((BIT_ULL(SVE_MAX_VQ) - 1) & ~BIT_ULL(2)),
|
|
|
|
"{ 'sve384': false }");
|
|
|
|
|
|
|
|
/*
|
|
|
|
* ---------------------------------------------------------------------
|
|
|
|
* power-of-two(vq) all-power- can can
|
|
|
|
* of-two(< vq) enable disable
|
|
|
|
* ---------------------------------------------------------------------
|
|
|
|
* vq < max_vq no MUST* yes yes
|
|
|
|
* vq < max_vq yes MUST* yes no
|
|
|
|
* ---------------------------------------------------------------------
|
|
|
|
* vq == max_vq n/a MUST* yes** yes**
|
|
|
|
* ---------------------------------------------------------------------
|
|
|
|
* vq > max_vq n/a no no yes
|
|
|
|
* vq > max_vq n/a yes yes yes
|
|
|
|
* ---------------------------------------------------------------------
|
|
|
|
*
|
|
|
|
* [*] "MUST" means this requirement must already be satisfied,
|
|
|
|
* otherwise 'max_vq' couldn't itself be enabled.
|
|
|
|
*
|
|
|
|
* [**] Not testable with the QMP interface, only with the command line.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/* max_vq := 8 */
|
|
|
|
assert_sve_vls(qts, cpu_type, 0x8b, "{ 'sve1024': true }");
|
|
|
|
|
|
|
|
/* max_vq := 8, vq < max_vq, !power-of-two(vq) */
|
|
|
|
assert_sve_vls(qts, cpu_type, 0x8f,
|
|
|
|
"{ 'sve1024': true, 'sve384': true }");
|
|
|
|
assert_sve_vls(qts, cpu_type, 0x8b,
|
|
|
|
"{ 'sve1024': true, 'sve384': false }");
|
|
|
|
|
|
|
|
/* max_vq := 8, vq < max_vq, power-of-two(vq) */
|
|
|
|
assert_sve_vls(qts, cpu_type, 0x8b,
|
|
|
|
"{ 'sve1024': true, 'sve256': true }");
|
|
|
|
assert_error(qts, cpu_type, "cannot disable sve256",
|
|
|
|
"{ 'sve1024': true, 'sve256': false }");
|
|
|
|
|
|
|
|
/* max_vq := 3, vq > max_vq, !all-power-of-two(< vq) */
|
|
|
|
assert_error(qts, cpu_type, "cannot disable sve512",
|
|
|
|
"{ 'sve384': true, 'sve512': false, 'sve640': true }");
|
|
|
|
|
|
|
|
/*
|
|
|
|
* We can disable power-of-two vector lengths when all larger lengths
|
|
|
|
* are also disabled. We only need to disable the power-of-two length,
|
|
|
|
* as all non-enabled larger lengths will then be auto-disabled.
|
|
|
|
*/
|
|
|
|
assert_sve_vls(qts, cpu_type, 0x7, "{ 'sve512': false }");
|
|
|
|
|
|
|
|
/* max_vq := 3, vq > max_vq, all-power-of-two(< vq) */
|
|
|
|
assert_sve_vls(qts, cpu_type, 0x1f,
|
|
|
|
"{ 'sve384': true, 'sve512': true, 'sve640': true }");
|
|
|
|
assert_sve_vls(qts, cpu_type, 0xf,
|
|
|
|
"{ 'sve384': true, 'sve512': true, 'sve640': false }");
|
|
|
|
}
|
|
|
|
|
|
|
|
static void sve_tests_sve_max_vq_8(const void *data)
|
|
|
|
{
|
|
|
|
QTestState *qts;
|
|
|
|
|
|
|
|
qts = qtest_init(MACHINE "-cpu max,sve-max-vq=8");
|
|
|
|
|
|
|
|
assert_sve_vls(qts, "max", BIT_ULL(8) - 1, NULL);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Disabling the max-vq set by sve-max-vq is not allowed, but
|
|
|
|
* of course enabling it is OK.
|
|
|
|
*/
|
|
|
|
assert_error(qts, "max", "cannot disable sve1024", "{ 'sve1024': false }");
|
|
|
|
assert_sve_vls(qts, "max", 0xff, "{ 'sve1024': true }");
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Enabling anything larger than max-vq set by sve-max-vq is not
|
|
|
|
* allowed, but of course disabling everything larger is OK.
|
|
|
|
*/
|
|
|
|
assert_error(qts, "max", "cannot enable sve1152", "{ 'sve1152': true }");
|
|
|
|
assert_sve_vls(qts, "max", 0xff, "{ 'sve1152': false }");
|
|
|
|
|
|
|
|
/*
|
|
|
|
* We can enable/disable non power-of-two lengths smaller than the
|
|
|
|
* max-vq set by sve-max-vq, but, while we can enable power-of-two
|
|
|
|
* lengths, we can't disable them.
|
|
|
|
*/
|
|
|
|
assert_sve_vls(qts, "max", 0xff, "{ 'sve384': true }");
|
|
|
|
assert_sve_vls(qts, "max", 0xfb, "{ 'sve384': false }");
|
|
|
|
assert_sve_vls(qts, "max", 0xff, "{ 'sve256': true }");
|
|
|
|
assert_error(qts, "max", "cannot disable sve256", "{ 'sve256': false }");
|
|
|
|
|
|
|
|
qtest_quit(qts);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void sve_tests_sve_off(const void *data)
|
|
|
|
{
|
|
|
|
QTestState *qts;
|
|
|
|
|
|
|
|
qts = qtest_init(MACHINE "-cpu max,sve=off");
|
|
|
|
|
|
|
|
/* SVE is off, so the map should be empty. */
|
|
|
|
assert_sve_vls(qts, "max", 0, NULL);
|
|
|
|
|
|
|
|
/* The map stays empty even if we turn lengths off. */
|
|
|
|
assert_sve_vls(qts, "max", 0, "{ 'sve128': false }");
|
|
|
|
|
|
|
|
/* It's an error to enable lengths when SVE is off. */
|
|
|
|
assert_error(qts, "max", "cannot enable sve128", "{ 'sve128': true }");
|
|
|
|
|
|
|
|
/* With SVE re-enabled we should get all vector lengths enabled. */
|
|
|
|
assert_sve_vls(qts, "max", BIT_ULL(SVE_MAX_VQ) - 1, "{ 'sve': true }");
|
|
|
|
|
|
|
|
/* Or enable SVE with just specific vector lengths. */
|
|
|
|
assert_sve_vls(qts, "max", 0x3,
|
|
|
|
"{ 'sve': true, 'sve128': true, 'sve256': true }");
|
|
|
|
|
|
|
|
qtest_quit(qts);
|
|
|
|
}
|
|
|
|
|
2019-10-31 17:27:33 +03:00
|
|
|
static void sve_tests_sve_off_kvm(const void *data)
|
|
|
|
{
|
|
|
|
QTestState *qts;
|
|
|
|
|
|
|
|
qts = qtest_init(MACHINE_KVM "-cpu max,sve=off");
|
|
|
|
|
|
|
|
/*
|
|
|
|
* We don't know if this host supports SVE so we don't
|
|
|
|
* attempt to test enabling anything. We only test that
|
|
|
|
* everything is disabled (as it should be with sve=off)
|
|
|
|
* and that using sve<N>=off to explicitly disable vector
|
|
|
|
* lengths is OK too.
|
|
|
|
*/
|
|
|
|
assert_sve_vls(qts, "max", 0, NULL);
|
|
|
|
assert_sve_vls(qts, "max", 0, "{ 'sve128': false }");
|
|
|
|
|
|
|
|
qtest_quit(qts);
|
|
|
|
}
|
|
|
|
|
2021-01-12 02:57:39 +03:00
|
|
|
static void pauth_tests_default(QTestState *qts, const char *cpu_type)
|
|
|
|
{
|
|
|
|
assert_has_feature_enabled(qts, cpu_type, "pauth");
|
|
|
|
assert_has_feature_disabled(qts, cpu_type, "pauth-impdef");
|
2023-08-30 02:23:28 +03:00
|
|
|
assert_has_feature_disabled(qts, cpu_type, "pauth-qarma3");
|
2021-01-12 02:57:39 +03:00
|
|
|
assert_set_feature(qts, cpu_type, "pauth", false);
|
|
|
|
assert_set_feature(qts, cpu_type, "pauth", true);
|
|
|
|
assert_set_feature(qts, cpu_type, "pauth-impdef", true);
|
|
|
|
assert_set_feature(qts, cpu_type, "pauth-impdef", false);
|
2023-08-30 02:23:28 +03:00
|
|
|
assert_set_feature(qts, cpu_type, "pauth-qarma3", true);
|
|
|
|
assert_set_feature(qts, cpu_type, "pauth-qarma3", false);
|
|
|
|
assert_error(qts, cpu_type,
|
|
|
|
"cannot enable pauth-impdef or pauth-qarma3 without pauth",
|
2021-01-12 02:57:39 +03:00
|
|
|
"{ 'pauth': false, 'pauth-impdef': true }");
|
2023-08-30 02:23:28 +03:00
|
|
|
assert_error(qts, cpu_type,
|
|
|
|
"cannot enable pauth-impdef or pauth-qarma3 without pauth",
|
|
|
|
"{ 'pauth': false, 'pauth-qarma3': true }");
|
|
|
|
assert_error(qts, cpu_type,
|
|
|
|
"cannot enable both pauth-impdef and pauth-qarma3",
|
|
|
|
"{ 'pauth': true, 'pauth-impdef': true, 'pauth-qarma3': true }");
|
2021-01-12 02:57:39 +03:00
|
|
|
}
|
|
|
|
|
2019-10-31 17:27:27 +03:00
|
|
|
static void test_query_cpu_model_expansion(const void *data)
|
|
|
|
{
|
|
|
|
QTestState *qts;
|
|
|
|
|
|
|
|
qts = qtest_init(MACHINE "-cpu max");
|
|
|
|
|
|
|
|
/* Test common query-cpu-model-expansion input validation */
|
|
|
|
assert_type_full(qts);
|
|
|
|
assert_bad_props(qts, "max");
|
|
|
|
assert_error(qts, "foo", "The CPU type 'foo' is not a recognized "
|
|
|
|
"ARM CPU type", NULL);
|
target: Improve error reporting for CpuModelInfo member @props
query-cpu-model-comparison, query-cpu-model-baseline, and
query-cpu-model-expansion take CpuModelInfo arguments. Errors in
@props members of these arguments are reported for 'props', without
further context. For instance, s390x rejects
{"execute": "query-cpu-model-comparison", "arguments": {"modela": {"name": "z13", "props": {}}, "modelb": {"name": "z14", "props": []}}}
with
{"error": {"class": "GenericError", "desc": "Invalid parameter type for 'props', expected: object"}}
This is unusual; the common QAPI unmarshaling machinery would complain
about 'modelb.props'. Our hand-written code to visit the @props
member neglects to provide the context.
Tweak it so it provides it. The command above now fails with
{"error": {"class": "GenericError", "desc": "Invalid parameter type for 'modelb.props', expected: dict"}}
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-ID: <20240305145919.2186971-4-armbru@redhat.com>
Acked-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
2024-03-05 17:59:17 +03:00
|
|
|
assert_error(qts, "max", "Parameter 'model.props.not-a-prop' is unexpected",
|
2019-10-31 17:27:27 +03:00
|
|
|
"{ 'not-a-prop': false }");
|
|
|
|
assert_error(qts, "host", "The CPU type 'host' requires KVM", NULL);
|
|
|
|
|
|
|
|
/* Test expected feature presence/absence for some cpu types */
|
2020-01-30 19:02:06 +03:00
|
|
|
assert_has_feature_enabled(qts, "cortex-a15", "pmu");
|
2019-10-31 17:27:27 +03:00
|
|
|
assert_has_not_feature(qts, "cortex-a15", "aarch64");
|
|
|
|
|
2020-06-23 12:06:21 +03:00
|
|
|
/* Enabling and disabling pmu should always work. */
|
|
|
|
assert_has_feature_enabled(qts, "max", "pmu");
|
|
|
|
assert_set_feature(qts, "max", "pmu", false);
|
|
|
|
assert_set_feature(qts, "max", "pmu", true);
|
|
|
|
|
2020-01-30 19:02:06 +03:00
|
|
|
assert_has_not_feature(qts, "max", "kvm-no-adjvtime");
|
2020-10-01 09:17:18 +03:00
|
|
|
assert_has_not_feature(qts, "max", "kvm-steal-time");
|
2020-01-30 19:02:06 +03:00
|
|
|
|
2019-10-31 17:27:27 +03:00
|
|
|
if (g_str_equal(qtest_get_arch(), "aarch64")) {
|
2020-01-30 19:02:06 +03:00
|
|
|
assert_has_feature_enabled(qts, "max", "aarch64");
|
|
|
|
assert_has_feature_enabled(qts, "max", "sve");
|
|
|
|
assert_has_feature_enabled(qts, "max", "sve128");
|
|
|
|
assert_has_feature_enabled(qts, "cortex-a57", "pmu");
|
|
|
|
assert_has_feature_enabled(qts, "cortex-a57", "aarch64");
|
2019-10-31 17:27:27 +03:00
|
|
|
|
2021-08-31 11:29:40 +03:00
|
|
|
assert_has_feature_enabled(qts, "a64fx", "pmu");
|
|
|
|
assert_has_feature_enabled(qts, "a64fx", "aarch64");
|
|
|
|
/*
|
|
|
|
* A64FX does not support any other vector lengths besides those
|
|
|
|
* that are enabled by default(128bit, 256bits, 512bit).
|
|
|
|
*/
|
|
|
|
assert_has_feature_enabled(qts, "a64fx", "sve");
|
|
|
|
assert_sve_vls(qts, "a64fx", 0xb, NULL);
|
|
|
|
assert_error(qts, "a64fx", "cannot enable sve384",
|
|
|
|
"{ 'sve384': true }");
|
|
|
|
assert_error(qts, "a64fx", "cannot enable sve640",
|
|
|
|
"{ 'sve640': true }");
|
|
|
|
|
target/arm/cpu64: max cpu: Introduce sve<N> properties
Introduce cpu properties to give fine control over SVE vector lengths.
We introduce a property for each valid length up to the current
maximum supported, which is 2048-bits. The properties are named, e.g.
sve128, sve256, sve384, sve512, ..., where the number is the number of
bits. See the updates to docs/arm-cpu-features.rst for a description
of the semantics and for example uses.
Note, as sve-max-vq is still present and we'd like to be able to
support qmp_query_cpu_model_expansion with guests launched with e.g.
-cpu max,sve-max-vq=8 on their command lines, then we do allow
sve-max-vq and sve<N> properties to be provided at the same time, but
this is not recommended, and is why sve-max-vq is not mentioned in the
document. If sve-max-vq is provided then it enables all lengths smaller
than and including the max and disables all lengths larger. It also has
the side-effect that no larger lengths may be enabled and that the max
itself cannot be disabled. Smaller non-power-of-two lengths may,
however, be disabled, e.g. -cpu max,sve-max-vq=4,sve384=off provides a
guest the vector lengths 128, 256, and 512 bits.
This patch has been co-authored with Richard Henderson, who reworked
the target/arm/cpu64.c changes in order to push all the validation and
auto-enabling/disabling steps into the finalizer, resulting in a nice
LOC reduction.
Signed-off-by: Andrew Jones <drjones@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Tested-by: Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>
Reviewed-by: Beata Michalska <beata.michalska@linaro.org>
Message-id: 20191031142734.8590-5-drjones@redhat.com
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
2019-10-31 17:27:29 +03:00
|
|
|
sve_tests_default(qts, "max");
|
2021-01-12 02:57:39 +03:00
|
|
|
pauth_tests_default(qts, "max");
|
target/arm/cpu64: max cpu: Introduce sve<N> properties
Introduce cpu properties to give fine control over SVE vector lengths.
We introduce a property for each valid length up to the current
maximum supported, which is 2048-bits. The properties are named, e.g.
sve128, sve256, sve384, sve512, ..., where the number is the number of
bits. See the updates to docs/arm-cpu-features.rst for a description
of the semantics and for example uses.
Note, as sve-max-vq is still present and we'd like to be able to
support qmp_query_cpu_model_expansion with guests launched with e.g.
-cpu max,sve-max-vq=8 on their command lines, then we do allow
sve-max-vq and sve<N> properties to be provided at the same time, but
this is not recommended, and is why sve-max-vq is not mentioned in the
document. If sve-max-vq is provided then it enables all lengths smaller
than and including the max and disables all lengths larger. It also has
the side-effect that no larger lengths may be enabled and that the max
itself cannot be disabled. Smaller non-power-of-two lengths may,
however, be disabled, e.g. -cpu max,sve-max-vq=4,sve384=off provides a
guest the vector lengths 128, 256, and 512 bits.
This patch has been co-authored with Richard Henderson, who reworked
the target/arm/cpu64.c changes in order to push all the validation and
auto-enabling/disabling steps into the finalizer, resulting in a nice
LOC reduction.
Signed-off-by: Andrew Jones <drjones@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Tested-by: Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>
Reviewed-by: Beata Michalska <beata.michalska@linaro.org>
Message-id: 20191031142734.8590-5-drjones@redhat.com
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
2019-10-31 17:27:29 +03:00
|
|
|
|
2019-10-31 17:27:27 +03:00
|
|
|
/* Test that features that depend on KVM generate errors without. */
|
|
|
|
assert_error(qts, "max",
|
|
|
|
"'aarch64' feature cannot be disabled "
|
|
|
|
"unless KVM is enabled and 32-bit EL1 "
|
|
|
|
"is supported",
|
|
|
|
"{ 'aarch64': false }");
|
|
|
|
}
|
|
|
|
|
|
|
|
qtest_quit(qts);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void test_query_cpu_model_expansion_kvm(const void *data)
|
|
|
|
{
|
|
|
|
QTestState *qts;
|
|
|
|
|
|
|
|
qts = qtest_init(MACHINE_KVM "-cpu max");
|
|
|
|
|
2020-06-23 12:06:21 +03:00
|
|
|
/* Enabling and disabling kvm-no-adjvtime should always work. */
|
2020-01-30 19:02:06 +03:00
|
|
|
assert_has_feature_disabled(qts, "host", "kvm-no-adjvtime");
|
2020-06-23 12:06:21 +03:00
|
|
|
assert_set_feature(qts, "host", "kvm-no-adjvtime", true);
|
|
|
|
assert_set_feature(qts, "host", "kvm-no-adjvtime", false);
|
2020-01-30 19:02:06 +03:00
|
|
|
|
2019-10-31 17:27:27 +03:00
|
|
|
if (g_str_equal(qtest_get_arch(), "aarch64")) {
|
2020-10-01 09:17:18 +03:00
|
|
|
bool kvm_supports_steal_time;
|
2019-10-31 17:27:33 +03:00
|
|
|
bool kvm_supports_sve;
|
|
|
|
char max_name[8], name[8];
|
|
|
|
uint32_t max_vq, vq;
|
|
|
|
uint64_t vls;
|
|
|
|
QDict *resp;
|
|
|
|
char *error;
|
|
|
|
|
2023-04-26 21:00:06 +03:00
|
|
|
/*
|
|
|
|
* When using KVM, only the 'host' and 'max' CPU models are
|
|
|
|
* supported. Test that we're emitting a suitable error for
|
|
|
|
* unsupported CPU models.
|
|
|
|
*/
|
|
|
|
if (qtest_has_accel("tcg")) {
|
|
|
|
assert_error(qts, "cortex-a7",
|
|
|
|
"We cannot guarantee the CPU type 'cortex-a7' works "
|
|
|
|
"with KVM on this host", NULL);
|
|
|
|
} else {
|
|
|
|
/*
|
|
|
|
* With a KVM-only build the 32-bit CPUs are not present.
|
|
|
|
*/
|
|
|
|
assert_error(qts, "cortex-a7",
|
|
|
|
"The CPU type 'cortex-a7' is not a "
|
|
|
|
"recognized ARM CPU type", NULL);
|
|
|
|
}
|
2020-10-01 09:17:18 +03:00
|
|
|
|
2020-01-30 19:02:06 +03:00
|
|
|
assert_has_feature_enabled(qts, "host", "aarch64");
|
2020-06-23 12:06:21 +03:00
|
|
|
|
|
|
|
/* Enabling and disabling pmu should always work. */
|
2020-01-30 19:02:06 +03:00
|
|
|
assert_has_feature_enabled(qts, "host", "pmu");
|
2020-06-23 12:06:21 +03:00
|
|
|
assert_set_feature(qts, "host", "pmu", false);
|
|
|
|
assert_set_feature(qts, "host", "pmu", true);
|
2019-10-31 17:27:27 +03:00
|
|
|
|
2020-10-01 09:17:18 +03:00
|
|
|
/*
|
|
|
|
* Some features would be enabled by default, but they're disabled
|
|
|
|
* because this instance of KVM doesn't support them. Test that the
|
|
|
|
* features are present, and, when enabled, issue further tests.
|
|
|
|
*/
|
|
|
|
assert_has_feature(qts, "host", "kvm-steal-time");
|
2019-10-31 17:27:34 +03:00
|
|
|
assert_has_feature(qts, "host", "sve");
|
2020-10-01 09:17:18 +03:00
|
|
|
|
2019-10-31 17:27:34 +03:00
|
|
|
resp = do_query_no_props(qts, "host");
|
2020-10-01 09:17:18 +03:00
|
|
|
kvm_supports_steal_time = resp_get_feature(resp, "kvm-steal-time");
|
2019-10-31 17:27:33 +03:00
|
|
|
kvm_supports_sve = resp_get_feature(resp, "sve");
|
|
|
|
vls = resp_get_sve_vls(resp);
|
|
|
|
qobject_unref(resp);
|
|
|
|
|
2020-10-01 09:17:18 +03:00
|
|
|
if (kvm_supports_steal_time) {
|
|
|
|
/* If we have steal-time then we should be able to toggle it. */
|
|
|
|
assert_set_feature(qts, "host", "kvm-steal-time", false);
|
|
|
|
assert_set_feature(qts, "host", "kvm-steal-time", true);
|
|
|
|
}
|
|
|
|
|
2019-10-31 17:27:33 +03:00
|
|
|
if (kvm_supports_sve) {
|
|
|
|
g_assert(vls != 0);
|
|
|
|
max_vq = 64 - __builtin_clzll(vls);
|
2020-11-04 13:23:19 +03:00
|
|
|
sprintf(max_name, "sve%u", max_vq * 128);
|
2019-10-31 17:27:33 +03:00
|
|
|
|
|
|
|
/* Enabling a supported length is of course fine. */
|
2019-10-31 17:27:34 +03:00
|
|
|
assert_sve_vls(qts, "host", vls, "{ %s: true }", max_name);
|
2019-10-31 17:27:33 +03:00
|
|
|
|
|
|
|
/* Get the next supported length smaller than max-vq. */
|
|
|
|
vq = 64 - __builtin_clzll(vls & ~BIT_ULL(max_vq - 1));
|
|
|
|
if (vq) {
|
|
|
|
/*
|
|
|
|
* We have at least one length smaller than max-vq,
|
|
|
|
* so we can disable max-vq.
|
|
|
|
*/
|
2019-10-31 17:27:34 +03:00
|
|
|
assert_sve_vls(qts, "host", (vls & ~BIT_ULL(max_vq - 1)),
|
2019-10-31 17:27:33 +03:00
|
|
|
"{ %s: false }", max_name);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Smaller, supported vector lengths cannot be disabled
|
|
|
|
* unless all larger, supported vector lengths are also
|
|
|
|
* disabled.
|
|
|
|
*/
|
2020-11-04 13:23:19 +03:00
|
|
|
sprintf(name, "sve%u", vq * 128);
|
2019-10-31 17:27:33 +03:00
|
|
|
error = g_strdup_printf("cannot disable %s", name);
|
2019-10-31 17:27:34 +03:00
|
|
|
assert_error(qts, "host", error,
|
2019-10-31 17:27:33 +03:00
|
|
|
"{ %s: true, %s: false }",
|
|
|
|
max_name, name);
|
|
|
|
g_free(error);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* The smallest, supported vector length is required, because
|
|
|
|
* we need at least one vector length enabled.
|
|
|
|
*/
|
|
|
|
vq = __builtin_ffsll(vls);
|
2020-11-04 13:23:19 +03:00
|
|
|
sprintf(name, "sve%u", vq * 128);
|
2019-10-31 17:27:33 +03:00
|
|
|
error = g_strdup_printf("cannot disable %s", name);
|
2019-10-31 17:27:34 +03:00
|
|
|
assert_error(qts, "host", error, "{ %s: false }", name);
|
2019-10-31 17:27:33 +03:00
|
|
|
g_free(error);
|
|
|
|
|
|
|
|
/* Get an unsupported length. */
|
|
|
|
for (vq = 1; vq <= max_vq; ++vq) {
|
|
|
|
if (!(vls & BIT_ULL(vq - 1))) {
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if (vq <= SVE_MAX_VQ) {
|
2020-11-04 13:23:19 +03:00
|
|
|
sprintf(name, "sve%u", vq * 128);
|
2019-10-31 17:27:33 +03:00
|
|
|
error = g_strdup_printf("cannot enable %s", name);
|
2019-10-31 17:27:34 +03:00
|
|
|
assert_error(qts, "host", error, "{ %s: true }", name);
|
2019-10-31 17:27:33 +03:00
|
|
|
g_free(error);
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
g_assert(vls == 0);
|
|
|
|
}
|
2019-10-31 17:27:27 +03:00
|
|
|
} else {
|
|
|
|
assert_has_not_feature(qts, "host", "aarch64");
|
|
|
|
assert_has_not_feature(qts, "host", "pmu");
|
2019-10-31 17:27:34 +03:00
|
|
|
assert_has_not_feature(qts, "host", "sve");
|
2020-10-01 09:17:18 +03:00
|
|
|
assert_has_not_feature(qts, "host", "kvm-steal-time");
|
2019-10-31 17:27:27 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
qtest_quit(qts);
|
|
|
|
}
|
|
|
|
|
|
|
|
int main(int argc, char **argv)
|
|
|
|
{
|
|
|
|
g_test_init(&argc, &argv, NULL);
|
|
|
|
|
2023-02-13 23:29:22 +03:00
|
|
|
if (qtest_has_accel("tcg")) {
|
|
|
|
qtest_add_data_func("/arm/query-cpu-model-expansion",
|
|
|
|
NULL, test_query_cpu_model_expansion);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!g_str_equal(qtest_get_arch(), "aarch64")) {
|
|
|
|
goto out;
|
|
|
|
}
|
2019-10-31 17:27:27 +03:00
|
|
|
|
|
|
|
/*
|
|
|
|
* For now we only run KVM specific tests with AArch64 QEMU in
|
|
|
|
* order avoid attempting to run an AArch32 QEMU with KVM on
|
|
|
|
* AArch64 hosts. That won't work and isn't easy to detect.
|
|
|
|
*/
|
2023-02-13 23:29:22 +03:00
|
|
|
if (qtest_has_accel("kvm")) {
|
2021-09-02 14:35:49 +03:00
|
|
|
/*
|
|
|
|
* This tests target the 'host' CPU type, so register it only if
|
|
|
|
* KVM is available.
|
|
|
|
*/
|
2019-10-31 17:27:27 +03:00
|
|
|
qtest_add_data_func("/arm/kvm/query-cpu-model-expansion",
|
|
|
|
NULL, test_query_cpu_model_expansion_kvm);
|
2023-02-13 23:29:22 +03:00
|
|
|
|
|
|
|
qtest_add_data_func("/arm/kvm/query-cpu-model-expansion/sve-off",
|
|
|
|
NULL, sve_tests_sve_off_kvm);
|
2019-10-31 17:27:27 +03:00
|
|
|
}
|
|
|
|
|
2023-02-13 23:29:22 +03:00
|
|
|
if (qtest_has_accel("tcg")) {
|
target/arm/cpu64: max cpu: Introduce sve<N> properties
Introduce cpu properties to give fine control over SVE vector lengths.
We introduce a property for each valid length up to the current
maximum supported, which is 2048-bits. The properties are named, e.g.
sve128, sve256, sve384, sve512, ..., where the number is the number of
bits. See the updates to docs/arm-cpu-features.rst for a description
of the semantics and for example uses.
Note, as sve-max-vq is still present and we'd like to be able to
support qmp_query_cpu_model_expansion with guests launched with e.g.
-cpu max,sve-max-vq=8 on their command lines, then we do allow
sve-max-vq and sve<N> properties to be provided at the same time, but
this is not recommended, and is why sve-max-vq is not mentioned in the
document. If sve-max-vq is provided then it enables all lengths smaller
than and including the max and disables all lengths larger. It also has
the side-effect that no larger lengths may be enabled and that the max
itself cannot be disabled. Smaller non-power-of-two lengths may,
however, be disabled, e.g. -cpu max,sve-max-vq=4,sve384=off provides a
guest the vector lengths 128, 256, and 512 bits.
This patch has been co-authored with Richard Henderson, who reworked
the target/arm/cpu64.c changes in order to push all the validation and
auto-enabling/disabling steps into the finalizer, resulting in a nice
LOC reduction.
Signed-off-by: Andrew Jones <drjones@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Eric Auger <eric.auger@redhat.com>
Tested-by: Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>
Reviewed-by: Beata Michalska <beata.michalska@linaro.org>
Message-id: 20191031142734.8590-5-drjones@redhat.com
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
2019-10-31 17:27:29 +03:00
|
|
|
qtest_add_data_func("/arm/max/query-cpu-model-expansion/sve-max-vq-8",
|
|
|
|
NULL, sve_tests_sve_max_vq_8);
|
|
|
|
qtest_add_data_func("/arm/max/query-cpu-model-expansion/sve-off",
|
|
|
|
NULL, sve_tests_sve_off);
|
|
|
|
}
|
|
|
|
|
2023-02-13 23:29:22 +03:00
|
|
|
out:
|
2019-10-31 17:27:27 +03:00
|
|
|
return g_test_run();
|
|
|
|
}
|