qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] i386: Allow cpuid bit override
Date: Thu, 30 Mar 2017 16:23:34 +0200	[thread overview]
Message-ID: <67d1d8fe-0f0d-3c68-bcf7-6889727b8927@suse.de> (raw)
In-Reply-To: <20170330142240.GH3709@thinpad.lan.raisama.net>

On 03/30/2017 04:22 PM, Eduardo Habkost wrote:
> On Tue, Mar 28, 2017 at 02:35:57PM +0200, Alexander Graf wrote:
>> On 03/28/2017 02:31 PM, Eduardo Habkost wrote:
>>> On Tue, Mar 28, 2017 at 01:26:04PM +0200, Alexander Graf wrote:
> [...]
>>>> Putting it into a special enum sounds much more fragile than the current
>>>> solution to me. We need to bool fallback either way, so I fail to see any
>>>> benefit from having the enum.
>>> I don't see why the enum would be more fragile. With the QAPI
>>> enum, we:
>>> * Have a meaningful value for the QOM property 'type' field,
>>>     and have some hope to make type information for QOM properties
>>>     really useful one day;
>>> * Have the possible values for the property well-documented in
>>>     the QAPI schema;
>>> * Have the string<->enum translation code automatically generated
>>>     for us;
>>> * Can easily add other values later (I have been planning to
>>>     support "feat=host" so "-cpu host/max" aren't special cases in
>>>     the code.
>>>
>> Ok, can you create the boilerplate for an OnOff enum type for me and I'll
>> plug =force into that? All that visitor stuff scares me :).
> I can do it, if you don't mind waiting for a few days. :)


As long as we still manage to hit 2.9 with this I'm all happy :).


Alex

  reply	other threads:[~2017-03-30 14:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 22:19 [Qemu-devel] [PATCH] i386: Allow cpuid bit override Alexander Graf
2017-03-28  0:41 ` Eduardo Habkost
2017-03-28 11:26   ` Alexander Graf
2017-03-28 12:31     ` Eduardo Habkost
2017-03-28 12:35       ` Alexander Graf
2017-03-30 14:22         ` Eduardo Habkost
2017-03-30 14:23           ` Alexander Graf [this message]
2017-03-30 14:25             ` Eduardo Habkost
2017-03-30 14:27               ` Alexander Graf
2017-04-13 17:20       ` Eduardo Habkost
2017-03-28 12:41     ` Paolo Bonzini
2017-03-28 16:01       ` Eduardo Habkost
2017-03-28 16:35         ` Paolo Bonzini

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=67d1d8fe-0f0d-3c68-bcf7-6889727b8927@suse.de \
    --to=agraf@suse.de \
    --cc=ehabkost@redhat.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).