Avi Kivity wrote: > Jan Kiszka wrote: >> Avi Kivity wrote: >> >>> After a lengthy testing phase, qemu-kvm.git has replaced >>> kvm-userspace.git as the source repository for kvm userspace >>> development. >>> >>> Differences from kvm-userspace.git are as follows: >>> - everything under qemu/ has been moved to the top-level directory >>> - everything not under qemu/ has been moved under a new top-level >>> directory, kvm/ >>> - all qemu subversion commits have been rewritten to be compatible with >>> what will become the master qemu git repository >>> - all branches and tags have been converted >>> - qemu-kvm.git builds standalone (does not require kvm.git) >>> >>> The repository is compatible with upstream qemu.git; merges and >>> cherry-picking will work fine in either direction >>> >>> Still missing: >>> - I have not tested powerpc or ia64. Patches welcome! >>> - testsuite (kvm/user/ directory) does not build >>> >> >> - proper guest memory setup >> >> During merge with upstream, the call to qemu_alloc_physram dropped under >> the table (due to removal of phys_ram_base from qemu). And that means we >> no longer call kvm_setup_guest_memory (fork will cause troubles, deja >> vu...) and -mempath is broken. Sorry, I'm not deep enough into all parts >> to provide a quick-fix. >> > > That's unrelated to the repository conversion. Then it's a merge artifact, but it's a problematic regression compared to still-working kvm-userspace. > > I'm unhappy with both qemu.git and qemu-kvm.git memory slot management; > qemu-kvm.git is clumsy, and qemu.git is too simplistic (for example, it > ignores the fact that dirty logging is a global resource with multiple > users). Don't get your point yet. Can you name a concrete scenario that is problematic in upstream? I'd really like to get slot management right there before we drop the old version of qemu-kvm. Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux -- To unsubscribe from this list: send the line "unsubscribe kvm-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
