From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:39017)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lvivier@redhat.com>) id 1ZAfK8-0002iw-0q
	for qemu-devel@nongnu.org; Thu, 02 Jul 2015 10:18:48 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lvivier@redhat.com>) id 1ZAfK7-00063X-4A
	for qemu-devel@nongnu.org; Thu, 02 Jul 2015 10:18:43 -0400
Message-ID: <55954836.3060700@redhat.com>
Date: Thu, 02 Jul 2015 16:18:30 +0200
From: Laurent Vivier <lvivier@redhat.com>
MIME-Version: 1.0
References: <AB4CFA84-0BE1-41D1-A825-E879FD3EF2CB@gmail.com>
	<CAJSP0QX2VOBPx=vGQVsJ+Ci8iw4k+nP9ggjivrX0xD4jaKKXKg@mail.gmail.com>
	<55952D97.7040009@redhat.com> <559540F6.9090800@redhat.com>
	<55954384.9010906@redhat.com> <559544C4.4050809@redhat.com>
In-Reply-To: <559544C4.4050809@redhat.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH] raw-posix.c: remove raw device access for
	cdrom
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: Paolo Bonzini <pbonzini@redhat.com>, Stefan Hajnoczi <stefanha@gmail.com>, Programmingkid <programmingkidx@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Peter Maydell <peter.maydell@linaro.org>, John Snow <jsnow@redhat.com>, qemu-devel qemu-devel <qemu-devel@nongnu.org>, Qemu-block <qemu-block@nongnu.org>



On 02/07/2015 16:03, Paolo Bonzini wrote:
> 
> 
> On 02/07/2015 15:58, Laurent Vivier wrote:
>> Since any /dev entry can be treated as a raw disk image, it is worth
>> noting which devices can be accessed when and how. /dev/rdisk nodes are
>> character-special devices, but are "raw" in the BSD sense and force
>> block-aligned I/O. They are closer to the physical disk than the buffer
>> cache. /dev/disk nodes, on the other hand, are buffered block-special
>> devices and are used primarily by the kernel's filesystem code.
> 
> So the right thing to do would not be just to set need_alignment, but to
> probe it like we do on Linux for BDRV_O_NO_CACHE.
> 
> I'm okay with doing the simple thing, but it needs a comment for non-BSDers.

So, what we have to do, in our case, for MacOS X cdrom, is something like:

... GetBSDPath ...
...
    if (flags & BDRV_O_NOCACHE) {
        strcat(bsdPath, "r");
    }
...

?

Laurent