qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v8 1/2] target/s390x: support SHA-512 extensions


From: David Hildenbrand
Subject: Re: [PATCH v8 1/2] target/s390x: support SHA-512 extensions
Date: Thu, 22 Sep 2022 17:37:55 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.1

On 22.09.22 17:36, Thomas Huth wrote:
On 22/09/2022 16.51, David Hildenbrand wrote:
[...]
Thanks. I'll resend this patch only as reply to your original one,
so Thomas can easily pick it up (or add more feedback :)).

We're also missing the machine compat handling ... could you
add something like this on top:

diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c
--- a/hw/s390x/s390-virtio-ccw.c
+++ b/hw/s390x/s390-virtio-ccw.c
@@ -803,8 +803,11 @@ DEFINE_CCW_MACHINE(7_2, "7.2", true);
static void ccw_machine_7_1_instance_options(MachineState *machine)
   {
+    static const S390FeatInit qemu_cpu_feat = { S390_FEAT_LIST_QEMU_V7_1 };
+
       ccw_machine_7_2_instance_options(machine);
       s390_cpudef_featoff_greater(16, 1, S390_FEAT_PAIE);
+    s390_set_qemu_cpu_model(0x8561, 15, 1, qemu_cpu_feat);
   }
static void ccw_machine_7_1_class_options(MachineClass *mc)
diff --git a/target/s390x/gen-features.c b/target/s390x/gen-features.c
--- a/target/s390x/gen-features.c
+++ b/target/s390x/gen-features.c
@@ -744,13 +744,16 @@ static uint16_t qemu_V7_0[] = {
       S390_FEAT_MISC_INSTRUCTION_EXT3,
   };
+static uint16_t qemu_V7_1[] = {
+    S390_FEAT_VECTOR_ENH2,
+};
+
   /*
    * Features for the "qemu" CPU model of the latest QEMU machine and the "max"
    * CPU model under TCG. Don't include features that are not part of the full
    * feature set of the current "max" CPU model generation.
    */
   static uint16_t qemu_MAX[] = {
-    S390_FEAT_VECTOR_ENH2,
       S390_FEAT_MSA_EXT_5,
       S390_FEAT_KIMD_SHA_512,
       S390_FEAT_KLMD_SHA_512,
@@ -876,6 +879,7 @@ static FeatGroupDefSpec QemuFeatDef[] = {
       QEMU_FEAT_INITIALIZER(V6_0),
       QEMU_FEAT_INITIALIZER(V6_2),
       QEMU_FEAT_INITIALIZER(V7_0),
+    QEMU_FEAT_INITIALIZER(V7_1),
       QEMU_FEAT_INITIALIZER(MAX),
   };
(otherwise I can also add it when picking up the patch)

He, I just added that already while testing :)

--
Thanks,

David / dhildenb




reply via email to

[Prev in Thread] Current Thread [Next in Thread]