qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH 5/5] target-i386: implement machine->hot_add_cpu hook
Date: Thu, 2 May 2013 09:18:06 +0200	[thread overview]
Message-ID: <20130502091806.39e109ee@thinkpad> (raw)
In-Reply-To: <51816DEB.1070502@suse.de>

On Wed, 01 May 2013 21:32:59 +0200
Andreas Färber <afaerber@suse.de> wrote:

> Am 30.04.2013 18:00, schrieb Igor Mammedov:
> > Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> > ---
> > v3:
> >   * use local static variable for saving cpu_model
> > 
> > v2:
> >   * override .hot_add_cpu statically starting with 1.5 machine
> 
> Thanks, applied to qom-cpu:
> https://github.com/afaerber/qemu-cpu/commits/qom-cpu
> 
> I verified it's working as expected in Windows 2012 Datacenter, but
> neither in openSUSE 12.3 nor in Fedora 18 Live DVD did I see any change
> in /proc/cpuinfo or GNOME System Monitor.
Right after hot-add a new CPU entry should appear in /sys/devices/system/cpu
then kernel doesn't online hot-added CPUs automatically, one needs online
a new CPU manually, for example issuing following command:
 echo 1 > /sys/devices/system/cpu/cpuXX/online




> Andreas
> 
> -- 
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg


-- 
Regards,
  Igor

  reply	other threads:[~2013-05-02  7:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30 13:41 [Qemu-devel] [PATCH 0/5 v9 for-1.5] target-i386: CPU hot-add with cpu-add QMP command Igor Mammedov
2013-04-30 13:41 ` [Qemu-devel] [PATCH 1/5] add hot_add_cpu hook to QEMUMachine Igor Mammedov
2013-04-30 14:19   ` Eduardo Habkost
2013-04-30 15:48   ` Andreas Färber
2013-04-30 13:41 ` [Qemu-devel] [PATCH 2/5] QMP: add cpu-add command Igor Mammedov
2013-04-30 14:19   ` Eduardo Habkost
2013-04-30 15:58   ` Andreas Färber
2013-04-30 13:41 ` [Qemu-devel] [PATCH 3/5] add cpu_model to QEMUMachine Igor Mammedov
2013-04-30 14:30   ` Eduardo Habkost
2013-04-30 14:48     ` [Qemu-devel] [PATCH] target-arm: cpu: set default cpu_model via QEMUMachine.cpu_model Igor Mammedov
2013-04-30 14:55       ` Peter Maydell
2013-04-30 15:01         ` Igor Mammedov
2013-04-30 15:06         ` Eduardo Habkost
2013-04-30 14:54     ` [Qemu-devel] [PATCH 3/5] add cpu_model to QEMUMachine Peter Maydell
2013-04-30 15:14       ` Igor Mammedov
2013-04-30 15:32         ` Peter Maydell
2013-04-30 13:41 ` [Qemu-devel] [PATCH 4/5] target-i386: get default cpu_model from QEMUMachine Igor Mammedov
2013-04-30 14:47   ` Eduardo Habkost
2013-04-30 13:41 ` [Qemu-devel] [PATCH 5/5] target-i386: implement machine->hot_add_cpu hook Igor Mammedov
2013-04-30 16:00   ` Igor Mammedov
2013-04-30 16:31     ` Eduardo Habkost
2013-05-01 19:32     ` Andreas Färber
2013-05-02  7:18       ` Igor Mammedov [this message]
2013-05-02 11:46         ` Andreas Färber
2013-04-30 16:32   ` [Qemu-devel] [PATCH 5/5 v10] " 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=20130502091806.39e109ee@thinkpad \
    --to=imammedo@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=ehabkost@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).