From: Zhi Yong Wu <zwu.kernel@gmail.com>
To: KVM mailing list <kvm@vger.kernel.org>,
QEMU Developers <qemu-devel@nongnu.org>,
libvir-list@redhat.com, Eric Blake <eblake@redhat.com>
Cc: loki2441@gmail.com, Zhi Yong Wu <zhiyong.wzy@alibaba-inc.com>
Subject: Re: [Qemu-devel] vmfork in KVM
Date: Fri, 8 May 2015 17:55:54 +0800 [thread overview]
Message-ID: <CAEH94LhQKWqw1qC+aHfSS_ZH93sb1x1XU3ZN-EUPeb8PwRGi4Q@mail.gmail.com> (raw)
In-Reply-To: <CAHqbYQt50ZNoQOaEapc18TLGT+zPXZ6q-gcdUQG+oTSuLJ149Q@mail.gmail.com>
HI, all guys
Why does vmfork not get supported by KVM project? What is the
drawback? It's very cool if it's used in some scenario, e.g. HPC. It
will be appreciated for your comments, thanks.
On Fri, Oct 24, 2014 at 2:25 AM, Hu Yaohui <loki2441@gmail.com> wrote:
> Hi all,
> There are some vmfork features provided by Xen based on shadow page
> table few years ago. I am wondering whether KVM provides the similar
> feature on the same host.
> By triggering vmfork, we can get a child VM which CPU and I/O status
> is the same as the parent, and the memory is CoW shared with parent
> VM.
>
> Thanks,
> Yaohui
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Regards,
Zhi Yong Wu
next parent reply other threads:[~2015-05-08 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHqbYQt50ZNoQOaEapc18TLGT+zPXZ6q-gcdUQG+oTSuLJ149Q@mail.gmail.com>
2015-05-08 9:55 ` Zhi Yong Wu [this message]
2015-05-08 15:07 ` [Qemu-devel] vmfork in KVM Eric Blake
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=CAEH94LhQKWqw1qC+aHfSS_ZH93sb1x1XU3ZN-EUPeb8PwRGi4Q@mail.gmail.com \
--to=zwu.kernel@gmail.com \
--cc=eblake@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@redhat.com \
--cc=loki2441@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=zhiyong.wzy@alibaba-inc.com \
/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;
as well as URLs for NNTP newsgroup(s).