From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: qemu-kvm.git now live
Date: Wed, 29 Apr 2009 10:42:44 +0000 [thread overview]
Message-ID: <49F82F24.8040506@redhat.com> (raw)
In-Reply-To: <49F08BD0.6000706@redhat.com>
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.
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).
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-04-29 10:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 15:40 qemu-kvm.git now live Avi Kivity
2009-04-29 8:49 ` Jan Kiszka
2009-04-29 10:42 ` Avi Kivity [this message]
2009-04-29 10:55 ` Jan Kiszka
2009-04-29 11:12 ` Avi Kivity
2009-04-29 11:31 ` Jan Kiszka
2009-04-29 14:40 ` Avi Kivity
2009-04-29 15:42 ` Jan Kiszka
2009-04-30 9:12 ` Avi Kivity
2009-04-30 9:29 ` Jan Kiszka
2009-04-30 10:54 ` Avi Kivity
2009-04-30 15:32 ` Jan Kiszka
2009-04-30 15:43 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49F82F24.8040506@redhat.com \
--to=avi@redhat.com \
--cc=kvm-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox