qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: stefano.stabellini@eu.citrix.com
Cc: kwolf@redhat.com, xen-devel@lists.xensource.com, mst@redhat.com,
	qemu-devel@nongnu.org, armbru@redhat.com,
	anthony.perard@citrix.com
Subject: Re: [Qemu-devel] [PATCH RESEND v3] xen: implement unplug protocol in xen_platform
Date: Wed, 27 Jul 2011 14:44:19 +0200	[thread overview]
Message-ID: <4E300823.9000408@suse.de> (raw)
In-Reply-To: <1311005222-31060-1-git-send-email-stefano.stabellini@eu.citrix.com>

On 07/18/2011 06:07 PM, stefano.stabellini@eu.citrix.com wrote:
> From: Stefano Stabellini<stefano.stabellini@eu.citrix.com>
>
> The unplug protocol is necessary to support PV drivers in the guest: the
> drivers expect to be able to "unplug" emulated disks and nics before
> initializing the Xen PV interfaces.
> It is responsibility of the guest to make sure that the unplug is done
> before the emulated devices or the PV interface start to be used.
>
> We use pci_for_each_device to walk the PCI bus, identify the devices and
> disks that we want to disable and dynamically unplug them.
>
> Changes in v2:
>
> - use PCI_CLASS constants;
>
> - replace pci_unplug_device with qdev_unplug;
>
> - do not import hw/ide/internal.h in xen_platform.c;
>
>
> Changes in v3:
>
> - introduce piix3-ide-xen, that support hot-unplug;
>
> - move the unplug code to hw/ide/piix.c;
>
> - just call qdev_unplug from xen_platform.c to unplug the IDE disks;
>
> Signed-off-by: Stefano Stabellini<stefano.stabellini@eu.citrix.com>

Kevin, please ack.


Alex

  reply	other threads:[~2011-07-27 12:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 16:07 [Qemu-devel] [PATCH RESEND v3] xen: implement unplug protocol in xen_platform stefano.stabellini
2011-07-27 12:44 ` Alexander Graf [this message]
2011-07-27 12:58   ` Kevin Wolf
2011-07-27 13:26     ` Alexander Graf

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=4E300823.9000408@suse.de \
    --to=agraf@suse.de \
    --cc=anthony.perard@citrix.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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).