From: Igor Mammedov <imammedo@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
"Greg Bellows" <greg.bellows@linaro.org>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Christoffer Dall" <christoffer.dall@linaro.org>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH 1/5] target-arm: Add ARM CPU feature parsing
Date: Tue, 20 Jan 2015 16:59:41 +0100 [thread overview]
Message-ID: <20150120165941.39c9a0f5@nial.brq.redhat.com> (raw)
In-Reply-To: <CAFEAcA-hHXkQAYwFC_4FRXheHbV0djCQGS6wJBiOTv1vVVONDA@mail.gmail.com>
On Tue, 20 Jan 2015 15:34:23 +0000
Peter Maydell <peter.maydell@linaro.org> wrote:
> On 20 January 2015 at 15:22, Igor Mammedov <imammedo@redhat.com> wrote:
> > Please do not use legacy +-feature format and support only foo=val format.
> > Other targets have it only for to being able support legacy setups
> > which use +- format.
>
> I thought this was the standard format for CPU features. Do you
> have an example of a CPU feature being set using foo=val format?
Currently on x86 we can use either legacy +foo1,-foo2,foo3 and
in addition to it we ca use canonized format for generic properties
like, foo1=on,foo2=off,foo3=on
We try to move out of legacy format, so that it would be possible
to reuse generic property parsing infrastructure like with any
device object. That would allow to use -device/device_add for CPUs.
>
> -- PMM
>
next prev parent reply other threads:[~2015-01-20 15:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 22:30 [Qemu-devel] [PATCH 0/5] target-arm: ARM64: Adding EL1 AARCH32 guest support Greg Bellows
2015-01-19 22:30 ` [Qemu-devel] [PATCH 1/5] target-arm: Add ARM CPU feature parsing Greg Bellows
2015-01-20 14:19 ` Alex Bennée
2015-01-20 14:49 ` Greg Bellows
2015-01-21 10:57 ` Alex Bennée
2015-01-20 15:22 ` Igor Mammedov
2015-01-20 15:34 ` Peter Maydell
2015-01-20 15:59 ` Igor Mammedov [this message]
2015-01-20 16:08 ` Peter Maydell
2015-01-20 16:25 ` Igor Mammedov
2015-01-20 22:45 ` Greg Bellows
2015-01-21 11:33 ` Igor Mammedov
2015-01-20 15:34 ` Greg Bellows
2015-01-20 16:02 ` Eduardo Habkost
2015-01-20 16:05 ` Igor Mammedov
2015-01-19 22:30 ` [Qemu-devel] [PATCH 2/5] target-arm: Add feature parsing to virt Greg Bellows
2015-01-20 16:58 ` Alex Bennée
2015-01-19 22:30 ` [Qemu-devel] [PATCH 3/5] target-arm: Add 32/64-bit register sync Greg Bellows
2015-01-19 22:30 ` [Qemu-devel] [PATCH 4/5] target-arm: Add AArch32 guest support to KVM64 Greg Bellows
2015-01-20 16:57 ` Alex Bennée
2015-01-20 20:03 ` Greg Bellows
2015-01-21 10:54 ` Alex Bennée
2015-01-21 10:56 ` Peter Maydell
2015-01-19 22:30 ` [Qemu-devel] [PATCH 5/5] target-arm: Adjust kernel load address for Image Greg Bellows
2015-01-20 10:21 ` [Qemu-devel] [PATCH 0/5] target-arm: ARM64: Adding EL1 AARCH32 guest support Sergey Fedorov
2015-01-20 10:26 ` Peter Maydell
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=20150120165941.39c9a0f5@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=christoffer.dall@linaro.org \
--cc=ehabkost@redhat.com \
--cc=greg.bellows@linaro.org \
--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).