From: Michael Mueller <mimu@linux.vnet.ibm.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
Gleb Natapov <gleb@kernel.org>,
qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
"Jason J. Herne" <jjherne@linux.vnet.ibm.com>,
Daniel Hansel <daniel.hansel@linux.vnet.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Andreas Faerber <afaerber@suse.de>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v6 15/17] target-s390x: Extend arch specific QMP command query-cpu-definitions
Date: Wed, 6 May 2015 16:48:57 +0200 [thread overview]
Message-ID: <20150506164857.5df6a1ae@bee> (raw)
In-Reply-To: <20150506123741.GH25766@thinpad.lan.raisama.net>
On Wed, 6 May 2015 09:37:41 -0300
Eduardo Habkost <ehabkost@redhat.com> wrote:
> On Mon, Apr 27, 2015 at 04:53:29PM +0200, Michael Mueller wrote:
> [...]
> > #ifndef CONFIG_USER_ONLY
> > +static CpuDefinitionInfoList *qmp_query_cpu_definition_host(void)
> > +{
> > + CpuDefinitionInfoList *host = NULL;
> > + CpuDefinitionInfo *info;
> > +
> > + info = g_try_new0(CpuDefinitionInfo, 1);
> > + if (!info) {
> > + goto out;
> > + }
> > + info->name = g_strdup("host");
> > +
> > + host = g_try_new0(CpuDefinitionInfoList, 1);
> > + if (!host) {
> > + g_free(info->name);
> > + g_free(info);
> > + goto out;
> > + }
> > + host->value = info;
> > +out:
> > + return host;
> > +}
> [...]
> > CpuDefinitionInfoList *arch_query_cpu_definitions(bool has_machine,
> > const char *machine,
> > bool has_accel,
> > AccelId accel,
> > Error **errp)
> > {
> > - CpuDefinitionInfoList *entry;
> > - CpuDefinitionInfo *info;
> > + S390MachineProps mach;
> > + GSList *classes;
> > + uint64_t *mask = NULL;
> > + CpuDefinitionInfoList *list = NULL;
> > +
> > + if (has_machine) {
> > + mask = s390_fac_list_mask_by_machine(machine);
> > + if (!mask) {
> > + error_set(errp, QERR_INVALID_PARAMETER_VALUE, "machine",
> > + "a valid machine type");
> > + return NULL;
> > + }
> > + }
>
> I would like to understand better the meaning of "runnable" when machine
> is omitted. Is it really possible to tell if a CPU model is runnable if
> no machine/mask info is provided as input?
Yes it is. The list of runnable CPU models is derived from the set of S390 CPU
facilities available. One subset of facilities depends on the accelerator and
the second on the capabilities of QEMU which is represented by the mask. In the
case the no machine is specified only those of the accelerator are taken into
account for the calculation.
It is even possible to omit both, the accelerator and the machine, in that case
only the model none is runnable and becomes the default:
{"return":[{"order":3345,"name":"2964-ga1","live-migration-safe":true},{"name":"zBC12"},
{"name":"2828"},{"order":3105,"name":"2828-ga1","live-migration-safe":true},{"name":"host"},
{"name":"zEC12"},{"name":"2827"},{"order":3090,"name":"2827-ga2","live-migration-safe":true},
{"order":3089,"name":"2827-ga1","live-migration-safe":true},{"name":"z114"},{"name":"2818"},
{"order":2849,"name":"2818-ga1","live-migration-safe":true},{"name":"z196"},{"name":"2817"},
{"order":2834,"name":"2817-ga2","live-migration-safe":true},{"order":2833,"name":"2817-ga1",
"live-migration-safe":true},{"name":"z10-bc"},{"name":"2098"},{"order":2594,"name":"2098-ga2",
"live-migration-safe":true},{"order":2593,"name":"2098-ga1","live-migration-safe":true},
{"name":"z10-ec"},{"name":"z10"},{"name":"2097"},{"order":2579,"name":"2097-ga3",
"live-migration-safe":true},{"order":2578,"name":"2097-ga2","live-migration-safe":true},
{"order":2577,"name":"2097-ga1","live-migration-safe":true},{"name":"z9-bc"},{"name":"2096"},
{"order":2338,"name":"2096-ga2","live-migration-safe":true},{"order":2337,"name":"2096-ga1",
"live-migration-safe":true},{"name":"z9-ec"},{"name":"z9"},{"name":"2094"},{"order":2323,
"name":"2094-ga3","live-migration-safe":true},{"order":2322,"name":"2094-ga2",
"live-migration-safe":true},{"name":"z9-109"},{"order":2321,"name":"2094-ga1",
"live-migration-safe":true},{"name":"z890"},{"name":"2086"},{"order":2083,"name":"2086-ga3",
"live-migration-safe":true},{"order":2082,"name":"2086-ga2","live-migration-safe":true},
{"order":2081,"name":"2086-ga1","live-migration-safe":true},{"name":"z990"},{"name":"2084"},
{"order":2069,"name":"2084-ga5","live-migration-safe":true},{"order":2068,"name":"2084-ga4",
"live-migration-safe":true},{"order":2067,"name":"2084-ga3","live-migration-safe":true},
{"order":2066,"name":"2084-ga2","live-migration-safe":true},{"order":2065,"name":"2084-ga1",
"live-migration-safe":true},{"name":"z800"},{"name":"2066"},{"order":1825,"name":"2066-ga1",
"live-migration-safe":true},{"name":"z900"},{"name":"2064"},{"order":1811,"name":"2064-ga3",
"live-migration-safe":true},{"order":1810,"name":"2064-ga2","live-migration-safe":true},
{"order":1809,"name":"2064-ga1","live-migration-safe":true},{"name":"none","runnable":true,
"is-default":true}],"id":"libvirt-15"}
>
> If machine is omitted and the command returns runnable=true, does that
> mean the CPU model is runnable using any machine? Does it mean it is
> runnable using some of the available machines? If so, which ones? Does
> it mean something else?
As it is a lower limit all machines shall be able to run it. Although a somewhat
clever management interface should iterate through all accel/machine combinations.
>
> >
> > - info = g_malloc0(sizeof(*info));
> > - info->name = g_strdup("host");
> > + memset(&mach, 0, sizeof(mach));
> > + if (has_accel) {
> > + switch (accel) {
> > + case ACCEL_ID_KVM:
> > + kvm_s390_get_machine_props(NULL, &mach);
> > + break;
> > + default:
> > + return qmp_query_cpu_definition_host();
>
> This will return only a single element. I don't think that's correct. If
> machine or accel is omitted, I believe we should just omit the
> "runnable" field, but always return the full list of CPU models.
That is the !KVM case where I keep the behavior currently unchanged to
the existing implementation. But right for the TCG case there has to be
a comparable get_machine_props() call returning whatever TCG is implementing.
But that is not part of this patch series.
>
> > + }
> > + }
> >
> > - entry = g_malloc0(sizeof(*entry));
> > - entry->value = info;
> > + s390_setup_cpu_classes(ACCEL_TEMP, &mach, mask);
> > +
> > + classes = object_class_get_list(TYPE_S390_CPU, false);
> > + classes = g_slist_sort(classes, s390_cpu_class_asc_order_compare);
> > + g_slist_foreach(classes, qmp_query_cpu_definition_entry, &list);
> > + g_slist_free(classes);
> >
> > - return entry;
> > + return list;
> > }
> > #endif
> >
> [...]
>
next prev parent reply other threads:[~2015-05-06 14:49 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 14:53 [Qemu-devel] [PATCH v6 00/17] s390 cpu model implementation Michael Mueller
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 01/17] Introduce stub routine cpu_desc_avail Michael Mueller
2015-05-05 13:55 ` Eduardo Habkost
2015-05-05 16:12 ` Michael Mueller
2015-05-05 17:41 ` Eduardo Habkost
2015-05-06 9:17 ` Michael Mueller
2015-05-06 11:23 ` Eduardo Habkost
2015-05-06 16:23 ` Michael Mueller
2015-05-06 17:06 ` Eduardo Habkost
2015-05-07 7:35 ` Michael Mueller
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 02/17] Add accelerator id and model name to CPUState Michael Mueller
2015-05-05 13:26 ` Eduardo Habkost
2015-05-05 14:36 ` Eric Blake
2015-05-05 14:46 ` Eduardo Habkost
2015-05-06 9:28 ` Michael Mueller
2015-05-06 9:59 ` Michael Mueller
2015-05-06 11:41 ` Eduardo Habkost
2015-05-07 7:55 ` Michael Mueller
2015-05-07 15:04 ` Eduardo Habkost
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 03/17] Extend QMP command query-cpus to return accelerator id and model name Michael Mueller
2015-05-05 13:11 ` Eduardo Habkost
2015-05-06 9:49 ` Michael Mueller
2015-05-06 11:33 ` Eduardo Habkost
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 04/17] Extend HMP command info cpus to display " Michael Mueller
2015-05-05 13:14 ` Eduardo Habkost
2015-05-06 7:32 ` Michael Mueller
2015-05-06 10:38 ` Eduardo Habkost
2015-05-06 12:59 ` Luiz Capitulino
2015-05-06 13:33 ` Eduardo Habkost
2015-05-06 13:44 ` Michael Mueller
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 05/17] Add optional parameters to QMP command query-cpu-definitions Michael Mueller
2015-05-06 12:42 ` Eduardo Habkost
2015-05-07 7:37 ` Michael Mueller
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 06/17] target-s390x: Introduce S390 CPU facilities Michael Mueller
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 07/17] target-s390x: Generate facility defines per S390 CPU model Michael Mueller
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 08/17] target-s390x: Introduce S390 CPU models Michael Mueller
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 09/17] target-s390x: Define S390 CPU model specific facility lists Michael Mueller
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 10/17] target-s390x: Add S390 CPU model alias definition routines Michael Mueller
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 11/17] target-s390x: Add KVM VM attribute interface for S390 CPU models Michael Mueller
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 12/17] target-s390x: Add S390 CPU class initialization routines Michael Mueller
2015-05-05 14:34 ` Eduardo Habkost
2015-05-06 8:02 ` Michael Mueller
2015-05-06 12:20 ` Eduardo Habkost
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 13/17] target-s390x: Prepare accelerator during S390 CPU object realization Michael Mueller
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 14/17] target-s390x: Initialize S390 CPU model name in CPUState Michael Mueller
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 15/17] target-s390x: Extend arch specific QMP command query-cpu-definitions Michael Mueller
2015-05-05 18:40 ` Eduardo Habkost
2015-05-06 15:31 ` Michael Mueller
2015-05-06 16:00 ` Eduardo Habkost
2015-05-06 16:27 ` Michael Mueller
2015-05-06 12:37 ` Eduardo Habkost
2015-05-06 14:48 ` Michael Mueller [this message]
2015-05-11 16:59 ` Eduardo Habkost
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 16/17] target-s390x: Introduce S390 CPU facility test routine Michael Mueller
2015-04-27 14:53 ` [Qemu-devel] [PATCH v6 17/17] target-s390x: Enable S390 CPU model usage Michael Mueller
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=20150506164857.5df6a1ae@bee \
--to=mimu@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=daniel.hansel@linux.vnet.ibm.com \
--cc=ehabkost@redhat.com \
--cc=gleb@kernel.org \
--cc=jjherne@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).