From: Keir Fraser <keir.xen@gmail.com>
To: Kai Luo <kluo@vmware.com>, xen-devel@lists.xensource.com
Subject: Re: Question about mapping hvmŒs memory to dom0
Date: Mon, 01 Jul 2013 06:37:32 +0100 [thread overview]
Message-ID: <CDF6D42C.55E26%keir.xen@gmail.com> (raw)
In-Reply-To: <1747857728.13873212.1372645948621.JavaMail.root@vmware.com>
[-- Attachment #1.1: Type: text/plain, Size: 945 bytes --]
The HVM domain is not destroyed while there are still external mappings of
its memory.
On 01/07/2013 03:32, "Kai Luo" <kluo@vmware.com> wrote:
> Hi:
> I am trying to make some source code modifications to map the hvm
> memory to dom0,I use the xc_map_foreign_bulk to do this,It works and I export
> the hvm's memory to a file. My question is,after mapping the memory I use
> xc_domain_destroy to shutdown the running hvm,theoretically the mapped memory
> will be scrubbed because xen will scrubbed the hvm's memory before they are
> freed to xen hyperviser,however I export the mapped memory after destroying
> hvm,finding the content in mapped memory nearly same as formly exported,they
> are not scrubbed at all.That confused me.Can you give me any suggestion?
>
> Thank you
> Jone
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 1725 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-07-01 5:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <183829454.13872961.1372645851829.JavaMail.root@vmware.com>
2013-07-01 2:32 ` Question about mapping hvm‘s memory to dom0 Kai Luo
2013-07-01 5:37 ` Keir Fraser [this message]
2013-07-01 5:58 ` Question about mapping hvmŒs " Kai Luo
2013-07-01 9:52 ` Question about mapping hvm‘s " George Dunlap
2013-07-01 10:19 ` Dietmar Hahn
2013-07-02 13:31 ` Kai Luo
2013-07-02 13:43 ` George Dunlap
2013-07-02 14:26 ` Kai Luo
2013-07-02 16:51 ` George Dunlap
2013-07-02 17:50 ` Andres Lagar-Cavilla
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=CDF6D42C.55E26%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=kluo@vmware.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.