On Mon, Jun 15, 2015 at 11:10:31AM +0200, Igor Mammedov wrote: > On Thu, 11 Jun 2015 10:39:05 +0300 > Fahri Cihan Demirci <cih...@skyatlas.com> wrote: > > > On Tue, Jun 09, 2015 at 05:44:15PM +0200, Eduardo Otubo wrote: > > > Hello all, > > > > > > I'm a little confused by all the email traffic I've seen on this list > > > lately so I guess asking doesn't hurt: How's the current status > > > regarding CPU hot unplug for x86_64? If there's any task left hanging > > > for testing or debugging -- or even implementing something that is not > > > done yet -- for some reason please let me know how to help. We have a > > > lot of interest on this feature for our projects. > > > > > > Regards, > > > > > > -- > > > Eduardo Otubo > > > ProfitBricks GmbH > > > > Hello, > > > > We are (yet another startup) are also interested in this feature and > > likewise are willing to contribute. As Eduardo mentioned, it is not quite > > easy to assess the progress or identify the people who require or desire > > any help. Therefore, any kind of feedback would be most welcome. Thank you. > > Here is a cpu-remove related series that need reviewing/testing: > http://lists.nongnu.org/archive/html/qemu-devel/2015-06/msg02055.html > > somewhat related, but unplug could live without it: > http://lists.nongnu.org/archive/html/qemu-devel/2015-06/msg02143.html > > I general we don't want to add cpu_del monitor command to compliment cpu_add > one, > and move to device_add, device_del commands instead. > So you could look at making device_add work for x86 CPU and on top of it > add device_del support.
Hello Igor, That was my impression as well. However, since there is some groundwork for it and people are sending patches, would you (as a maintainer) be willing to merge a CPU only hot unplug feature if it reaches an acceptable state? Thank you for your input. > > > > > Best regards, > > > > Fahri Cihan Demirci > > >