From: Max Reitz <mreitz@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
Markus Armbruster <armbru@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 05/11] block: Move BDS close notifiers into BB
Date: Mon, 02 Mar 2015 10:18:50 -0500 [thread overview]
Message-ID: <54F47F5A.10803@redhat.com> (raw)
In-Reply-To: <20150228025520.GA27129@ad.nay.redhat.com>
On 2015-02-27 at 21:55, Fam Zheng wrote:
> On Fri, 02/27 11:43, Max Reitz wrote:
>> static void virtio_scsi_hotplug(HotplugHandler *hotplug_dev, DeviceState *dev,
>> Error **errp)
>> {
>> @@ -763,12 +794,26 @@ static void virtio_scsi_hotplug(HotplugHandler *hotplug_dev, DeviceState *dev,
>> SCSIDevice *sd = SCSI_DEVICE(dev);
>>
>> if (s->ctx && !s->dataplane_disabled) {
>> + VirtIOSCSIBlkChangeNotifier *insert_notifier, *remove_notifier;
>> +
>> + insert_notifier = g_new0(VirtIOSCSIBlkChangeNotifier, 1);
>> + insert_notifier->n.notify = virtio_scsi_blk_insert_notifier;
>> + insert_notifier->s = s;
>> + insert_notifier->sd = sd;
>> + blk_add_insert_bs_notifier(sd->conf.blk, &insert_notifier->n);
>> + QTAILQ_INSERT_TAIL(&s->insert_notifiers, insert_notifier, next);
> Could you instead embed a Notifier into SCSIDevice, similarly? That way there
> is no need to maintain a list in VirtIOSCSI.
I thought about that, but somehow SCSIDevice seemed so generic to me...
I didn't really want to add a VirtIOSCSI pointer to it (or even just a
notifier only to be used by virtio-scsi).
So I take it you want me to?
Max
>> +
>> + remove_notifier = g_new0(VirtIOSCSIBlkChangeNotifier, 1);
>> + remove_notifier->n.notify = virtio_scsi_blk_remove_notifier;
>> + remove_notifier->s = s;
>> + remove_notifier->sd = sd;
>> + blk_add_remove_bs_notifier(sd->conf.blk, &remove_notifier->n);
>> + QTAILQ_INSERT_TAIL(&s->remove_notifiers, remove_notifier, next);
>> +
>> if (blk_op_is_blocked(sd->conf.blk, BLOCK_OP_TYPE_DATAPLANE, errp)) {
>> return;
>> }
>> - assert(!s->blocker);
>> - error_setg(&s->blocker, "block device is in use by data plane");
>> - blk_op_block_all(sd->conf.blk, s->blocker);
>> + virtio_scsi_set_up_op_blockers(s, sd);
>> }
> Fam
next prev parent reply other threads:[~2015-03-02 15:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 16:43 [Qemu-devel] [PATCH v4 00/11] block: Rework bdrv_close_all() Max Reitz
2015-02-27 16:43 ` [Qemu-devel] [PATCH v4 01/11] iotests: Move _filter_nbd into common.filter Max Reitz
2015-02-27 16:43 ` [Qemu-devel] [PATCH v4 02/11] iotests: Make redirecting qemu's stderr optional Max Reitz
2015-02-27 16:43 ` [Qemu-devel] [PATCH v4 03/11] iotests: Add test for eject under NBD server Max Reitz
2015-02-27 16:43 ` [Qemu-devel] [PATCH v4 04/11] quorum: Fix close path Max Reitz
2015-02-27 16:43 ` [Qemu-devel] [PATCH v4 05/11] block: Move BDS close notifiers into BB Max Reitz
2015-02-27 20:08 ` Max Reitz
2015-02-28 2:55 ` Fam Zheng
2015-03-02 15:18 ` Max Reitz [this message]
2015-03-03 2:08 ` Fam Zheng
2015-02-27 16:43 ` [Qemu-devel] [PATCH v4 06/11] block: Use blk_remove_bs() in blk_delete() Max Reitz
2015-02-27 16:43 ` [Qemu-devel] [PATCH v4 07/11] blockdev: Use blk_remove_bs() in do_drive_del() Max Reitz
2015-02-27 16:43 ` [Qemu-devel] [PATCH v4 08/11] block: Make bdrv_close() static Max Reitz
2015-02-27 16:43 ` [Qemu-devel] [PATCH v4 09/11] blockdev: Keep track of monitor-owned BDS Max Reitz
2015-02-27 16:43 ` [Qemu-devel] [PATCH v4 10/11] block: Eject BDS tree from BB at bdrv_close_all() Max Reitz
2015-02-27 16:44 ` [Qemu-devel] [PATCH v4 11/11] iotests: Add test for multiple BB on BDS tree Max Reitz
2015-03-02 9:25 ` [Qemu-devel] [PATCH v4 00/11] block: Rework bdrv_close_all() Kevin Wolf
2015-03-02 15:15 ` Max Reitz
2015-03-02 15:57 ` Kevin Wolf
2015-03-02 16:03 ` Max Reitz
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=54F47F5A.10803@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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.