All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: "Collin L. Walling" <walling@linux.vnet.ibm.com>,
	jjherne@linux.vnet.ibm.com, borntraeger@de.ibm.com,
	libvir-list@redhat.com, Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v1] qemu: command: rework cpu feature argument support
Date: Tue, 15 Nov 2016 11:44:00 -0200	[thread overview]
Message-ID: <20161115134400.GH5057@thinpad.lan.raisama.net> (raw)
In-Reply-To: <20161115074212.GB4015667@orkuz.home>

CCing qemu-devel.

CCing Markus, in case he has any insights about the interface
introspection.

On Tue, Nov 15, 2016 at 08:42:12AM +0100, Jiri Denemark wrote:
> On Mon, Nov 14, 2016 at 18:02:29 -0200, Eduardo Habkost wrote:
> > On Mon, Nov 14, 2016 at 02:26:03PM -0500, Collin L. Walling wrote:
> > > cpu features are passed to the qemu command with feature=on/off
> > > instead of +/-feature.
> > > 
> > > Signed-off-by: Collin L. Walling <walling@linux.vnet.ibm.com>
> > 
> > If I'm not mistaken, the "feature=on|off" syntax was added on
> > QEMU 2.0.0. Does current libvirt support older QEMU versions?
> 
> Of course it does. I'd love to switch to feature=on|off, but how can we
> check if QEMU supports it? We can't really start using this syntax
> without it.

Actually, I was wrong, this was added in v2.4.0. "feat=on|off"
needs two things to work (in x86):

* Translation of all "foo=bar" options to QOM property setting.
  This was added in v2.0.0-rc0~162^2
* The actual QOM properties for feature names to be present. They
  were added in v2.4.0-rc0~101^2~1

So you can be sure "feat=on" is supported by checking if the
feature flags are present in device-list-properties output for
the CPU model. But device-list-properties is also messy[1].

Maybe we can use the availability of query-cpu-model-expansion to
check if we can safely use the new "feat=on|off" system? It's
easier than taking all the variables above into account.

---

[1] * device-list-properties support for x86 CPU QOM classes
      will be in QEMU 2.8.
    * device-list-properties on x86 CPU QOM classes returns
      an error on QEMU 2.5-2.7.
    * device-list-properties on x86 CPU classes may crash QEMU in
      QEMU older than 2.5 (see commit 4c315c27).
  But:
    * query-cpu-definitions will probably return the CPU QOM
      typename in QEMU 2.9+ only.


-- 
Eduardo

       reply	other threads:[~2016-11-15 13:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1479151563-13473-1-git-send-email-walling@linux.vnet.ibm.com>
     [not found] ` <1479151563-13473-2-git-send-email-walling@linux.vnet.ibm.com>
     [not found]   ` <20161114200229.GG5057@thinpad.lan.raisama.net>
     [not found]     ` <20161115074212.GB4015667@orkuz.home>
2016-11-15 13:44       ` Eduardo Habkost [this message]
2016-11-16 13:15         ` [Qemu-devel] [libvirt] [PATCH v1] qemu: command: rework cpu feature argument support Jiri Denemark
2016-11-16 14:05           ` Eduardo Habkost
2016-11-16 15:44             ` Collin L. Walling
2016-11-17 15:04         ` [Qemu-devel] " Markus Armbruster
2016-11-17 16:36           ` Eduardo Habkost

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=20161115134400.GH5057@thinpad.lan.raisama.net \
    --to=ehabkost@redhat.com \
    --cc=armbru@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=jjherne@linux.vnet.ibm.com \
    --cc=libvir-list@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=walling@linux.vnet.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.