From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Liu Ping Fan <pingfank@linux.vnet.ibm.com>,
Liu Ping Fan <qemulist@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qom: removal of link property need to release its target
Date: Thu, 23 Aug 2012 10:35:02 +0200 [thread overview]
Message-ID: <5035EB36.40807@redhat.com> (raw)
In-Reply-To: <87mx1mo8iy.fsf@codemonkey.ws>
Il 23/08/2012 00:40, Anthony Liguori ha scritto:
> I don't really like the notion of a "forced eject" where we delete a
> device when the guest is using it and not cooperative. I don't see the
> benefit at all.
>
> Forcing detachment of a BlockDriverState from a device followed by EIO
> being reported to the guest for all I/O ops makes sense to me. But not
> forced removal of virtio-blk-pci.
PCI express even has support for detecting surprise removal early (with
card presence detection pins, that break contact before others) and
remove power before damaging the hardware. It's very much a real thing.
You could surprise-remove an assigned card from under the feet of a
non-cooperating guest, for example.
Paolo
next prev parent reply other threads:[~2012-08-23 8:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 3:02 [Qemu-devel] [PATCH] qom: removal of link property need to release its target Liu Ping Fan
2012-08-22 12:02 ` Paolo Bonzini
2012-08-22 16:36 ` Anthony Liguori
2012-08-22 20:55 ` Paolo Bonzini
2012-08-22 21:41 ` Anthony Liguori
2012-08-22 22:01 ` Paolo Bonzini
2012-08-22 22:40 ` Anthony Liguori
2012-08-23 8:35 ` Paolo Bonzini [this message]
2012-08-23 8:02 ` liu ping fan
2012-08-22 17:07 ` Andreas Färber
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=5035EB36.40807@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=pingfank@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemulist@gmail.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).