From: David Hildenbrand <dahi@linux.vnet.ibm.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
qemu-devel@nongnu.org, peter.maydell@linaro.org,
mark.cave-ayland@ilande.co.uk, blauwirbel@gmail.com,
qemu-arm@nongnu.org, pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH RFC 0/8] cpus: make "-cpu cpux, features" global properties
Date: Mon, 6 Jun 2016 11:59:19 +0200 [thread overview]
Message-ID: <201606060959.u569wtau013539@mx0a-001b2d01.pphosted.com> (raw)
In-Reply-To: <20160603195457.GZ19055@thinpad.lan.raisama.net>
> I assume Igor explained it, already, and his suggestion sounds OK
> to you. But I will answer your questions to confirm that this is
> really the case:
Yes, this all sounds good to me, thanks for the additional explanation!
[...]
>
> >
> > d) has to work for us. Otherwise we will have to fallback to manual
> > property parsing.
>
> It will be affected by the globals, but I assume management code
> is not going to use add extra -cpu arguments when probing for CPU
> model information, right?
Yes, that's also what I figured out, this should not be a problem.
>
> Users will need to be aware that -cpu is equivalent to -global,
> and will affect CPU information returned by query-cpu-definitions
> (or similar commands).
>
> >
> > >
> > > If all you need is to parse properties, why can't you reuse the
> > > existing QOM/Device mechanisms to handle properties (the one used
> > > by -device and device_add), instead of the -cpu code?
> >
> > We can, if my given example works. And the global properties
> > don't interfere with cpus.
>
> They do, but only the model specified in -cpu.
>
> >
> > >
> > > We need to use less of the infrastructure that exists for the
> > > legacy -cpu option (and use more of the generic QOM/Device
> > > mechanisms), not more of it.
> >
> > It is better to have one way of creating cpus that two.
>
> Unfortunately we already have two ways of creating CPUs: -cpu and
> device_add. We are trying to translate -cpu to something
> equivalent to generic mechanisms (-device and -global), so we
> have only one underlying mechanism.
Yes, understood. Sounds sane to me!
[...]
> I understand that this may be confusing, but that's because -smp
> and -cpu don't fit the QEMU device/object models. We are moving
> towards allowing CPU topologies to be created using only -device.
>
> To do that, we are gradually translating -cpu to the generic
> mechanisms used by -device/-global, so command-line options could
> be easily converted to use the new mechanisms in the future.
>
> Does that make sense?
>
Absolutely!
David
prev parent reply other threads:[~2016-06-06 9:59 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 16:37 [Qemu-devel] [PATCH RFC 0/8] cpus: make "-cpu cpux, features" global properties Igor Mammedov
2016-06-01 16:37 ` [Qemu-devel] [PATCH RFC 1/8] target-i386: cpu: move features logic that requires CPUState to realize time Igor Mammedov
2016-06-01 17:43 ` Eduardo Habkost
2016-06-02 9:59 ` Igor Mammedov
2016-06-02 14:38 ` Eduardo Habkost
2016-06-02 16:56 ` Igor Mammedov
2016-06-02 17:34 ` Eduardo Habkost
2016-06-02 18:23 ` Igor Mammedov
2016-06-02 18:43 ` Eduardo Habkost
2016-06-03 10:13 ` Igor Mammedov
2016-06-03 19:26 ` Eduardo Habkost
2016-06-04 16:44 ` Igor Mammedov
2016-06-01 16:37 ` [Qemu-devel] [PATCH RFC 2/8] target-i386: cpu: move xcc->kvm_required check to reaize time Igor Mammedov
2016-06-01 17:46 ` Eduardo Habkost
2016-06-02 10:02 ` Igor Mammedov
2016-06-01 16:37 ` [Qemu-devel] [PATCH RFC 3/8] target-i386: cpu: use cpu_generic_init() in cpu_x86_init() Igor Mammedov
2016-06-01 18:08 ` Eduardo Habkost
2016-06-01 16:37 ` [Qemu-devel] [PATCH RFC 4/8] target-i386: cpu: consolidate calls of object_property_parse() in x86_cpu_parse_featurestr Igor Mammedov
2016-06-01 18:46 ` Eduardo Habkost
2016-06-02 12:22 ` Igor Mammedov
2016-06-02 14:42 ` Eduardo Habkost
2016-06-02 14:53 ` Eduardo Habkost
2016-06-02 15:05 ` Peter Krempa
2016-06-02 16:31 ` Igor Mammedov
2016-06-03 7:30 ` Peter Krempa
2016-06-03 9:37 ` Igor Mammedov
2016-06-03 19:36 ` Eduardo Habkost
2016-06-02 16:32 ` Igor Mammedov
2016-06-02 16:55 ` [Qemu-devel] [PATCH] target-i386: Remove xlevel & hv-spinlocks option fixups Eduardo Habkost
2016-06-02 21:07 ` [Qemu-devel] [libvirt] " Eric Blake
2016-06-01 16:37 ` [Qemu-devel] [PATCH RFC 5/8] target-sparc: cpu: use sparc_cpu_parse_features() directly Igor Mammedov
2016-06-01 16:37 ` [Qemu-devel] [PATCH RFC 6/8] cpu: use CPUClass->parse_features() as convertor to global properties Igor Mammedov
2016-06-01 18:54 ` Eduardo Habkost
2016-06-02 10:06 ` Igor Mammedov
2016-06-02 14:41 ` Eduardo Habkost
2016-06-01 16:37 ` [Qemu-devel] [PATCH RFC 7/8] arm: virt: parse cpu_model only once Igor Mammedov
2016-06-01 16:37 ` [Qemu-devel] [PATCH RFC 8/8] pc: parse cpu features " Igor Mammedov
2016-06-01 18:21 ` [Qemu-devel] [PATCH RFC 0/8] cpus: make "-cpu cpux, features" global properties Peter Maydell
2016-06-01 18:51 ` Eduardo Habkost
2016-06-02 20:44 ` David Hildenbrand
2016-06-03 12:06 ` Jiri Denemark
2016-06-03 12:14 ` David Hildenbrand
[not found] ` <201606022044.u52KaIkv017063@mx0a-001b2d01.pphosted.com>
2016-06-03 0:02 ` Eduardo Habkost
2016-06-03 6:36 ` David Hildenbrand
[not found] ` <20160603083621.6547bde4@thinkpad-w530>
2016-06-03 9:20 ` Igor Mammedov
2016-06-03 10:18 ` David Hildenbrand
2016-06-03 19:54 ` Eduardo Habkost
2016-06-06 9:59 ` David Hildenbrand [this message]
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=201606060959.u569wtau013539@mx0a-001b2d01.pphosted.com \
--to=dahi@linux.vnet.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--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).