From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:41591)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1RzshT-00085j-Nj
	for qemu-devel@nongnu.org; Tue, 21 Feb 2012 11:36:24 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1RzshN-0005hq-Qm
	for qemu-devel@nongnu.org; Tue, 21 Feb 2012 11:36:23 -0500
Received: from mx1.redhat.com ([209.132.183.28]:16721)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <kwolf@redhat.com>) id 1RzshN-0005he-HT
	for qemu-devel@nongnu.org; Tue, 21 Feb 2012 11:36:17 -0500
Message-ID: <4F43C8CD.90907@redhat.com>
Date: Tue, 21 Feb 2012 17:39:41 +0100
From: Kevin Wolf <kwolf@redhat.com>
MIME-Version: 1.0
References: <73865e0ce364c40e0eb65ec6b22b819d@mail.gmail.com>
	<4F3137DB.1040503@redhat.com> <4F3139CE.4040103@zerto.com>
	<4F314798.8010009@redhat.com> <4F3211D0.3070502@zerto.com>
	<4F323875.1000000@redhat.com> <4F3244C2.1040604@zerto.com>
	<4F32489A.80307@redhat.com> <4F32788C.60904@zerto.com>
	<CAJSP0QXRdU4XhW2wU+vOPh+vuzEECdKEWUGzaaENEtTbpRfKMg@mail.gmail.com>
	<4F40FBD6.2000500@zerto.com> <4F425987.20103@redhat.com>
	<4F435DD2.8080600@redhat.com> <4F4360C7.5080806@redhat.com>
	<4F4368BF.4040707@redhat.com> <4F436D76.6090206@redhat.com>
	<4F43773B.6060109@redhat.com> <4F4381CE.70604@redhat.com>
	<4F4397D1.2020807@redhat.com>
	<m339a46uz6.fsf@blackfin.pond.sub.org>
	<4F43C097.9050308@redhat.com>
	<m3ipj0qhub.fsf@blackfin.pond.sub.org>
In-Reply-To: <m3ipj0qhub.fsf@blackfin.pond.sub.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] BlockDriverState stack and BlockListeners
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Markus Armbruster <armbru@redhat.com>
Cc: =?UTF-8?B?16rXldee16gg15HXnyDXkNeV16g=?= <tomer@zertodata.com>, =?UTF-8?B?16LXldeT15Mg16fXk9ed?= <oded@zerto.com>, Jeff Cody <jcody@redhat.com>, dlaor@redhat.com, qemu-devel@nongnu.org, Zhi Yong Wu <zwu.kernel@gmail.com>, Federico Simoncelli <fsimonce@redhat.com>, Ori Mamluk <omamluk@zerto.com>, Stefan Hajnoczi <stefanha@gmail.com>, Yair Kuszpet <yairk@zerto.com>, Paolo Bonzini <pbonzini@redhat.com>

Am 21.02.2012 17:19, schrieb Markus Armbruster:
>>>> Oh, and just to open another can of worms: We should probably design=
 in
>>>> the notion of media (which can be ejected etc.) and drives (which al=
ways
>>>> stay there). We don't have a clean separation today.
>>>
>>> The "closed BDS means no media" thing works, but it's odd.
>>
>> I'm more talking about data that belongs to the media, like geometry.
>> This came up recently with Herv=C3=A9's floppy patches.
>=20
> Is geometry relevant to anything but floppies and really small disks
> being accessed via really old interfaces?

Not sure what it's actually used for, but even virtio-blk does have a
geometry.

But is it really only geometry? I think the read-only flag belongs to
the medium as well. There are probably more candidates.

Kevin