All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	QEMU-devel <qemu-devel@nongnu.org>,
	Anthony Liguori <anthony@codemonkey.ws>,
	Xen Devel <xen-devel@lists.xen.org>
Subject: Re: [Qemu-devel] [PATCH 4/4] xen: Fix PV-on-HVM
Date: Wed, 16 May 2012 16:24:15 +0300	[thread overview]
Message-ID: <20120516132415.GC8620@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1205161133270.26786@kaball-desktop>

On Wed, May 16, 2012 at 11:37:02AM +0100, Stefano Stabellini wrote:
> On Wed, 16 May 2012, Michael S. Tsirkin wrote:
> > On Wed, May 16, 2012 at 11:19:53AM +0100, Stefano Stabellini wrote:
> > > On Wed, 16 May 2012, Paolo Bonzini wrote:
> > > > Il 16/05/2012 10:13, Michael S. Tsirkin ha scritto:
> > > > > On Wed, May 16, 2012 at 10:06:25AM +0200, Paolo Bonzini wrote:
> > > > >> On Xen the PV drivers can ask the firmware to surprise-remove the
> > > > >> emulated NICs.
> > > > > 
> > > > > So driver tells firmware (meaning acpi? how?) that it's ok
> > > > > to do surprize removal?
> > > > 
> > > > It writes something to some I/O port, and then QEMU surprise-removes the
> > > > NICs.
> > > 
> > > Yes, writing to a static I/O port provided by the Xen platform PCI
> > > device, see hw/xen_platform.c:platform_fixed_ioport_writew.
> > > 
> > > The guest can ask to unplug emulated NICs and disks this way.
> > > Surprise-removal is OK in these cases.
> > 
> > Confused.
> > Don't you want to just remove the device on unplug?
> 
> Yes, the NIC needs to "disappear" from the PCI bus.
> 
> 
> > In fact the equivalent of guest calling _EJ0?
> 
> Except that _EJ0 can or cannot be implemented, while this doesn't have
> to go through ACPI or PCI hotplug and it is supposed to always work.

So the answer is to simply free on unplug exactly
like _EJ0 does. There's no forcing and no surprise removal here.

-- 
MST

  reply	other threads:[~2012-05-16 13:24 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 15:26 [Qemu-devel] [PATCH 1.1 0/4] Xen: Fix PV-on-HVM Anthony PERARD
2012-05-15 15:26 ` [Qemu-devel] [PATCH 1/4] Introduce a new hotplug state: Force eject Anthony PERARD
2012-05-15 15:26   ` Anthony PERARD
2012-05-15 18:19   ` [Qemu-devel] " Stefano Stabellini
2012-05-15 18:25     ` Anthony PERARD
2012-05-15 18:25     ` Anthony PERARD
2012-05-15 18:19   ` Stefano Stabellini
2012-05-15 20:52   ` Michael S. Tsirkin
2012-05-15 20:52   ` [Qemu-devel] " Michael S. Tsirkin
2012-05-16 10:32     ` Stefano Stabellini
2012-05-16 11:15       ` Anthony PERARD
2012-05-16 11:23         ` Paolo Bonzini
2012-05-16 11:37           ` Anthony PERARD
2012-05-16 13:20             ` Michael S. Tsirkin
2012-05-16 13:20             ` Michael S. Tsirkin
2012-05-16 15:52               ` Paolo Bonzini
2012-05-16 15:52               ` [Qemu-devel] " Paolo Bonzini
2012-05-16 16:25                 ` Michael S. Tsirkin
2012-05-16 16:25                 ` [Qemu-devel] " Michael S. Tsirkin
2012-05-16 11:37           ` Anthony PERARD
2012-05-16 16:02           ` Anthony Liguori
2012-05-16 16:02           ` [Qemu-devel] " Anthony Liguori
2012-05-16 16:24             ` Michael S. Tsirkin
2012-05-16 16:24             ` Michael S. Tsirkin
2012-05-16 11:23         ` Paolo Bonzini
2012-05-16 11:15       ` [Qemu-devel] " Anthony PERARD
2012-05-16 10:32     ` Stefano Stabellini
2012-05-15 15:26 ` [Qemu-devel] [PATCH 2/4] qdev: Introduce qdev_force_unplug Anthony PERARD
2012-05-15 15:26   ` Anthony PERARD
2012-05-15 18:15   ` Stefano Stabellini
2012-05-15 18:15   ` [Qemu-devel] " Stefano Stabellini
2012-05-15 18:22     ` Anthony PERARD
2012-05-15 18:22     ` Anthony PERARD
2012-05-15 15:26 ` [Qemu-devel] [PATCH 3/4] pci: Add force_unplug callback Anthony PERARD
2012-05-15 15:26   ` Anthony PERARD
2012-05-15 15:26 ` [Qemu-devel] [PATCH 4/4] xen: Fix PV-on-HVM Anthony PERARD
2012-05-15 15:26   ` Anthony PERARD
2012-05-15 21:00   ` Michael S. Tsirkin
2012-05-15 21:00   ` [Qemu-devel] " Michael S. Tsirkin
2012-05-16  8:06     ` Paolo Bonzini
2012-05-16  8:13       ` Michael S. Tsirkin
2012-05-16  8:13       ` [Qemu-devel] " Michael S. Tsirkin
2012-05-16  8:42         ` Paolo Bonzini
2012-05-16  8:42         ` [Qemu-devel] " Paolo Bonzini
2012-05-16 10:19           ` Stefano Stabellini
2012-05-16 10:19           ` [Qemu-devel] " Stefano Stabellini
2012-05-16 10:30             ` Michael S. Tsirkin
2012-05-16 10:30             ` [Qemu-devel] " Michael S. Tsirkin
2012-05-16 10:37               ` Stefano Stabellini
2012-05-16 13:24                 ` Michael S. Tsirkin [this message]
2012-05-16 13:24                 ` Michael S. Tsirkin
2012-05-16 10:37               ` Stefano Stabellini
2012-05-16  8:06     ` Paolo Bonzini
2012-05-15 16:26 ` [PATCH 1.1 0/4] Xen: " Anthony Liguori
2012-05-15 16:26 ` [Qemu-devel] " Anthony Liguori
2012-05-15 16:42   ` Stefano Stabellini
2012-05-15 16:42   ` [Qemu-devel] " Stefano Stabellini
2012-05-15 18:20 ` Stefano Stabellini
2012-05-15 18:20 ` Stefano Stabellini
2012-05-15 21:06 ` Michael S. Tsirkin
2012-05-15 21:06 ` [Qemu-devel] " Michael S. Tsirkin

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=20120516132415.GC8620@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony.perard@citrix.com \
    --cc=anthony@codemonkey.ws \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.