From: Andrea Bolognani <abologna@redhat.com>
To: Andrew Jones <drjones@redhat.com>, Igor Mammedov <imammedo@redhat.com>
Cc: peter.maydell@linaro.org,
"Daniel P. Berrangé" <berrange@redhat.com>,
ehabkost@redhat.com, "Markus Armbruster" <armbru@redhat.com>,
qemu-devel@nongnu.org, dgilbert@redhat.com, Dave.Martin@arm.com
Subject: Re: [Qemu-devel] How do we do user input bitmap properties?
Date: Thu, 23 May 2019 10:35:24 +0200 [thread overview]
Message-ID: <2186eb85f8541b0c9cc69cacae9321ace8addaa6.camel@redhat.com> (raw)
In-Reply-To: <20190515115413.cqvzjkky7xubnsuo@kamzik.brq.redhat.com>
On Wed, 2019-05-15 at 13:54 +0200, Andrew Jones wrote:
> On Wed, May 15, 2019 at 12:52:29PM +0200, Igor Mammedov wrote:
> > since using magic numbers is not very descriptive
> > (but if there is some spec where they come from that we could point users to
> > it might be acceptable too, but I'd reserve number approach for values only).
>
> The numbers aren't magic, they're part of the name. '1' in the above
> 'sve1' means one quadword. It would probably have been better to use bits
> instead in the example, i.e.
>
> -cpu host,sve128=on,sve256=on,sve384=off,sve512=on
>
> where it's now clear that "sve512" has an analogy with x86's "avx512".
>
[...]
>
> So I set off to convince Igor of the wide word idea (he sits next to me,
> so I didn't have go far), but he has convinced me of the above property
> idea. He used the magic phrase: "less code would be needed". If we use
> the properties like above then we get introspection for free (cpu property
> listing which libvirt already knows how to do) - so no QMP query needed.
> The cost is adding several properties (16 to handle the current 2048-bit
> limit), but I guess that's cheap enough. The command line is verbose, but
> also much easier for a human to construct and read. I'm pretty sold on
> this path, but adding Andrea and Eduardo for their input as well.
Sorry for taking a while to respond. Anyway, the above looks good to
me as a general direction, but note that you'll have to implement at
the very least the query-cpu-model-expansion QMP command for the
introspection to work.
query-cpu-model-baseline and query-cpu-model-comparison are two more
QMP command which, while perhaps not immediately applicabile, we will
want to implement at some point; more in general, what s390x is doing
with respect to CPU models is a good blueprint, according to the
libvirt developer who's the most involved with that specific area of
the project.
--
Andrea Bolognani / Red Hat / Virtualization
next prev parent reply other threads:[~2019-05-23 8:41 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 9:28 [Qemu-devel] How do we do user input bitmap properties? Andrew Jones
2019-04-18 9:28 ` Andrew Jones
2019-04-18 9:46 ` Andrew Jones
2019-04-18 9:46 ` Andrew Jones
2019-04-18 10:52 ` Dave Martin
2019-04-18 10:52 ` Dave Martin
2019-04-18 11:28 ` Andrew Jones
2019-04-18 11:28 ` Andrew Jones
2019-04-18 14:03 ` Dave Martin
2019-04-18 14:03 ` Dave Martin
2019-04-18 14:43 ` Andrew Jones
2019-04-18 14:43 ` Andrew Jones
2019-04-18 14:46 ` Dave Martin
2019-04-18 14:46 ` Dave Martin
2019-04-18 14:57 ` Dr. David Alan Gilbert
2019-04-18 14:57 ` Dr. David Alan Gilbert
2019-04-18 11:26 ` Daniel P. Berrangé
2019-04-18 11:26 ` Daniel P. Berrangé
2019-04-18 15:09 ` Andrew Jones
2019-04-18 15:09 ` Andrew Jones
2019-04-18 17:48 ` Markus Armbruster
2019-04-18 17:48 ` Markus Armbruster
2019-05-13 18:42 ` Andrew Jones
2019-05-14 4:54 ` Markus Armbruster
2019-05-14 9:02 ` Andrew Jones
2019-05-14 13:32 ` Markus Armbruster
2019-05-15 8:15 ` Andrew Jones
2019-05-15 10:53 ` Dave Martin
2019-05-15 10:59 ` Dr. David Alan Gilbert
2019-05-14 14:48 ` Igor Mammedov
2019-05-15 8:18 ` Andrew Jones
2019-05-15 10:52 ` Igor Mammedov
2019-05-15 11:54 ` Andrew Jones
2019-05-23 8:35 ` Andrea Bolognani [this message]
2019-05-24 18:24 ` Eduardo Habkost
2019-05-27 16:29 ` Andrea Bolognani
2019-05-27 18:59 ` Eduardo Habkost
2019-05-15 11:00 ` Dave Martin
2019-05-15 11:09 ` Dr. David Alan Gilbert
2019-05-15 12:51 ` Dave Martin
2019-05-15 11:42 ` Andrew Jones
2019-05-15 12:50 ` Dave Martin
2019-05-14 15:28 ` Dave Martin
2019-04-19 0:07 ` Laszlo Ersek
2019-04-19 0:07 ` Laszlo Ersek
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=2186eb85f8541b0c9cc69cacae9321ace8addaa6.camel@redhat.com \
--to=abologna@redhat.com \
--cc=Dave.Martin@arm.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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 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).