From: David Hildenbrand <david@redhat.com>
To: Collin Walling <walling@linux.ibm.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: eduardo@habkost.net, marcel.apfelbaum@gmail.com,
philmd@linaro.org, wangyanan55@huawei.com, eblake@redhat.com,
armbru@redhat.com, richard.henderson@linaro.org,
iii@linux.ibm.com, thuth@redhat.com
Subject: Re: [PATCH v1 2/2] target/s390x: flag te and cte as deprecated
Date: Tue, 12 Sep 2023 08:59:02 +0200 [thread overview]
Message-ID: <49c05a21-3cb3-c7f3-a104-8cf82683c685@redhat.com> (raw)
In-Reply-To: <20230911205232.71735-2-walling@linux.ibm.com>
On 11.09.23 22:52, Collin Walling wrote:
> Add the CONSTRAINT_TRANSACTIONAL_EXE (cte) and TRANSACTIONAL_EXE (te)
> under the list of deprecated features.
>
> Signed-off-by: Collin Walling <walling@linux.ibm.com>
> ---
> target/s390x/cpu_features.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/target/s390x/cpu_features.c b/target/s390x/cpu_features.c
> index efafc9711c..cb4e2b8920 100644
> --- a/target/s390x/cpu_features.c
> +++ b/target/s390x/cpu_features.c
> @@ -218,6 +218,9 @@ void s390_get_deprecated_features(S390FeatBitmap features)
> /* CSSKE is deprecated on newer generations */
> S390_FEAT_CONDITIONAL_SSKE,
> S390_FEAT_BPB,
> + /* Deprecated on z16 */
> + S390_FEAT_CONSTRAINT_TRANSACTIONAL_EXE,
> + S390_FEAT_TRANSACTIONAL_EXE
> };
> int i;
>
We don't have to consider them in init_ignored_base_feat, because they
have never been part of base model I guess?
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-09-12 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 20:52 [PATCH v1 1/2] target/s390x: introduce "host-recommended" option for model expansion Collin Walling
2023-09-11 20:52 ` [PATCH v1 2/2] target/s390x: flag te and cte as deprecated Collin Walling
2023-09-12 6:59 ` David Hildenbrand [this message]
2023-09-12 6:57 ` [PATCH v1 1/2] target/s390x: introduce "host-recommended" option for model expansion David Hildenbrand
2023-09-14 19:28 ` Collin Walling
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=49c05a21-3cb3-c7f3-a104-8cf82683c685@redhat.com \
--to=david@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=iii@linux.ibm.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
--cc=walling@linux.ibm.com \
--cc=wangyanan55@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).