Re: [Qemu-devel] [PATCH 0/3] migration: export cap/params to qdev props

2017-07-16 Thread Peter Xu
On Fri, Jul 14, 2017 at 12:57:15PM -0300, Eduardo Habkost wrote: > On Fri, Jul 14, 2017 at 12:23:06PM +0800, Peter Xu wrote: > > On Wed, Jul 12, 2017 at 08:02:40PM +0100, Dr. David Alan Gilbert wrote: > > > * Peter Xu (pet...@redhat.com) wrote: > > > > We have the MigrationState as QDev now (which

Re: [Qemu-devel] [PATCH 0/3] migration: export cap/params to qdev props

2017-07-16 Thread Peter Xu
On Fri, Jul 14, 2017 at 05:32:10PM +0100, Dr. David Alan Gilbert wrote: > * Eduardo Habkost (ehabk...@redhat.com) wrote: > > On Fri, Jul 14, 2017 at 01:04:23PM +0800, Peter Xu wrote: > > > On Wed, Jul 12, 2017 at 04:05:58PM -0300, Eduardo Habkost wrote: > > > > On Wed, Jul 12, 2017 at 02:53:40PM

Re: [Qemu-devel] [PATCH 0/3] migration: export cap/params to qdev props

2017-07-14 Thread Dr. David Alan Gilbert
* Eduardo Habkost (ehabk...@redhat.com) wrote: > On Fri, Jul 14, 2017 at 01:04:23PM +0800, Peter Xu wrote: > > On Wed, Jul 12, 2017 at 04:05:58PM -0300, Eduardo Habkost wrote: > > > On Wed, Jul 12, 2017 at 02:53:40PM +0800, Peter Xu wrote: > > > [...] > > > > These properties should only be used

Re: [Qemu-devel] [PATCH 0/3] migration: export cap/params to qdev props

2017-07-14 Thread Eduardo Habkost
On Fri, Jul 14, 2017 at 01:04:23PM +0800, Peter Xu wrote: > On Wed, Jul 12, 2017 at 04:05:58PM -0300, Eduardo Habkost wrote: > > On Wed, Jul 12, 2017 at 02:53:40PM +0800, Peter Xu wrote: > > [...] > > > These properties should only be used for debugging/testing purpose, > > > and we should not

Re: [Qemu-devel] [PATCH 0/3] migration: export cap/params to qdev props

2017-07-14 Thread Eduardo Habkost
On Fri, Jul 14, 2017 at 12:23:06PM +0800, Peter Xu wrote: > On Wed, Jul 12, 2017 at 08:02:40PM +0100, Dr. David Alan Gilbert wrote: > > * Peter Xu (pet...@redhat.com) wrote: > > > We have the MigrationState as QDev now (which seems crazy). Let's > > > continue to benefit. > > > > > > This series

Re: [Qemu-devel] [PATCH 0/3] migration: export cap/params to qdev props

2017-07-13 Thread Peter Xu
On Wed, Jul 12, 2017 at 04:05:58PM -0300, Eduardo Habkost wrote: > On Wed, Jul 12, 2017 at 02:53:40PM +0800, Peter Xu wrote: > [...] > > These properties should only be used for debugging/testing purpose, > > and we should not guarantee any interface compatibility for them (just > > like HMP). >

Re: [Qemu-devel] [PATCH 0/3] migration: export cap/params to qdev props

2017-07-13 Thread Peter Xu
On Wed, Jul 12, 2017 at 08:02:40PM +0100, Dr. David Alan Gilbert wrote: > * Peter Xu (pet...@redhat.com) wrote: > > We have the MigrationState as QDev now (which seems crazy). Let's > > continue to benefit. > > > > This series is exporting all migration capabilities/params as global > >

Re: [Qemu-devel] [PATCH 0/3] migration: export cap/params to qdev props

2017-07-12 Thread Eduardo Habkost
On Wed, Jul 12, 2017 at 02:53:40PM +0800, Peter Xu wrote: [...] > These properties should only be used for debugging/testing purpose, > and we should not guarantee any interface compatibility for them (just > like HMP). If we don't guarantee compatibility, the property names need to be prefixed

Re: [Qemu-devel] [PATCH 0/3] migration: export cap/params to qdev props

2017-07-12 Thread Dr. David Alan Gilbert
* Peter Xu (pet...@redhat.com) wrote: > We have the MigrationState as QDev now (which seems crazy). Let's > continue to benefit. > > This series is exporting all migration capabilities/params as global > parameters. Then we can do something like this: > > qemu -global

[Qemu-devel] [PATCH 0/3] migration: export cap/params to qdev props

2017-07-12 Thread Peter Xu
We have the MigrationState as QDev now (which seems crazy). Let's continue to benefit. This series is exporting all migration capabilities/params as global parameters. Then we can do something like this: qemu -global migration.postcopy-ram=true \ -global migration.max-bandwidth=4096