qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 v3 05/11] block: Move BDS close notifiers into BB
Date: Thu, 26 Feb 2015 08:59:57 -0500	[thread overview]
Message-ID: <54EF26DD.6040008@redhat.com> (raw)
In-Reply-To: <20150226021910.GD10137@ad.nay.redhat.com>

On 2015-02-25 at 21:19, Fam Zheng wrote:
> On Wed, 02/25 09:12, Max Reitz wrote:
>> Because I need a Notifier pointer to give to
>> blk_add_{insert,remove}_bs_notifier(), and most importantly because the only
>> "opaque" object the callbacks will receive is that Notifier pointer (which
>> in this case is actually a DataPlaneBlkChangeNotifier pointer). I cannot
>> influence the @data parameter, and I cannot (easily) identify the
>> VirtIOBlockDataPlane object from the BlockBackend (which is @data) alone.
> Probably like this:
>
>      struct VirtIOBlockDataPlane {
>          ...
>          Notifier insert_notifier, remove_notifier;
>          ...
>      };
>
>      static void data_plane_blk_insert_notifier(Notifier *n, void *data)
>      {
>          VirtIOBlockDataPlane *s = container_of(n, VirtIOBlockDataPlane, insert_notifier);
>          assert(s->conf->conf.blk == data);
>          data_plane_set_up_op_blockers(s);
>      }
>
>      void virtio_blk_data_plane_create(VirtIODevice *vdev, VirtIOBlkConf *conf,
>                                        VirtIOBlockDataPlane **dataplane,
>      {
>          ...
>          s->insert_notifier.notify = data_plane_blk_insert_notifier;
>          blk_add_insert_bs_notifier(conf->conf.blk, &s->insert_notifier);
>          ...
>      }
>
> ?

Oh, right, thanks!

>> Won't virtio_scsi_hotunplug() (which frees s->{insert,remove}_notifier) be
>> called before a second device is plugged?
>>
> No, multiple SCSIDevice objects (scsi-disk, scsi-generic, etc...) can be
> attached to the same virtio-scsi bus.

You're right, I'll see to it.

Thanks,

Max

  reply	other threads:[~2015-02-26 14:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 15:35 [Qemu-devel] [PATCH v3 00/11] block: Rework bdrv_close_all() Max Reitz
2015-02-24 15:35 ` [Qemu-devel] [PATCH v3 01/11] iotests: Move _filter_nbd into common.filter Max Reitz
2015-02-25  6:46   ` Fam Zheng
2015-02-25 13:53     ` Max Reitz
2015-02-24 15:35 ` [Qemu-devel] [PATCH v3 02/11] iotests: Do not redirect qemu's stderr Max Reitz
2015-02-25  7:04   ` Fam Zheng
2015-02-25 14:01     ` Max Reitz
2015-02-26  2:29       ` Fam Zheng
2015-02-26 14:03         ` Max Reitz
2015-02-24 15:35 ` [Qemu-devel] [PATCH v3 03/11] iotests: Add test for eject under NBD server Max Reitz
2015-02-24 15:35 ` [Qemu-devel] [PATCH v3 04/11] quorum: Fix close path Max Reitz
2015-02-25  7:12   ` Fam Zheng
2015-02-25 14:08     ` Max Reitz
2015-02-24 15:35 ` [Qemu-devel] [PATCH v3 05/11] block: Move BDS close notifiers into BB Max Reitz
2015-02-25  7:52   ` Fam Zheng
2015-02-25 14:12     ` Max Reitz
2015-02-26  2:19       ` Fam Zheng
2015-02-26 13:59         ` Max Reitz [this message]
2015-02-24 15:35 ` [Qemu-devel] [PATCH v3 06/11] block: Use blk_remove_bs() in blk_delete() Max Reitz
2015-02-24 15:36 ` [Qemu-devel] [PATCH v3 07/11] blockdev: Use blk_remove_bs() in do_drive_del() Max Reitz
2015-02-24 15:36 ` [Qemu-devel] [PATCH v3 08/11] block: Make bdrv_close() static Max Reitz
2015-02-24 15:36 ` [Qemu-devel] [PATCH v3 09/11] blockdev: Keep track of monitor-owned BDS Max Reitz
2015-02-24 15:36 ` [Qemu-devel] [PATCH v3 10/11] block: Eject BDS tree from BB at bdrv_close_all() Max Reitz
2015-02-24 15:36 ` [Qemu-devel] [PATCH v3 11/11] iotests: Add test for multiple BB on BDS tree 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=54EF26DD.6040008@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 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).