qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcos Oviedo <moviedo.maillist@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] monitor: Add force option support to pci_del command
Date: Wed, 9 Jun 2010 11:00:06 -0300	[thread overview]
Message-ID: <AANLkTikxXDikl-mG-jnFiTc57HYcehx1s8R5yISgeDA5@mail.gmail.com> (raw)
In-Reply-To: <4C0F450B.5000802@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

On Wed, Jun 9, 2010 at 4:38 AM, Gerd Hoffmann <kraxel@redhat.com> wrote:

> On 06/09/10 07:37, Marcos Oviedo wrote:
>
>> This adds a way to force the removal/unplug of previously added pci
>> devices when ACPI-based hotplug mechanism is not present.
>>
>
> Point being?
>
> If your guest can't handle pci hotplug it is pretty useless to plug in
> hardware in the first place.
>
> If your guest supports pci hotplug it will be quite upset if you zap the
> hardware without asking via ACPI.
>

This make sense when you mistakenly add a pci device on a -s -S scenario,
like the scenario described on the following bug:
https://bugs.launchpad.net/qemu/+bug/544367.

When ACPI-based hotplug support is present on the guest and we run pci_del
with the force option, the hotplug events will still be generated to the
guest and the guest still will trigger the EJx event, which will end by
calling pciej_write() on qemu side. This function will do nothing on a -f
and pci hotplug support scenario, as the pci device was previously removed
by pci_del.

Thanks!

Marcos



>
> cheers,
>  Gerd
>
>

[-- Attachment #2: Type: text/html, Size: 1819 bytes --]

  reply	other threads:[~2010-06-09 14:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09  5:37 [Qemu-devel] [PATCH] monitor: Add force option support to pci_del command Marcos Oviedo
2010-06-09  6:39 ` Markus Armbruster
2010-06-09  7:38 ` Gerd Hoffmann
2010-06-09 14:00   ` Marcos Oviedo [this message]
2010-06-09 14:27     ` Gerd Hoffmann
2010-06-14 16:59       ` Anthony Liguori
2010-06-15  8:46         ` Gerd Hoffmann
2010-06-15  9:03         ` Markus Armbruster
2010-06-17 18:15           ` Luiz Capitulino
2010-06-17 18:20             ` Anthony Liguori

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=AANLkTikxXDikl-mG-jnFiTc57HYcehx1s8R5yISgeDA5@mail.gmail.com \
    --to=moviedo.maillist@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.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 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).