From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33986) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z4l0M-0001FG-Lu for qemu-devel@nongnu.org; Tue, 16 Jun 2015 03:09:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z4l0J-0008Ok-FO for qemu-devel@nongnu.org; Tue, 16 Jun 2015 03:09:54 -0400 Received: from fmvm01.lax10.vpls.net ([209.11.253.20]:51988) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z4l0J-0008OR-6J for qemu-devel@nongnu.org; Tue, 16 Jun 2015 03:09:51 -0400 Date: Tue, 16 Jun 2015 10:09:30 +0300 From: Fahri Cihan Demirci Message-ID: <20150616070929.GA1229@francium.user.ytu.skyatlas.com> References: <20150609154414.GA13043@vader> <20150611073904.GB1169@francium.user.ytu.skyatlas.com> <20150615111031.0559d47f@nial.brq.redhat.com> <20150615123423.GB4037@francium.user.ytu.skyatlas.com> <20150615181423.3400ae60@nial.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150615181423.3400ae60@nial.brq.redhat.com> Subject: Re: [Qemu-devel] CPU hot unplug support for x86_64 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Igor Mammedov Cc: Qemu-devel , Eduardo Otubo On Mon, Jun 15, 2015 at 06:14:23PM +0200, Igor Mammedov wrote: > On Mon, 15 Jun 2015 15:34:24 +0300 > Fahri Cihan Demirci wrote: > > > 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 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? > I'm not maintainer, but I'll help any way I can to make a progress towards merging. Even though you are not the CPU maintainer I assumed you'd have better grasp of QEMU policy since you seem to be the ICC BUS maintainer. In any case, your feedback is much appreciated. Thank you. > > > > > Thank you for your input. > > > > > > > > > > > > > Best regards, > > > > > > > > Fahri Cihan Demirci > > > > > > > >