From: David Hildenbrand <david@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Janosch Frank" <frankja@linux.ibm.com>,
"David Hildenbrand" <david@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Halil Pasic" <pasic@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org, "Michael Mueller" <mimu@linux.ibm.com>,
"Jiri Denemark" <jdenemar@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>
Subject: [PATCH v2 0/2] s390x/cpumodel: Introduce dynamic feature group
Date: Mon, 25 Nov 2019 18:20:29 +0100 [thread overview]
Message-ID: <20191125172031.16282-1-david@redhat.com> (raw)
This thread was previously called:
s390x/cpumodel: Introduce "best" model variants
There was recently a discussion regarding CPU model versions. That concept
does not fit s390x where we have a lot of feature variability. I
proposed an alternative approach in [1], which might work for x86 as well
(but I am not sure if x86 still can or wants to switch to that), and
requires only little changes in upper layers.
[1] and patch #2 contains more information on the motivation for this. It
allows, for example, to specify/expand "best feature set possible on this
accelerator, hw and, firmware"
"
Get the best possible feature set (e.g., excluding deprecated features)
for a CPU definition in the configuration
-cpu z14,all-features=off,recommended-features=on
Get the maximum possible feature set (e.g., including deprecated
features) for a CPU definition in the configuration ("everything that
could be enabled"):
-cpu z14,all-features=off,available-features=on
Get all valid features for a CPU definition:
-cpu z14,all-features=on
"
v1 -> v2:
- Use dynamic feature groups instead of new models
[1] https://lists.gnu.org/archive/html/qemu-devel/2019-10/msg07222.html
Cc: Daniel P. Berrangé <berrange@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>
Cc: Jiri Denemark <jdenemar@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>
Cc: Michael Mueller <mimu@linux.ibm.com>
Cc: Peter Maydell <peter.maydell@linaro.org>
David Hildenbrand (2):
s390x/cpumodel: Factor out CPU feature dependencies
s390x/cpumodel: Introduce dynamic feature groups
target/s390x/cpu_features.c | 29 +++++
target/s390x/cpu_features.h | 14 +++
target/s390x/cpu_models.c | 242 +++++++++++++++++++++++++++---------
3 files changed, 228 insertions(+), 57 deletions(-)
--
2.21.0
next reply other threads:[~2019-11-25 17:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 17:20 David Hildenbrand [this message]
2019-11-25 17:20 ` [PATCH v2 1/2] s390x/cpumodel: Factor out CPU feature dependencies David Hildenbrand
2019-11-25 17:20 ` [PATCH v2 2/2] s390x/cpumodel: Introduce dynamic feature groups David Hildenbrand
2019-11-26 7:54 ` Christian Borntraeger
2019-11-26 8:04 ` David Hildenbrand
2019-11-26 12:59 ` Christian Borntraeger
2019-11-26 14:07 ` David Hildenbrand
2019-11-29 19:33 ` Eduardo Habkost
2019-12-02 9:15 ` David Hildenbrand
2019-12-05 14:35 ` Eduardo Habkost
2019-12-05 14:48 ` David Hildenbrand
2019-12-09 23:29 ` Eduardo Habkost
2019-12-12 15:27 ` David Hildenbrand
2019-11-25 23:20 ` [PATCH v2 0/2] s390x/cpumodel: Introduce dynamic feature group no-reply
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=20191125172031.16282-1-david@redhat.com \
--to=david@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=ehabkost@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=jdenemar@redhat.com \
--cc=mimu@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=peter.maydell@linaro.org \
--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 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).