From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>, qemu-devel@nongnu.org
Cc: "Daniel P . Berrangé" <berrange@redhat.com>,
qemu-s390x@nongnu.org,
"Richard Henderson" <richard.henderson@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"David Hildenbrand" <david@redhat.com>
Subject: Re: [PATCH v1 2/2] s390x/cpu_models: make "max" match the unmodified "qemu" CPU model under TCG
Date: Wed, 23 Mar 2022 12:20:24 +0100 [thread overview]
Message-ID: <878rt07w5j.fsf@redhat.com> (raw)
In-Reply-To: <20220322112256.118417-3-david@redhat.com>
On Tue, Mar 22 2022, David Hildenbrand <david@redhat.com> wrote:
> Before we were able to bump up the qemu CPU model to a z13, we included
> some experimental features during development in the "max" model only.
> Nowadays, the "max" model corresponds exactly to the "qemu" CPU model
> of the latest QEMU machine under TCG.
>
> Let's remove all the special casing, effectively making both models
> match completely from now on, and clean up.
>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
> target/s390x/cpu_models.c | 26 +++++++-------------------
> target/s390x/gen-features.c | 11 ++++++-----
> 2 files changed, 13 insertions(+), 24 deletions(-)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2022-03-23 11:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 11:22 [PATCH v1 0/2] s390x/cpu_models: make "max" match the unmodified "qemu" CPU model under TCG David Hildenbrand
2022-03-22 11:22 ` [PATCH v1 1/2] s390x/cpu_models: drop "msa5" from the TCG "max" model David Hildenbrand
2022-03-22 16:41 ` Thomas Huth
2022-03-23 11:18 ` Cornelia Huck
2022-03-22 11:22 ` [PATCH v1 2/2] s390x/cpu_models: make "max" match the unmodified "qemu" CPU model under TCG David Hildenbrand
2022-03-23 11:20 ` Cornelia Huck [this message]
2022-03-22 15:06 ` [PATCH v1 0/2] " Richard Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rt07w5j.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=berrange@redhat.com \
--cc=david@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.