qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Denemark <jdenemar@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	qemu-devel@nongnu.org, dahi@linux.vnet.ibm.com,
	Igor Mammedov <imammedo@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Richard Henderson <rth@twiddle.net>,
	libvir-list@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 01/11] tests: Add test case for x86 feature parsing compatibility
Date: Fri, 30 Sep 2016 10:08:54 +0200	[thread overview]
Message-ID: <20160930080854.GM952385@orkuz.home> (raw)
In-Reply-To: <690f3768-f7f4-95e1-9d64-b9780090ff41@redhat.com>

On Fri, Sep 30, 2016 at 09:55:33 +0200, Paolo Bonzini wrote:
> 
> 
> On 29/09/2016 23:14, Eduardo Habkost wrote:
> > +     * "-foo" overrides "+foo"
> > +     * "[+-]foo" overrides "foo=..."
> 
> Is this something that people are actually using?  Can we detect it and
> deprecate it in 2.8, and drop it in 2.9?

Libvirt uses -cpu Model,+foo,-bar style, but we do not mix mix -foo and
+foo, or even [+-]foo and foo= if this is what you asked.

Jirka

  reply	other threads:[~2016-09-30  8:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 21:14 [Qemu-devel] [PATCH v4 00/11] Add runnability info to query-cpu-definitions Eduardo Habkost
2016-09-29 21:14 ` [Qemu-devel] [PATCH v4 01/11] tests: Add test case for x86 feature parsing compatibility Eduardo Habkost
2016-09-29 21:31   ` Jonathan Neuschäfer
2016-09-30  7:55   ` Paolo Bonzini
2016-09-30  8:08     ` Jiri Denemark [this message]
2016-09-30 18:33     ` Eduardo Habkost
2016-09-30 21:07       ` Paolo Bonzini
2016-09-29 21:14 ` [Qemu-devel] [PATCH v4 02/11] target-i386: List CPU models using subclass list Eduardo Habkost
2016-09-29 21:14 ` [Qemu-devel] [PATCH v4 03/11] target-i386: Disable VME by default with TCG Eduardo Habkost
2016-09-29 21:14 ` [Qemu-devel] [PATCH v4 04/11] target-i386: Make plus_features/minus_features QOM-based Eduardo Habkost
2016-09-29 21:14 ` [Qemu-devel] [PATCH v4 05/11] target-i386: Remove underscores from property names Eduardo Habkost
2016-09-30  7:29   ` Jiri Denemark
2016-09-30 13:42     ` Eduardo Habkost
2016-09-29 21:14 ` [Qemu-devel] [PATCH v4 06/11] target-i386: Register properties for feature aliases manually Eduardo Habkost
2016-09-29 21:14 ` [Qemu-devel] [PATCH v4 07/11] target-i386: xsave: Add FP and SSE bits to x86_ext_save_areas Eduardo Habkost
2016-09-29 21:14 ` [Qemu-devel] [PATCH v4 08/11] target-i386: Move warning code outside x86_cpu_filter_features() Eduardo Habkost
2016-09-29 21:14 ` [Qemu-devel] [PATCH v4 09/11] target-i386: x86_cpu_load_features() function Eduardo Habkost
2016-09-30  8:00   ` Paolo Bonzini
2016-09-29 21:14 ` [Qemu-devel] [PATCH v4 10/11] qmp: Add runnability information to query-cpu-definitions Eduardo Habkost
2016-09-29 21:14 ` [Qemu-devel] [PATCH v4 11/11] target-i386: Return runnability information on query-cpu-definitions Eduardo Habkost
2016-09-30  8:02   ` Paolo Bonzini
2016-09-30 13:40     ` 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=20160930080854.GM952385@orkuz.home \
    --to=jdenemar@redhat.com \
    --cc=armbru@redhat.com \
    --cc=dahi@linux.vnet.ibm.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=libvir-list@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).