From: "Ján Tomko" <jtomko@redhat.com>
To: Greg Kurz <groug@kaod.org>
Cc: libvir-list@redhat.com, qemu-ppc@nongnu.org,
qemu-devel@nongnu.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] target/ppc: Remove "compat" property of server class POWER CPUs
Date: Tue, 1 Dec 2020 15:49:58 +0100 [thread overview]
Message-ID: <20201201144958.GA79432@lpt> (raw)
In-Reply-To: <20201201131103.897430-1-groug@kaod.org>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
On a Tuesday in 2020, Greg Kurz wrote:
>This property has been deprecated since QEMU 5.0 by commit 22062e54bb68.
>We only kept a legacy hack that internally converts "compat" into the
>official "max-cpu-compat" property of the pseries machine type.
>
>According to our deprecation policy, we could have removed it for QEMU 5.2
>already. Do it now ; since ppc_cpu_parse_featurestr() now just calls the
>generic parent_parse_features handler, drop it as well.
>
>Users are supposed to use the "max-cpu-compat" property of the pseries
>machine type instead.
>
For libvirt:
Reviewed-by: Ján Tomko <jtomko@redhat.com>
We use the new option as of libvirt commit:
commit 2b041dc8c7b70e762d99b6bd7805daa9961740f6
Author: Shivaprasad G Bhat <sbhat@linux.vnet.ibm.com>
AuthorDate: 2018-01-05 19:18:00 +0530
Commit: Andrea Bolognani <abologna@redhat.com>
CommitDate: 2018-01-05 17:12:14 +0100
qemu: Add support for pseries machine's max-cpu-compat= parameter
Jano
>Signed-off-by: Greg Kurz <groug@kaod.org>
>---
> docs/system/deprecated.rst | 7 ----
> target/ppc/translate_init.c.inc | 59 ---------------------------------
> 2 files changed, 66 deletions(-)
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-12-01 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 13:11 [PATCH] target/ppc: Remove "compat" property of server class POWER CPUs Greg Kurz
2020-12-01 13:35 ` Greg Kurz
2020-12-01 14:49 ` Ján Tomko [this message]
2020-12-02 3:16 ` David Gibson
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=20201201144958.GA79432@lpt \
--to=jtomko@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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.