Re: [Qemu-block] [PATCH v2 7/8] gluster: Support auto-read-only option

2018-10-14 Thread Niels de Vos
On Fri, Oct 12, 2018 at 12:31:21PM -0500, Eric Blake wrote: > On 10/12/18 6:55 AM, Kevin Wolf wrote: > > If read-only=off, but auto-read-only=on is given, open the file > > read-write if we have the permissions, but instead of erroring out for > > read-only files, just degrade to read-only. > > >

Re: [Qemu-block] [RFC] Require Python 3 for building QEMU

2018-10-14 Thread Max Reitz
On 13.10.18 22:36, Eduardo Habkost wrote: > On Sat, Oct 13, 2018 at 08:20:25PM +0200, Max Reitz wrote: >> On 13.10.18 07:02, Eduardo Habkost wrote: >>> Signed-off-by: Eduardo Habkost >>> --- >>> I'd like to do this in QEMU 3.1. I think it's time to drop >>> support for old systems that have only

[Qemu-block] [PATCH 2/3] Introduce attributes to qemu timer subsystem

2018-10-14 Thread Artem Pisarenko
Attributes are simple flags, associated with individual timers for their whole lifetime. They intended to be used to mark individual timers for special handling by various qemu features operating at qemu core level. Existing timer, aio and coroutine interface extended with attribute-enabled vari

Re: [Qemu-block] [Qemu-devel] [RFC] Require Python 3 for building QEMU

2018-10-14 Thread Markus Armbruster
Max Reitz writes: > On 13.10.18 22:36, Eduardo Habkost wrote: >> On Sat, Oct 13, 2018 at 08:20:25PM +0200, Max Reitz wrote: >>> On 13.10.18 07:02, Eduardo Habkost wrote: Signed-off-by: Eduardo Habkost --- I'd like to do this in QEMU 3.1. I think it's time to drop support for