public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Wenchao Xia <wenchaolinuxkvm@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: [RFC] provide an API to userspace doing memory snapshot
Date: Tue, 16 Apr 2013 15:54:15 +0800	[thread overview]
Message-ID: <516D03A7.1060206@gmail.com> (raw)
In-Reply-To: <20130416055112.GB5286@stefanha-thinkpad.redhat.com>

于 2013-4-16 13:51, Stefan Hajnoczi 写道:
> On Mon, Apr 15, 2013 at 09:03:36PM +0800, Wenchao Xia wrote:
>>    I'd like to add/export an function which allow userspace program
>> to take snapshot for a region of memory. Since it is not implemented yet
>> I will describe it as C APIs, it is quite simple now and if it is worthy
>> I'll improve the interface later:
>
> We talked about a simple approach using fork(2) on IRC yesterday.
>
> Is this email outdated?
>
> Stefan
>
   No, after the discuss on IRC, I agree that fork() is a simpler
method to do it, which can comes to qemu fast, since user wants it.
   With a more consideration, still I think a KVM's mem snapshot would
be an long term solution for it:
   The source of the problem comes from acceleration module, kvm.ko, when
qemu does not use it, no troubles. This means an acceleration module
missed a function while caller requires. My instinct idea is: when
acceleration module replace a pure software one, it should try provide
all parts or not stop software filling the gap, and doing so brings
benefits, so hope to add it.
   My API description is old, the core is COW pages, maybe redesign if
reasonable.

  reply	other threads:[~2013-04-16  7:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 13:03 [RFC] provide an API to userspace doing memory snapshot Wenchao Xia
2013-04-16  5:51 ` Stefan Hajnoczi
2013-04-16  7:54   ` Wenchao Xia [this message]
2013-04-17 13:57     ` Stefan Hajnoczi

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=516D03A7.1060206@gmail.com \
    --to=wenchaolinuxkvm@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=stefanha@gmail.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