arm: enable MTE for QEMU + kvm
v2 cover arm: enable MTE for QEMU + kvm
This series makes it possible to enable MTE for kvm guests, if the kernel supports it. Again, tested on the simulator via patiently waiting for the arm64/mte kselftests to finish successfully.
For tcg, turning on mte on the machine level (to get tag memory) stays a requirement. If the new mte cpu feature is not explicitly specified, a tcg vm will get mte depending on the presence of tag memory (just as today).
For kvm, mte stays off by default; this is because migration is not yet supported (postcopy will need an extension of the kernel interface, possibly an extension of the userfaultfd interface), and turning on mte will add a migration blocker.
My biggest question going forward is actually concerning migration; I gather that we should not bother adding something unless postcopy is working as well? If I'm not misunderstanding things, we need a way to fault in a page together with the tag; doing that in one go is probably the only way that we can be sure that this is race-free on the QEMU side. Comments welcome :)
Changes v1->v2: [Thanks to Eric for the feedback!]
- add documentation
- switch the mte prop to OnOffAuto; this improves the interaction with the existing mte machine prop
- leave mte off for kvm by default
- improve tests; the poking in QDicts feels a bit ugly, but seems to work
Cornelia Huck (2):
arm/kvm: add support for MTE
qtests/arm: add some mte tests
docs/system/arm/cpu-features.rst | 21 +++++ target/arm/cpu.c | 18 ++--- target/arm/cpu.h | 1 + target/arm/cpu64.c | 132 +++++++++++++++++++++++++++++++ target/arm/internals.h | 1 + target/arm/kvm64.c | 5 ++ target/arm/kvm_arm.h | 12 +++ target/arm/monitor.c | 1 + tests/qtest/arm-cpu-features.c | 77 ++++++++++++++++++ 9 files changed, 256 insertions(+), 12 deletions(-)
Signature · 1 line
2.35.3
RFC PATCH v2 1/2 arm/kvm: add support for MTE
Introduce a new cpu feature flag to control MTE support. To preserve backwards compatibility for tcg, MTE will continue to be enabled as long as tag memory has been provided.
If MTE has been enabled, we need to disable migration, as we do not yet have a way to migrate the tags as well. Therefore, MTE will stay off with KVM unless requested explicitly.
--- docs/system/arm/cpu-features.rst | 21 +++++ target/arm/cpu.c | 18 ++--- target/arm/cpu.h | 1 + target/arm/cpu64.c | 132 +++++++++++++++++++++++++++++++ target/arm/internals.h | 1 + target/arm/kvm64.c | 5 ++ target/arm/kvm_arm.h | 12 +++ target/arm/monitor.c | 1 + 8 files changed, 179 insertions(+), 12 deletions(-)
docs/system/arm/cpu-features.rst +21 -0
@@ -443,3 +443,24 @@ As with ``sve-default-vector-length``, if the default length is larger than the maximum vector length enabled, the actual vector length will be reduced. If this property is set to ``-1`` then the default vector length is set to the maximum possible length. + +MTE CPU Property +================ + +The ``mte`` property controls the Memory Tagging Extension. For TCG, it requires +presence of tag memory (which can be turned on for the ``virt`` machine via +``mte=on``). For KVM, it requires the ``KVM_CAP_ARM_MTE`` capability; until +proper migration support is implemented, enabling MTE will install a migration +blocker. + +If not specified explicitly via ``on`` or ``off``, MTE will be available +according to the following rules: + +* When TCG is used, MTE will be available iff tag memory is available; i. e. it + preserves the behaviour prior to introduction of the feature. + +* When KVM is used, MTE will default to off, so that migration will not + unintentionally be blocked. + +* Other accelerators currently don't support MTE. +
target/arm/cpu.c +6 -12
@@ -1442,6 +1442,11 @@ void arm_cpu_finalize_features(ARMCPU *cpu, Error **errp)error_propagate (errp, local_err); return; } +arm_cpu_mte_finalize (cpu, &local_err); +if (local_err !=NULL ) { +error_propagate (errp, local_err); +return ; + } }#endif
@@ -1518,7 +1523,7 @@ static void arm_cpu_realizefn(DeviceState *dev, Error **errp) }if (cpu->tag_memory) {error_setg (errp, -"Cannot enable %s when guest CPUs has MTE enabled" , +"Cannot enable %s when guest CPUs has tag memory enabled" ,current_accel_name ());return ; }
@@ -1897,17 +1902,6 @@ static void arm_cpu_realizefn(DeviceState *dev, Error **errp) ID_PFR1, VIRTUALIZATION, 0); } -#ifndef CONFIG_USER_ONLY -if (cpu->tag_memory ==NULL &&cpu_isar_feature (aa64_mte, cpu)) { -/* -* Disable the MTE feature bits if we do not have tag-memory -* provided by the machine. -*/ - cpu->isar.id_aa64pfr1 = -FIELD_DP64 (cpu->isar.id_aa64pfr1,ID_AA64PFR1 ,MTE ,0 ); - } -#endif -/* MPU can be configured out of a PMSA CPU either by setting has-mpu * to false or by setting pmsav7-dregion to 0. */
target/arm/cpu.h +1 -0
@@ -1028,6 +1028,7 @@ struct ArchCPU {bool prop_pauth;bool prop_pauth_impdef;bool prop_lpa2; +OnOffAuto prop_mte;/* DCZ blocksize, in log_2(words), ie low 4 bits of DCZID_EL0 */ uint32_t dcz_blocksize;
target/arm/cpu64.c +132 -0
157 lines not on this page · raw message
target/arm/internals.h +1 -0
@@ -1292,6 +1292,7 @@ void arm_cpu_sve_finalize(ARMCPU *cpu, Error **errp);void arm_cpu_sme_finalize (ARMCPU *cpu,Error **errp);void arm_cpu_pauth_finalize (ARMCPU *cpu,Error **errp);void arm_cpu_lpa2_finalize (ARMCPU *cpu,Error **errp); +void arm_cpu_mte_finalize (ARMCPU *cpu,Error **errp);#endif #ifdef CONFIG_USER_ONLY
target/arm/kvm64.c +5 -0
@@ -761,6 +761,11 @@ bool kvm_arm_steal_time_supported(void)return kvm_check_extension (kvm_state,KVM_CAP_STEAL_TIME ); } +bool kvm_arm_mte_supported (void ) +{ +return kvm_check_extension (kvm_state,KVM_CAP_ARM_MTE ); +} +QEMU_BUILD_BUG_ON (KVM_ARM64_SVE_VQ_MIN !=1 );uint32_t kvm_arm_sve_get_vls (CPUState *cs)
target/arm/kvm_arm.h +12 -0
@@ -305,6 +305,13 @@ bool kvm_arm_pmu_supported(void);*/ bool kvm_arm_sve_supported (void ); +/** +* kvm_arm_mte_supported: +* +* Returns: true if KVM can enable MTE, and false otherwise. +*/ +bool kvm_arm_mte_supported (void ); +/** * kvm_arm_get_max_vm_ipa_size: * @ms: Machine state handle
@@ -395,6 +402,11 @@ static inline bool kvm_arm_steal_time_supported(void)return false; } +static inline bool kvm_arm_mte_supported (void ) +{ +return false; +} +/* * These functions should never actually be called without KVM support. */
target/arm/monitor.c +1 -0
@@ -96,6 +96,7 @@ static const char *cpu_model_advertised_features[] = {"sve1408" ,"sve1536" ,"sve1664" ,"sve1792" ,"sve1920" ,"sve2048" ,"kvm-no-adjvtime" ,"kvm-steal-time" ,"pauth" ,"pauth-impdef" , +"mte" ,NULL };
Signature · 1 line
2.35.3
RFC PATCH v2 2/2 qtests/arm: add some mte tests
In reply to Cornelia Huck--- tests/qtest/arm-cpu-features.c | 77 ++++++++++++++++++++++++++++++++++ 1 file changed, 77 insertions(+)
tests/qtest/arm-cpu-features.c +77 -0
@@ -22,6 +22,7 @@#define MACHINE "-machine virt,gic-version=max -accel tcg "#define MACHINE_KVM "-machine virt,gic-version=max -accel kvm -accel tcg " +#define MACHINE_MTE "-machine virt,gic-version=max,mte=on -accel tcg "#define QUERY_HEAD "{ 'execute': 'query-cpu-model-expansion', " \ " 'arguments': { 'type': 'full', "#define QUERY_TAIL "}}"
@@ -155,6 +156,18 @@ static bool resp_get_feature(QDict *resp, const char *feature)g_assert (qdict_get_bool (_props, feature) == (expected_value)); \ }) +#define resp_assert_feature_str (resp, feature, expected_value) \ +({ \ + QDict *_props; \ + \ + g_assert(_resp); \ + g_assert(resp_has_props(_resp)); \ + _props = resp_get_props(_resp); \ + g_assert(qdict_get(_props, feature)); \ + g_assert_cmpstr(qdict_get_try_str(_props, feature), ==, \ + expected_value); \ +}) +#define assert_feature (qts, cpu_type, feature, expected_value) \ ({ \ QDict *_resp; \
@@ -165,6 +178,16 @@ static bool resp_get_feature(QDict *resp, const char *feature)qobject_unref (_resp); \ }) +#define assert_feature_str (qts, cpu_type, feature, expected_value) \ +({ \ + QDict *_resp; \ + \ + _resp = do_query_no_props(qts, cpu_type); \ + g_assert(_resp); \ + resp_assert_feature_str(_resp, feature, expected_value); \ + qobject_unref(_resp); \ +}) +#define assert_set_feature (qts, cpu_type, feature, value) \ ({ \ const char *_fmt = (value) ? "{ %s: true }" : "{ %s: false }"; \
@@ -176,6 +199,16 @@ static bool resp_get_feature(QDict *resp, const char *feature)qobject_unref (_resp); \ }) +#define assert_set_feature_str (qts, cpu_type, feature, value, _fmt) \ +({ \ + QDict *_resp; \ + \ + _resp = do_query(qts, cpu_type, _fmt, feature); \ + g_assert(_resp); \ + resp_assert_feature_str(_resp, feature, value); \ + qobject_unref(_resp); \ +}) +#define assert_has_feature_enabled (qts, cpu_type, feature) \ assert_feature(qts, cpu_type, feature, true)
@@ -412,6 +445,24 @@ static void sve_tests_sve_off_kvm(const void *data)qtest_quit (qts); } +static void mte_tests_tag_memory_on (const void *data) +{ +QTestState *qts; + + qts =qtest_init (MACHINE_MTE "-cpu max" ); + +/* +* With tag memory, "mte" should default to on, and explicitly specifying +* either on or off should be fine. +*/ +assert_has_feature (qts,"max" ,"mte" ); + +assert_set_feature_str (qts,"max" ,"mte" ,"off" ,"{ 'mte': 'off' }" ); +assert_set_feature_str (qts,"max" ,"mte" ,"on" ,"{ 'mte': 'on' }" ); + +qtest_quit (qts); +} +static void pauth_tests_default (QTestState *qts,const char *cpu_type) {assert_has_feature_enabled (qts, cpu_type,"pauth" );
@@ -424,6 +475,21 @@ static void pauth_tests_default(QTestState *qts, const char *cpu_type) "{ 'pauth': false, 'pauth-impdef': true }"); } +static void mte_tests_default (QTestState *qts,const char *cpu_type) +{ +assert_has_feature (qts, cpu_type,"mte" ); + +/* +* Without tag memory, mte will be off under tcg. +* Explicitly enabling it yields an error. +*/ +assert_has_feature (qts, cpu_type,"mte" ); + +assert_set_feature_str (qts,"max" ,"mte" ,"off" ,"{ 'mte': 'off' }" ); +assert_error (qts, cpu_type,"mte=on requires tag memory" , +"{ 'mte': 'on' }" ); +} +static void test_query_cpu_model_expansion (const void *data) {QTestState *qts;
@@ -473,6 +539,7 @@ static void test_query_cpu_model_expansion(const void *data)sve_tests_default (qts,"max" );pauth_tests_default (qts,"max" ); +mte_tests_default (qts,"max" );/* Test that features that depend on KVM generate errors without. */ assert_error(qts, "max",
@@ -499,6 +566,7 @@ static void test_query_cpu_model_expansion_kvm(const void *data)if (g_str_equal (qtest_get_arch (),"aarch64" )) {bool kvm_supports_steal_time;bool kvm_supports_sve; +bool kvm_supports_mte;char max_name[8 ], name[8 ];uint32_t max_vq, vq;uint64_t vls;
@@ -523,10 +591,12 @@ static void test_query_cpu_model_expansion_kvm(const void *data)*/ assert_has_feature (qts,"host" ,"kvm-steal-time" );assert_has_feature (qts,"host" ,"sve" ); +assert_has_feature (qts,"host" ,"mte" ); resp =do_query_no_props (qts,"host" ); kvm_supports_steal_time =resp_get_feature (resp,"kvm-steal-time" ); kvm_supports_sve =resp_get_feature (resp,"sve" ); + kvm_supports_mte =resp_get_feature (resp,"mte" ); vls =resp_get_sve_vls (resp);qobject_unref (resp);
@@ -592,6 +662,11 @@ static void test_query_cpu_model_expansion_kvm(const void *data) }else {g_assert (vls ==0 ); } +if (kvm_supports_mte) { +/* If we have mte then we should be able to toggle it. */ +assert_set_feature (qts,"host" ,"mte" , false); +assert_set_feature (qts,"host" ,"mte" , true); + } }else {assert_has_not_feature (qts,"host" ,"aarch64" );assert_has_not_feature (qts,"host" ,"pmu" );
@@ -630,6 +705,8 @@ int main(int argc, char **argv) NULL, sve_tests_sve_off);qtest_add_data_func ("/arm/kvm/query-cpu-model-expansion/sve-off" ,NULL , sve_tests_sve_off_kvm); +qtest_add_data_func ("/arm/max/query-cpu-model-expansion/tag-memory" , +NULL , mte_tests_tag_memory_on); }return g_test_run ();
Signature · 1 line
2.35.3
Quoted 3 lines · Cornelia Huck
If I'm not misunderstanding things, we need a way to fault in a page together with the tag; doing that in one go is probably the only way that we can be sure that this is race-free on the QEMU side.
That's my understanding as well.
r~
Quoted 4 lines · * Cornelia Huck ([email protected]) wrote:
This series makes it possible to enable MTE for kvm guests, if the kernel supports it. Again, tested on the simulator via patiently waiting for the arm64/mte kselftests to finish successfully.
Quoted 8 lines
For tcg, turning on mte on the machine level (to get tag memory) stays a requirement. If the new mte cpu feature is not explicitly specified, a tcg vm will get mte depending on the presence of tag memory (just as today).
For kvm, mte stays off by default; this is because migration is not yet supported (postcopy will need an extension of the kernel interface, possibly an extension of the userfaultfd interface), and turning on mte will add a migration blocker.
My assumption was that a normal migration would need something as well to retrieve and place the MTE flags; albeit not atomically.
Quoted 2 lines
My biggest question going forward is actually concerning migration; I gather that we should not bother adding something unless postcopy is working as well?
I don't think that restriction is fair on you; just make sure postcopy_ram_supported_by_host gains an arch call and fails cleanly; that way if anyone tries to enable postcopy they'll find out with a clean fail.
Quoted 3 lines
If I'm not misunderstanding things, we need a way to fault in a page together with the tag; doing that in one go is probably the only way that we can be sure that this is race-free on the QEMU side. Comments welcome :)
I think it will.
But, ignoring postcopy for a minute, with KVM how do different types of backing memory work - e.g. if I back a region of guest memory with /dev/shm/something or a hugepage equivalent, where does the MTE memory come from, and how do you set it?
Dave
Quoted 25 lines
Changes
v1->v2: [Thanks to Eric for the feedback!]
- add documentation
- switch the mte prop to OnOffAuto; this improves the interaction with the existing mte machine prop
- leave mte off for kvm by default
- improve tests; the poking in QDicts feels a bit ugly, but seems to workCornelia Huck (2):
arm/kvm: add support for MTE
qtests/arm: add some mte testsdocs/system/arm/cpu-features.rst | 21 +++++ target/arm/cpu.c | 18 ++--- target/arm/cpu.h | 1 + target/arm/cpu64.c | 132 +++++++++++++++++++++++++++++++ target/arm/internals.h | 1 + target/arm/kvm64.c | 5 ++ target/arm/kvm_arm.h | 12 +++ target/arm/monitor.c | 1 + tests/qtest/arm-cpu-features.c | 77 ++++++++++++++++++ 9 files changed, 256 insertions(+), 12 deletions(-)Signature · 1 line
2.35.3
Signature · 1 line
Dr. David Alan Gilbert / [email protected] / Manchester, UK
Quoted 4 lines · Dr. David Alan Gilbert
But, ignoring postcopy for a minute, with KVM how do different types of backing memory work - e.g. if I back a region of guest memory with
/dev/shm/somethingor a hugepage equivalent, where does the MTE memory come from, and how do you set it?
Generally in an MTE system anything that's "plain old RAM" is expected to support tags. (The architecture manual calls this "conventional memory". This isn't quite the same as "anything that looks RAM-like", e.g. the graphics card framebuffer doesn't have to support tags!)
One plausible implementation is that the firmware and memory controller are in cahoots and arrange that the appropriate fraction of the DRAM is reserved for holding tags (and inaccessible as normal RAM even by the OS); but where the tags are stored is entirely impdef and an implementation could choose to put the tags in their own entirely separate storage if it liked. The only way to access the tag storage is via the instructions for getting and setting tags.
-- PMM
Quoted 11 lines · * Peter Maydell ([email protected]) wrote:
Quoted 4 lines · Dr. David Alan Gilbert
But, ignoring postcopy for a minute, with KVM how do different types of backing memory work - e.g. if I back a region of guest memory with
/dev/shm/somethingor a hugepage equivalent, where does the MTE memory come from, and how do you set it?Generally in an MTE system anything that's "plain old RAM" is expected to support tags. (The architecture manual calls this "conventional memory". This isn't quite the same as "anything that looks RAM-like", e.g. the graphics card framebuffer doesn't have to support tags!)
I guess things like non-volatile disks mapped as DAX are fun edge cases.
Quoted 7 lines
One plausible implementation is that the firmware and memory controller are in cahoots and arrange that the appropriate fraction of the DRAM is reserved for holding tags (and inaccessible as normal RAM even by the OS); but where the tags are stored is entirely impdef and an implementation could choose to put the tags in their own entirely separate storage if it liked. The only way to access the tag storage is via the instructions for getting and setting tags.
Hmm OK; In postcopy, at the moment, the call qemu uses is a call that
atomically places a page of data in memory and then tells the vCPUs to continue. I guess a variant that took an extra blob of MTE data would do.
Note that other VMMs built on kvm work in different ways; the other common way is to write into the backing file (i.e. the /dev/shm whatever atomically somehow) and then do the userfault call to tell the vcpus to continue. It looks like this is the way things will work in the split hugepage mechanism Google are currently adding.
Dave
Quoted 2 lines
-- PMM
Signature · 1 line
Dr. David Alan Gilbert / [email protected] / Manchester, UK
Quoted 23 lines · Dr. David Alan Gilbert
Quoted 11 lines · * Peter Maydell ([email protected]) wrote:
Quoted 4 lines · Dr. David Alan Gilbert
But, ignoring postcopy for a minute, with KVM how do different types of backing memory work - e.g. if I back a region of guest memory with
/dev/shm/somethingor a hugepage equivalent, where does the MTE memory come from, and how do you set it?Generally in an MTE system anything that's "plain old RAM" is expected to support tags. (The architecture manual calls this "conventional memory". This isn't quite the same as "anything that looks RAM-like", e.g. the graphics card framebuffer doesn't have to support tags!)
I guess things like non-volatile disks mapped as DAX are fun edge cases.
Quoted 7 lines
One plausible implementation is that the firmware and memory controller are in cahoots and arrange that the appropriate fraction of the DRAM is reserved for holding tags (and inaccessible as normal RAM even by the OS); but where the tags are stored is entirely impdef and an implementation could choose to put the tags in their own entirely separate storage if it liked. The only way to access the tag storage is via the instructions for getting and setting tags.
Quoted 4 lines
Hmm OK; In postcopy, at the moment, the call qemu uses is a call that
atomically places a page of data in memory and then tells the vCPUs to continue. I guess a variant that took an extra blob of MTE data would do.
Yes, the current idea is to extend UFFDIO_COPY with a flag so that we get the tag data along with the page.
Quoted 5 lines
Note that other VMMs built on kvm work in different ways; the other common way is to write into the backing file (i.e. the
/dev/shmwhatever atomically somehow) and then do the userfault call to tell the vcpus to continue. It looks like this is the way things will work in the split hugepage mechanism Google are currently adding.
Hmm... I had the impression that other VMMs had not cared about this particular use case yet; if they need a slightly different mechanism, it would complicate things a bit.
Quoted 39 lines · * Cornelia Huck ([email protected]) wrote:
Quoted 23 lines · Dr. David Alan Gilbert
Quoted 11 lines · * Peter Maydell ([email protected]) wrote:
Quoted 4 lines · Dr. David Alan Gilbert
But, ignoring postcopy for a minute, with KVM how do different types of backing memory work - e.g. if I back a region of guest memory with
/dev/shm/somethingor a hugepage equivalent, where does the MTE memory come from, and how do you set it?Generally in an MTE system anything that's "plain old RAM" is expected to support tags. (The architecture manual calls this "conventional memory". This isn't quite the same as "anything that looks RAM-like", e.g. the graphics card framebuffer doesn't have to support tags!)
I guess things like non-volatile disks mapped as DAX are fun edge cases.
Quoted 7 lines
One plausible implementation is that the firmware and memory controller are in cahoots and arrange that the appropriate fraction of the DRAM is reserved for holding tags (and inaccessible as normal RAM even by the OS); but where the tags are stored is entirely impdef and an implementation could choose to put the tags in their own entirely separate storage if it liked. The only way to access the tag storage is via the instructions for getting and setting tags.
Quoted 4 lines
Hmm OK; In postcopy, at the moment, the call qemu uses is a call that
atomically places a page of data in memory and then tells the vCPUs to continue. I guess a variant that took an extra blob of MTE data would do.Yes, the current idea is to extend
UFFDIO_COPYwith a flag so that we get the tag data along with the page.Quoted 5 lines
Note that other VMMs built on kvm work in different ways; the other common way is to write into the backing file (i.e. the
/dev/shmwhatever atomically somehow) and then do the userfault call to tell the vcpus to continue. It looks like this is the way things will work in the split hugepage mechanism Google are currently adding.
Quoted 3 lines
Hmm... I had the impression that other VMMs had not cared about this particular use case yet; if they need a slightly different mechanism, it would complicate things a bit.
I think Google's internal VMM doesn't use UFFDIO_COPY - but I don't have details to be sure of that.
Dave
Signature · 1 line
Dr. David Alan Gilbert / [email protected] / Manchester, UK
Quoted 29 lines · * Dr. David Alan Gilbert ([email protected]) wrote:
Quoted 4 lines · * Cornelia Huck ([email protected]) wrote:
This series makes it possible to enable MTE for kvm guests, if the kernel supports it. Again, tested on the simulator via patiently waiting for the arm64/mte kselftests to finish successfully.
Quoted 8 lines
For tcg, turning on mte on the machine level (to get tag memory) stays a requirement. If the new mte cpu feature is not explicitly specified, a tcg vm will get mte depending on the presence of tag memory (just as today).
For kvm, mte stays off by default; this is because migration is not yet supported (postcopy will need an extension of the kernel interface, possibly an extension of the userfaultfd interface), and turning on mte will add a migration blocker.
My assumption was that a normal migration would need something as well to retrieve and place the MTE flags; albeit not atomically.
Quoted 2 lines
My biggest question going forward is actually concerning migration; I gather that we should not bother adding something unless postcopy is working as well?
I don't think that restriction is fair on you; just make sure
postcopy_ram_supported_by_hostgains an arch call and fails cleanly; that way if anyone tries to enable postcopy they'll find out with a clean fail.Quoted 3 lines
If I'm not misunderstanding things, we need a way to fault in a page together with the tag; doing that in one go is probably the only way that we can be sure that this is race-free on the QEMU side. Comments welcome :)
Quoted 5 lines
I think it will.
But, ignoring postcopy for a minute, with KVM how do different types of backing memory work - e.g. if I back a region of guest memory with/dev/shm/somethingor a hugepage equivalent, where does the MTE memory come from, and how do you set it?
Another case that just came to mind, are the data content optimisations; we special case all-zero pages, which I guess you still need to transmit tags for, and the xbzrle page-difference code wouldn't notice differences in tags.
Dave
Quoted 29 lines
Dave
Quoted 25 lines
Changes
v1->v2: [Thanks to Eric for the feedback!]
- add documentation
- switch the mte prop to OnOffAuto; this improves the interaction with the existing mte machine prop
- leave mte off for kvm by default
- improve tests; the poking in QDicts feels a bit ugly, but seems to workCornelia Huck (2):
arm/kvm: add support for MTE
qtests/arm: add some mte testsdocs/system/arm/cpu-features.rst | 21 +++++ target/arm/cpu.c | 18 ++--- target/arm/cpu.h | 1 + target/arm/cpu64.c | 132 +++++++++++++++++++++++++++++++ target/arm/internals.h | 1 + target/arm/kvm64.c | 5 ++ target/arm/kvm_arm.h | 12 +++ target/arm/monitor.c | 1 + tests/qtest/arm-cpu-features.c | 77 ++++++++++++++++++ 9 files changed, 256 insertions(+), 12 deletions(-)Signature · 1 line
2.35.3Signature · 1 line
Dr. David Alan Gilbert / [email protected] / Manchester, UK
Signature · 1 line
Dr. David Alan Gilbert / [email protected] / Manchester, UK
Quoted 8 lines · Dr. David Alan Gilbert
Quoted 4 lines · * Cornelia Huck ([email protected]) wrote:
For kvm, mte stays off by default; this is because migration is not yet supported (postcopy will need an extension of the kernel interface, possibly an extension of the userfaultfd interface), and turning on mte will add a migration blocker.
My assumption was that a normal migration would need something as well to retrieve and place the MTE flags; albeit not atomically.
There's KVM_ARM_MTE_COPY_TAGS, which should be sufficient to move tags around for normal migration.
Quoted 8 lines
Quoted 3 lines
My biggest question going forward is actually concerning migration; I gather that we should not bother adding something unless postcopy is working as well?
I don't think that restriction is fair on you; just make sure
postcopy_ram_supported_by_hostgains an arch call and fails cleanly; that way if anyone tries to enable postcopy they'll find out with a clean fail.
Ok, if simply fencing off postcopy is fine, we can try to move forward with what we have now. The original attempt at
https://lore.kernel.org/all/881871e8394fa18a656dfb105d42e6099335c721.1615972140.git.haibo.xu@linaro.org/
hooked itself directly into common code; maybe we should rather copy the approach used for s390 storage keys (extra "device") instead?
Quoted 23 lines · * Cornelia Huck ([email protected]) wrote:
Quoted 8 lines · Dr. David Alan Gilbert
Quoted 4 lines · * Cornelia Huck ([email protected]) wrote:
For kvm, mte stays off by default; this is because migration is not yet supported (postcopy will need an extension of the kernel interface, possibly an extension of the userfaultfd interface), and turning on mte will add a migration blocker.
My assumption was that a normal migration would need something as well to retrieve and place the MTE flags; albeit not atomically.
There's
KVM_ARM_MTE_COPY_TAGS, which should be sufficient to move tags around for normal migration.Quoted 8 lines
Quoted 3 lines
My biggest question going forward is actually concerning migration; I gather that we should not bother adding something unless postcopy is working as well?
I don't think that restriction is fair on you; just make sure
postcopy_ram_supported_by_hostgains an arch call and fails cleanly; that way if anyone tries to enable postcopy they'll find out with a clean fail.
Quoted 5 lines
Ok, if simply fencing off postcopy is fine, we can try to move forward with what we have now. The original attempt at
https://lore.kernel.org/all/881871e8394fa18a656dfb105d42e6099335c721.1615972140.git.haibo.xu@linaro.org/
hooked itself directly into common code; maybe we should rather copy the approach used for s390 storage keys (extra "device") instead?
I don't understand how a separate device would keep the idea of page changed flags coherent with the main RAM that the tags correspond to.
Dave
Signature · 1 line
Dr. David Alan Gilbert / [email protected] / Manchester, UK