All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Collin Walling <walling@linux.ibm.com>
Cc: qemu-s390x@nongnu.org,  qemu-devel@nongnu.org,
	 mjrosato@linux.ibm.com, farman@linux.ibm.com,
	 cohuck@redhat.com,  david@kernel.org, iii@linux.ibm.com,
	 richard.henderson@linaro.org
Subject: Re: [PATCH] target/s390x: query-cpu-definitions filter deprecated features
Date: Thu, 09 Jul 2026 07:13:42 +0200	[thread overview]
Message-ID: <87mrw0hhix.fsf@pond.sub.org> (raw)
In-Reply-To: <20260708202149.103063-1-walling@linux.ibm.com> (Collin Walling's message of "Wed, 8 Jul 2026 16:21:49 -0400")

Collin Walling <walling@linux.ibm.com> writes:

> Part of the query-cpu-definitions return payload includes an array of
> of "unavailable-features" which helps determine if the CPU model is
> compatible with the system's configuration.  When a KVM guest is
> using a CPU model with deprecated features disabled,
> query-cpu-definitions will claim that certain models are incompatible
> due to these features missing.
>
> Since deprecated features are preferred to be disabled for s390 CPU
> models, lets filter them out from the "missing" features list.
>
> Signed-off-by: Collin Walling <walling@linux.ibm.com>
> ---
>
> Examples output of query-cpu-definitions ran on a gen17a host:
>
> WithOUT patch:
>
> ```
> {
>   "return": [
>     {
>       "name": "z13",
>       "typename": "z13-s390x-cpu",
>       "unavailable-features": [
>         "csske"
>       ],
>       "static": false,
>       "migration-safe": true,
>       "deprecated": false
>     },
>     ...
> ```
>
> WITH patch:
>
> ```
> {
>   "return": [
>     {
>       "name": "z13",
>       "typename": "z13-s390x-cpu",
>       "unavailable-features": [],
>       "static": false,
>       "migration-safe": true,
>       "deprecated": false
>     },
>     ...
> ```

I'd put this right into the commit message.

Possibly stupid question (I know nothing about the subject matter): any
compatibility ramifications?  Does the change need to be tied to machine
type version?



  reply	other threads:[~2026-07-09  5:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 20:21 [PATCH] target/s390x: query-cpu-definitions filter deprecated features Collin Walling
2026-07-09  5:13 ` Markus Armbruster [this message]
2026-07-09 16:50   ` 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=87mrw0hhix.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=david@kernel.org \
    --cc=farman@linux.ibm.com \
    --cc=iii@linux.ibm.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=walling@linux.ibm.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.