Re: [Qemu-devel] [RFC PATCH 0/6] block: Add driver specific options

2013-02-28 Thread Kevin Wolf
Am 28.02.2013 um 11:23 hat Stefan Hajnoczi geschrieben: > On Wed, Feb 27, 2013 at 06:25:49PM +0100, Kevin Wolf wrote: > > Instead of constantly keeping complaining that we need this big -blockdev > > things, let's start attacking individual parts of the project. Here is the > > first part, allowing

Re: [Qemu-devel] [RFC PATCH 0/6] block: Add driver specific options

2013-02-28 Thread Stefan Hajnoczi
On Wed, Feb 27, 2013 at 06:25:49PM +0100, Kevin Wolf wrote: > Instead of constantly keeping complaining that we need this big -blockdev > things, let's start attacking individual parts of the project. Here is the > first part, allowing block drivers to provide additional -drive options. > > Any op

Re: [Qemu-devel] [RFC PATCH 0/6] block: Add driver specific options

2013-02-28 Thread Kevin Wolf
Am 28.02.2013 um 02:52 hat Eric Blake geschrieben: > On 02/27/2013 10:25 AM, Kevin Wolf wrote: > > Instead of constantly keeping complaining that we need this big -blockdev > > things, let's start attacking individual parts of the project. Here is the > > first part, allowing block drivers to provi

Re: [Qemu-devel] [RFC PATCH 0/6] block: Add driver specific options

2013-02-27 Thread Eric Blake
On 02/27/2013 10:25 AM, Kevin Wolf wrote: > Instead of constantly keeping complaining that we need this big -blockdev > things, let's start attacking individual parts of the project. Here is the > first part, allowing block drivers to provide additional -drive options. So, if I understand the impl

[Qemu-devel] [RFC PATCH 0/6] block: Add driver specific options

2013-02-27 Thread Kevin Wolf
Instead of constantly keeping complaining that we need this big -blockdev things, let's start attacking individual parts of the project. Here is the first part, allowing block drivers to provide additional -drive options. Any options that isn't processed by the block layer is passed to the driver