Re: [Qemu-devel] [RFC PATCH 0/7] BlockBackends, nodes and guest devices

2016-06-27 Thread Max Reitz
On 27.06.2016 18:38, Kevin Wolf wrote: > Am 27.06.2016 um 18:13 hat Max Reitz geschrieben: >> I'm not sure if WCE truly is a guest device property, but adding it as a >> guest device property and then syncing it to the BB makes sense (as done >> in patch 7). > > It is truly a guest device property

Re: [Qemu-devel] [RFC PATCH 0/7] BlockBackends, nodes and guest devices

2016-06-27 Thread Kevin Wolf
Am 27.06.2016 um 18:13 hat Max Reitz geschrieben: > I'm not sure if WCE truly is a guest device property, but adding it as a > guest device property and then syncing it to the BB makes sense (as done > in patch 7). It is truly a guest device property. Physical hardware can have a volatile write ca

Re: [Qemu-devel] [RFC PATCH 0/7] BlockBackends, nodes and guest devices

2016-06-27 Thread Max Reitz
On 23.06.2016 16:36, Kevin Wolf wrote: > I am relatively confident to say that everything that should use a > BlockBackend, does so by now. Almost all users create their own anonymous > BlockBackend internally and use that. The user configures the BB only > indirectly using the configuration method

Re: [Qemu-devel] [RFC PATCH 0/7] BlockBackends, nodes and guest devices

2016-06-23 Thread Paolo Bonzini
On 23/06/2016 16:36, Kevin Wolf wrote: > But of course I'm aware that there probably isn't a clear right or wrong, and > that I might be missing important details, so this needs to be discussed in > advance before I go and implement the full thing instead of just small example > patches. > > So

[Qemu-devel] [RFC PATCH 0/7] BlockBackends, nodes and guest devices

2016-06-23 Thread Kevin Wolf
I am relatively confident to say that everything that should use a BlockBackend, does so by now. Almost all users create their own anonymous BlockBackend internally and use that. The user configures the BB only indirectly using the configuration methods of the user that the BB belongs to. There is