From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Juergen Gross <jgross@suse.com>, xen-devel@lists.xenproject.org
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
George.Dunlap@eu.citrix.com, ian.jackson@eu.citrix.com,
tim@xen.org, jbeulich@suse.com
Subject: Re: [PATCH 0/2] xen: modify dom0 interface for obtaining memory map
Date: Mon, 5 Dec 2016 16:39:08 +0000 [thread overview]
Message-ID: <32f8b48f-1b3e-843c-bb0d-c9a7f3a32b05@citrix.com> (raw)
In-Reply-To: <20161205163409.16714-1-jgross@suse.com>
On 05/12/16 16:34, Juergen Gross wrote:
> Today's interface to get the machine memory map in dom0 requires to
> know in advance how large the final map will be. There is however no
> way to either get only a part of the memory map or to ask the
> hypervisor about its size.
>
> This patch set enhances the XENMEM_machine_memory_map hypercall to
> solve both issues by returning only a partial memory map in case the
> supplied buffer was too small and to return the needed number of
> entries if no buffer is being supplied.
These changes appear to be a good improvement in behaviour.
However, there is a way to know the exact size of the memory map. Use
XENMEM_maximum_ram_page to find the maximum mfn, and use that to
calculate the size of the mapping.
See tools/libxc/xc_sr_common_x86_pv.c: x86_pv_map_m2p()
(Not that I think this interface is very nice either...)
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-12-05 16:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 16:34 [PATCH 0/2] xen: modify dom0 interface for obtaining memory map Juergen Gross
2016-12-05 16:34 ` [PATCH 1/2] xen/x86: return partial memory map in case of not enough space Juergen Gross
2016-12-05 17:17 ` Jan Beulich
[not found] ` <5845AF3E020000780012541F@suse.com>
2016-12-06 7:43 ` Juergen Gross
2016-12-06 8:15 ` Jan Beulich
[not found] ` <584681CA020000780012577A@suse.com>
2016-12-06 8:33 ` Juergen Gross
2016-12-06 8:51 ` Jan Beulich
[not found] ` <58468A1202000078001257BE@suse.com>
2016-12-06 9:44 ` Juergen Gross
2016-12-06 9:51 ` Jan Beulich
2016-12-05 16:34 ` [PATCH 2/2] xen/x86: add a way to obtain the needed number of memory map entries Juergen Gross
2016-12-05 16:39 ` Andrew Cooper [this message]
2016-12-05 16:43 ` [PATCH 0/2] xen: modify dom0 interface for obtaining memory map Juergen Gross
2016-12-05 17:06 ` Andrew Cooper
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=32f8b48f-1b3e-843c-bb0d-c9a7f3a32b05@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).