From: David Hildenbrand <david@redhat.com>
To: Richard Henderson <rth@twiddle.net>, qemu-devel@nongnu.org
Cc: thuth@redhat.com, aurelien@aurel32.net
Subject: Re: [Qemu-devel] [PATCH v2] target/s390x: Enforce instruction features
Date: Mon, 19 Jun 2017 09:52:21 +0200 [thread overview]
Message-ID: <e989e9c7-ed59-fc97-7fa4-4b309762b176@redhat.com> (raw)
In-Reply-To: <20170616051526.6814-1-rth@twiddle.net>
On 16.06.2017 07:15, Richard Henderson wrote:
> Introduce a synthetic feature (type MISC) to handle disabling of
> the enforcing of features at translation time.
>
> Signed-off-by: Richard Henderson <rth@twiddle.net>
> ---
> target/s390x/cpu_features.c | 4 +++-
> target/s390x/cpu_features_def.h | 1 +
> target/s390x/cpu_models.c | 5 +++++
> target/s390x/translate.c | 9 +++++++++
> 4 files changed, 18 insertions(+), 1 deletion(-)
>
> diff --git a/target/s390x/cpu_features.c b/target/s390x/cpu_features.c
> index 42fd9d7..8d542c0 100644
> --- a/target/s390x/cpu_features.c
> +++ b/target/s390x/cpu_features.c
> @@ -24,7 +24,7 @@
> }
>
> /* indexed by feature number for easy lookup */
> -static const S390FeatDef s390_features[] = {
> +static const S390FeatDef s390_features[S390_FEAT_MAX] = {
> FEAT_INIT("esan3", S390_FEAT_TYPE_STFL, 0, "Instructions marked as n3"),
> FEAT_INIT("zarch", S390_FEAT_TYPE_STFL, 1, "z/Architecture architectural mode"),
> FEAT_INIT("dateh", S390_FEAT_TYPE_STFL, 3, "DAT-enhancement facility"),
> @@ -251,6 +251,8 @@ static const S390FeatDef s390_features[] = {
> FEAT_INIT("pcc-xts-eaes-256", S390_FEAT_TYPE_PCC, 60, "PCC Compute-XTS-Parameter-Using-Encrypted-AES-256"),
>
> FEAT_INIT("ppno-sha-512-drng", S390_FEAT_TYPE_PPNO, 3, "PPNO SHA-512-DRNG"),
> +
> + FEAT_INIT("tcg-all-insns", S390_FEAT_TYPE_MISC, 0, "Enable all insns supported by TCG"),
Very mixed feelings about fake features. Will return
strange/wrong/misleading information on baselining/comparing..... I
don't like this.
Basically also because this is a temporary hack and will - in theory -
be dropped at one point. nack from my side.
Can't we just handle the qemu model special as proposed?
--
Thanks,
David
prev parent reply other threads:[~2017-06-19 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 5:15 [Qemu-devel] [PATCH v2] target/s390x: Enforce instruction features Richard Henderson
2017-06-16 8:55 ` no-reply
2017-06-19 7:52 ` David Hildenbrand [this message]
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=e989e9c7-ed59-fc97-7fa4-4b309762b176@redhat.com \
--to=david@redhat.com \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--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 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).