From: Kevin Wolf <kwolf@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"mst@redhat.com" <mst@redhat.com>,
"armbru@redhat.com" <armbru@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"agraf@suse.de" <agraf@suse.de>,
Anthony Perard <anthony.perard@citrix.com>
Subject: Re: [Qemu-devel] [PATCH v3] xen: implement unplug protocol in xen_platform
Date: Fri, 15 Jul 2011 12:52:52 +0200 [thread overview]
Message-ID: <4E201C04.9090500@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1107151125150.12963@kaball-desktop>
Am 15.07.2011 12:34, schrieb Stefano Stabellini:
> On Fri, 1 Jul 2011, Stefano Stabellini wrote:
>> On Fri, 1 Jul 2011, Kevin Wolf wrote:
>>> Am 30.06.2011 16:16, schrieb Stefano Stabellini:
>>>> On Thu, 30 Jun 2011, Kevin Wolf wrote:
>>>>>> +static int pci_piix3_xen_ide_unplug(DeviceState *dev)
>>>>>> +{
>>>>>> + PCIDevice *pci_dev;
>>>>>> + PCIIDEState *pci_ide;
>>>>>> + DriveInfo *di;
>>>>>> + int i = 0;
>>>>>> +
>>>>>> + pci_dev = DO_UPCAST(PCIDevice, qdev, dev);
>>>>>> + pci_ide = DO_UPCAST(PCIIDEState, dev, pci_dev);
>>>>>> +
>>>>>> + for (; i < 3; i++) {
>>>>>> + di = drive_get_by_index(IF_IDE, i);
>>>>>> + if (di != NULL && di->bdrv != NULL && !di->bdrv->removable) {
>>>>>> + DeviceState *ds = bdrv_get_attached(di->bdrv);
>>>>>> + if (ds) {
>>>>>> + bdrv_detach(di->bdrv, ds);
>>>>>> + }
>>>>>> + bdrv_close(di->bdrv);
>>>>>> + pci_ide->bus[di->bus].ifs[di->unit].bs = NULL;
>>>>>
>>>>> Have you tested if this is enough if the guest tries to continue using
>>>>> the device? I don't know of any case where it's not sufficient, just
>>>>> trying to make sure that it's really true in practice.
>>>>
>>>> The purpose of this is to "hide" the disk from the guest. The unplug is
>>>> supposed to happen *before* the guest enumerates the IDE disks; it is
>>>> responsibility of the guest to make sure of it.
>>>> I tested it with Linux PV on HVM drivers, and Linux doesn't see the
>>>> emulated disk after the unplug, as it should be.
>>>
>>> Yeah. What I meant is that we should make sure that a misbehaving guest,
>>> which just keeps on playing with the IDE ports anyway, can't crash qemu.
>>> A quick review suggests that it is the case, but testing it anyway would
>>> be better.
>>
>> I see what you mean: I tested it, a guest cannot crash Qemu.
>>
>
> ping?
I thought Alex had already merged it. I'm pretty sure that I stated
somewhere that the patch is okay for me now. In case I didn't:
Acked-by: Kevin Wolf <kwolf@redhat.com>
next prev parent reply other threads:[~2011-07-15 10:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 11:29 [Qemu-devel] [PATCH v3] xen: implement unplug protocol in xen_platform stefano.stabellini
2011-06-30 11:45 ` Alexander Graf
2011-06-30 12:16 ` Kevin Wolf
2011-06-30 12:14 ` Alexander Graf
2011-06-30 12:12 ` Kevin Wolf
2011-06-30 14:16 ` Stefano Stabellini
2011-07-01 8:05 ` Kevin Wolf
2011-07-01 17:30 ` Stefano Stabellini
2011-07-15 10:34 ` Stefano Stabellini
2011-07-15 10:52 ` Kevin Wolf [this message]
2011-07-18 12:25 ` Alexander Graf
2011-07-18 16:03 ` Stefano Stabellini
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=4E201C04.9090500@redhat.com \
--to=kwolf@redhat.com \
--cc=agraf@suse.de \
--cc=anthony.perard@citrix.com \
--cc=armbru@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).