From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NXakJ-0001fg-Dr for qemu-devel@nongnu.org; Wed, 20 Jan 2010 08:37:19 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NXakF-0001er-LP for qemu-devel@nongnu.org; Wed, 20 Jan 2010 08:37:19 -0500 Received: from [199.232.76.173] (port=38510 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NXakF-0001eo-Gh for qemu-devel@nongnu.org; Wed, 20 Jan 2010 08:37:15 -0500 Received: from mail2.shareable.org ([80.68.89.115]:57146) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NXakF-0000He-44 for qemu-devel@nongnu.org; Wed, 20 Jan 2010 08:37:15 -0500 Date: Wed, 20 Jan 2010 13:37:13 +0000 From: Jamie Lokier Subject: Re: [Qemu-devel] Re: [PATCH v2 2/4] Clean-up a little bit the RW related bits of BDRV_O_FLAGS. BDRV_O_RDONLY gone (and so is BDRV_O_ACCESS). Default value for bdrv_flags (0/zero) is READ-ONLY. Need to explicitly request READ-WRITE. Message-ID: <20100120133713.GC30789@shareable.org> References: <1263739695-13043-1-git-send-email-nsprei@redhat.com> <1263739695-13043-2-git-send-email-nsprei@redhat.com> <1263739695-13043-3-git-send-email-nsprei@redhat.com> <20100117153202.GC3420@redhat.com> <20100118104816.GC5874@redhat.com> <20100120020543.GG11920@shareable.org> <20100120103248.GA22941@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100120103248.GA22941@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Naphtali Sprei , Markus Armbruster , qemu-devel@nongnu.org Michael S. Tsirkin wrote: > On Wed, Jan 20, 2010 at 08:26:56AM +0100, Markus Armbruster wrote: > > Jamie Lokier writes: > > > > > Michael S. Tsirkin wrote: > > >> On Mon, Jan 18, 2010 at 11:34:59AM +0100, Markus Armbruster wrote: > > >> > BDRV_O_RDWR is a flag, just like BDRV_SNAPSHOT. We don't have > > >> > BDRV_DONT_SNAPSHOT, either. > > >> > > >> Well, this just mirros the file access macros: we have RDONLY, WRONLY > > >> and RDRW. I assume this similarity is just historical? > > > > > > To avoid confusion, why don't we just call the flag BDRV_O_WRITABLE. > > > Then it's obvious what clearing that flag means. > > > > Sounds good to me. > > Won't it be confused with WRONLY? No, because nobody sane would expect qemu's blockdevs to need WRONLY :-) -- Jamie