qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 11/12 v2] qmp: add cpu-set qmp command
Date: Tue, 26 Mar 2013 08:38:32 -0600	[thread overview]
Message-ID: <5151B2E8.4080904@redhat.com> (raw)
In-Reply-To: <20130326144301.79fed257@nial.usersys.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 730 bytes --]

On 03/26/2013 07:43 AM, Igor Mammedov wrote:

>>> The alternative is to have cpu-set-online and later cpu-set-offline. Quite
>>> verbose, but doesn't have issues.
> It looks like better as way to go. Later on we could keep them for
> compatibility sake and map it to device_add/device_del commands when they are
> ready.
> 

> Considering all said above, would it be acceptable to replace cpu-set with
> "cpu_add id=xx" command?

cpu_add id=xx from HMP, cpu-add from QMP is fine for getting things
started; it still leaves room for a future 'cpu-set' batching command if
batching turns out to be useful.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

  parent reply	other threads:[~2013-03-26 14:38 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 14:28 [Qemu-devel] [RFC 00/12] target-i386: CPU hot-add with cpu_set QMP command Igor Mammedov
2013-03-21 14:28 ` [Qemu-devel] [PATCH 01/12] target-i386: consolidate error propagation in x86_cpu_realizefn() Igor Mammedov
2013-03-27 10:21   ` Paolo Bonzini
2013-04-01 20:00   ` Eduardo Habkost
2013-03-21 14:28 ` [Qemu-devel] [PATCH 02/12] target-i386: split APIC creation from initialization " Igor Mammedov
2013-04-04  8:59   ` Andreas Färber
2013-04-04  9:56     ` Igor Mammedov
2013-03-21 14:28 ` [Qemu-devel] [PATCH 03/12] target-i386: split out CPU creation and features parsing into cpu_x86_create() Igor Mammedov
2013-03-21 14:28 ` [Qemu-devel] [PATCH 04/12] target-i386: introduce apic-id property Igor Mammedov
2013-03-21 14:28 ` [Qemu-devel] [PATCH 05/12] target-i386: push hot-plugged VCPU state to KVM and unstop it Igor Mammedov
2013-03-27 11:01   ` Paolo Bonzini
2013-03-27 12:12     ` Igor Mammedov
2013-03-27 12:17       ` Andreas Färber
2013-03-27 13:27         ` Igor Mammedov
2013-03-27 14:30           ` Andreas Färber
2013-03-27 15:16             ` Igor Mammedov
2013-03-27 15:20               ` Paolo Bonzini
2013-03-27 19:46                 ` Igor Mammedov
2013-03-27 19:51                 ` [Qemu-devel] [PATCH 05/14] cpu: Pass CPUState to *cpu_synchronize_post*() Igor Mammedov
2013-03-27 19:51                 ` [Qemu-devel] [PATCH 06/14] cpu: call cpu_synchronize_post_init() from CPUClass.realize() if hotplugged Igor Mammedov
2013-03-27 19:51                 ` [Qemu-devel] [PATCH 07/14] cpu: introduce CPUClass.resume() method Igor Mammedov
2013-03-21 14:28 ` [Qemu-devel] [PATCH 06/12] target-i386: replace FROM_SYSBUS() with QOM type cast Igor Mammedov
2013-03-27 10:22   ` Paolo Bonzini
2013-04-04  9:03   ` Andreas Färber
2013-04-04  9:59     ` Igor Mammedov
2013-04-04 10:05       ` Andreas Färber
2013-04-04 10:22         ` Igor Mammedov
2013-03-21 14:28 ` [Qemu-devel] [PATCH 07/12] target-i386: Add ICC_BUS and attach apic, kvmvapic and cpu to it Igor Mammedov
2013-03-27 10:57   ` Paolo Bonzini
2013-03-28 10:55   ` Igor Mammedov
2013-03-29  7:22     ` li guang
2013-03-29  8:12       ` Igor Mammedov
2013-04-04 11:10     ` Andreas Färber
2013-04-04 12:52       ` Igor Mammedov
2013-03-21 14:28 ` [Qemu-devel] [PATCH 08/12] introduce CPU hot-plug notifier Igor Mammedov
2013-03-27 11:06   ` Paolo Bonzini
2013-03-27 15:24     ` Igor Mammedov
2013-03-27 15:36       ` Paolo Bonzini
2013-03-21 14:28 ` [Qemu-devel] [PATCH 09/12] rtc: update rtc_cmos on CPU hot-plug Igor Mammedov
2013-03-21 14:28 ` [Qemu-devel] [PATCH 10/12] acpi_piix4: add infrastructure to send CPU hot-plug GPE to guest Igor Mammedov
2013-03-27 10:47   ` Paolo Bonzini
2013-03-21 14:28 ` [Qemu-devel] [PATCH 11/12] qmp: add cpu_set qmp command Igor Mammedov
2013-03-22  2:44   ` Eric Blake
2013-03-25 15:35     ` [Qemu-devel] [PATCH 11/12 v2] qmp: add cpu-set " Igor Mammedov
2013-03-25 20:09       ` Luiz Capitulino
2013-03-25 20:22         ` Eric Blake
2013-03-26 13:43           ` Igor Mammedov
2013-03-26 14:02             ` Luiz Capitulino
2013-03-26 14:38             ` Eric Blake [this message]
2013-03-27 10:36   ` [Qemu-devel] [PATCH 11/12] qmp: add cpu_set " Paolo Bonzini
2013-03-21 14:28 ` [Qemu-devel] [PATCH 12/12] target-i386: implement CPU hot-add Igor Mammedov
2013-03-22  2:46   ` Eric Blake
2013-03-25 15:31     ` Igor Mammedov
2013-03-27 11:19   ` Paolo Bonzini
2013-04-03 17:58     ` Igor Mammedov
2013-04-03 18:10       ` Eduardo Habkost
2013-04-03 18:59         ` Igor Mammedov
2013-04-03 19:27           ` Eduardo Habkost
2013-04-03 20:09             ` Igor Mammedov
2013-04-03 20:57               ` Eduardo Habkost
2013-04-03 18:22       ` Andreas Färber
2013-04-03 19:01         ` Igor Mammedov
2013-03-21 14:44 ` [Qemu-devel] [RFC 00/12] target-i386: CPU hot-add with cpu_set QMP command Eric Blake
2013-03-21 15:38   ` Igor Mammedov

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=5151B2E8.4080904@redhat.com \
    --to=eblake@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=lcapitulino@redhat.com \
    --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).