On 19 November 2014 14:19, Paolo Bonzini <pbonz...@redhat.com> wrote: > On 19/11/2014 15:10, Peter Maydell wrote: >> Would it be feasible to just have the migration code provide >> an API for registering things to be migrated in the live >> migration stage, rather than creating memory regions which >> you can't actually use for most of the purposes the memory >> region API exists for? > > It does already, for example PPC uses it for its IOMMU tables. > > But in any case this is really just memory that is auto-resized on > migration. And it can work even if it is mapped in memory, as long as > your resize callback (or some post_load code executed while migrating > devices) does something useful to update the memory map. Let's call it > like what it is.
...so why all the "this isn't going to work in KVM" warnings in the patchset? thanks -- PMM
