From: David Vrabel <david.vrabel@citrix.com>
To: Juergen Gross <jgross@suse.com>, <linux-kernel@vger.kernel.org>,
<xen-devel@lists.xensource.com>, <konrad.wilk@oracle.com>,
<david.vrabel@citrix.com>, <boris.ostrovsky@oracle.com>,
<linux-mm@kvack.org>
Subject: Re: [Xen-devel] [Patch V2 02/15] xen: save linear p2m list address in shared info structure
Date: Thu, 9 Apr 2015 09:24:47 +0100 [thread overview]
Message-ID: <5526374F.50401@citrix.com> (raw)
In-Reply-To: <1428562542-28488-3-git-send-email-jgross@suse.com>
On 09/04/15 07:55, Juergen Gross wrote:
> The virtual address of the linear p2m list should be stored in the
> shared info structure read by the Xen tools to be able to support
> 64 bit pv-domains larger than 512 GB. Additionally the linear p2m
> list interface includes a generation count which is changed prior
> to and after each mapping change of the p2m list. Reading the
> generation count the Xen tools can detect changes of the mappings
> and re-read the p2m list eventually.
Reviewed-by: David Vrabel <david.vrabel@citrix.com>
David
next prev parent reply other threads:[~2015-04-09 8:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 6:55 [Patch V2 00/15] xen: support pv-domains larger than 512GB Juergen Gross
2015-04-09 6:55 ` [Patch V2 01/15] xen: sync with xen headers Juergen Gross
2015-04-09 8:23 ` [Xen-devel] " David Vrabel
2015-04-09 6:55 ` [Patch V2 02/15] xen: save linear p2m list address in shared info structure Juergen Gross
2015-04-09 8:24 ` David Vrabel [this message]
2015-04-09 6:55 ` [Patch V2 03/15] xen: don't build mfn tree if tools don't need it Juergen Gross
2015-04-09 8:26 ` [Xen-devel] " David Vrabel
2015-04-09 6:55 ` [Patch V2 04/15] xen: eliminate scalability issues from initial mapping setup Juergen Gross
2015-04-09 6:55 ` [Patch V2 05/15] xen: move static e820 map to global scope Juergen Gross
2015-04-09 6:55 ` [Patch V2 06/15] xen: split counting of extra memory pages from remapping Juergen Gross
2015-04-09 6:55 ` [Patch V2 07/15] xen: check memory area against e820 map Juergen Gross
2015-04-09 8:29 ` [Xen-devel] " David Vrabel
2015-04-09 6:55 ` [Patch V2 08/15] xen: find unused contiguous memory area Juergen Gross
2015-04-09 12:41 ` [Xen-devel] " David Vrabel
2015-04-09 6:55 ` [Patch V2 09/15] xen: check for kernel memory conflicting with memory layout Juergen Gross
2015-04-09 12:42 ` [Xen-devel] " David Vrabel
2015-04-09 6:55 ` [Patch V2 10/15] xen: check pre-allocated page tables for conflict with memory map Juergen Gross
2015-04-09 12:47 ` [Xen-devel] " David Vrabel
2015-04-09 13:09 ` Juergen Gross
2015-04-09 6:55 ` [Patch V2 11/15] xen: check for initrd conflicting with e820 map Juergen Gross
2015-04-09 12:58 ` [Xen-devel] " David Vrabel
2015-04-09 6:55 ` [Patch V2 12/15] mm: provide early_memremap_ro to establish read-only mapping Juergen Gross
2015-04-09 6:55 ` [Patch V2 13/15] xen: move p2m list if conflicting with e820 map Juergen Gross
2015-04-09 6:55 ` [Patch V2 14/15] xen: allow more than 512 GB of RAM for 64 bit pv-domains Juergen Gross
2015-04-09 6:55 ` [Patch V2 15/15] xen: remove no longer needed p2m.h Juergen Gross
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=5526374F.50401@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 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).