qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: hutao@cn.fujitsu.com, qemu-devel@nongnu.org,
	tangchen@cn.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com,
	pbonzini@redhat.com, guz.fnst@cn.fujitsu.com,
	imammedo@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/5] acpi, pc: Add hotunplug request cb for pc machine.
Date: Wed, 28 Jan 2015 16:33:02 +0800	[thread overview]
Message-ID: <1422433982.4145.5.camel@G08FNSTD140041> (raw)
In-Reply-To: <20150128080223.GC16698@redhat.com>

On Wed, 2015-01-28 at 10:02 +0200, Michael S. Tsirkin wrote:
> On Wed, Jan 28, 2015 at 03:45:37PM +0800, Zhu Guihua wrote:
> > From: Tang Chen <tangchen@cn.fujitsu.com>
> > 
> > Memory and CPU hot unplug are both asynchronous procedures.
> > They both need unplug request callback to initiate unplug operation.
> > 
> > Add unplug handler to pc machine that will be used by following
> > CPU and memory unplug patches.
> > 
> > Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> > Signed-off-by: Tang Chen <tangchen@cn.fujitsu.com>
> > Signed-off-by: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
> > ---
> >  hw/i386/pc.c | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> > 
> > diff --git a/hw/i386/pc.c b/hw/i386/pc.c
> > index c7af6aa..15ee10a 100644
> > --- a/hw/i386/pc.c
> > +++ b/hw/i386/pc.c
> > @@ -1680,6 +1680,13 @@ static void pc_machine_device_plug_cb(HotplugHandler *hotplug_dev,
> >      }
> >  }
> >  
> > +static void pc_machine_device_unplug_request_cb(HotplugHandler *hotplug_dev,
> > +                                                DeviceState *dev, Error **errp)
> > +{
> > +    error_setg(errp, "acpi: device unplug request for not supported device"
> > +               " type: %s", object_get_typename(OBJECT(dev)));
> > +}
> > +
> >  static HotplugHandler *pc_get_hotpug_handler(MachineState *machine,
> >                                               DeviceState *dev)
> >  {
> 
> 
> So this is just a stub, your follow-up patches replace it with
> something more useful?
> 
> Why do we need the stub stage though?
> Why not just add whatever's going to be there eventually?
> 

This function will be used in memory hot-unplug
[RESEND PATCH v1 07/13] pc-dimm: Add memory hot unplug request support
for pc-dimm.
https://lists.nongnu.org/archive/html/qemu-devel/2015-01/msg00592.html

and cpu hot-unplug
[PATCH v2 05/11] pc: add cpu hot unplug request callback support
https://lists.nongnu.org/archive/html/qemu-devel/2015-01/msg01562.html

Regards,
Zhu

> 
> > @@ -1809,6 +1816,7 @@ static void pc_machine_class_init(ObjectClass *oc, void *data)
> >      pcmc->get_hotplug_handler = mc->get_hotplug_handler;
> >      mc->get_hotplug_handler = pc_get_hotpug_handler;
> >      hc->plug = pc_machine_device_plug_cb;
> > +    hc->unplug_request = pc_machine_device_unplug_request_cb;
> >  }
> >  
> >  static const TypeInfo pc_machine_info = {
> > -- 
> > 1.9.3

  reply	other threads:[~2015-01-28  8:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28  7:45 [Qemu-devel] [PATCH v2 0/5] Common unplug and unplug request cb for memory and CPU hot-unplug Zhu Guihua
2015-01-28  7:45 ` [Qemu-devel] [PATCH v2 1/5] acpi, pc: Add hotunplug request cb for pc machine Zhu Guihua
2015-01-28  8:02   ` Michael S. Tsirkin
2015-01-28  8:33     ` Zhu Guihua [this message]
2015-01-28  8:39       ` Michael S. Tsirkin
2015-01-28  8:42         ` Zhu Guihua
2015-01-28  7:45 ` [Qemu-devel] [PATCH v2 2/5] acpi, ich9: Add hotunplug request cb for ich9 Zhu Guihua
2015-01-28  7:59   ` Michael S. Tsirkin
2015-01-28  7:45 ` [Qemu-devel] [PATCH v2 3/5] acpi, pc: Add unplug cb for pc machine Zhu Guihua
2015-01-28  7:45 ` [Qemu-devel] [PATCH v2 4/5] acpi, ich9: Add unplug cb for ich9 Zhu Guihua
2015-01-28  7:45 ` [Qemu-devel] [PATCH v2 5/5] acpi, piix4: Add unplug cb for piix4 Zhu Guihua
2015-01-28  8:00 ` [Qemu-devel] [PATCH v2 0/5] Common unplug and unplug request cb for memory and CPU hot-unplug Michael S. Tsirkin
2015-01-28  8:18   ` Zhu Guihua
2015-01-29  3:19 ` Zhu Guihua
2015-02-03  8:39 ` Zhi Yong Wu

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=1422433982.4145.5.camel@G08FNSTD140041 \
    --to=zhugh.fnst@cn.fujitsu.com \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=hutao@cn.fujitsu.com \
    --cc=imammedo@redhat.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tangchen@cn.fujitsu.com \
    /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).