From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH DOCDAY] xen: write a high level description of the sub-arch choices for heap layout
Date: Wed, 30 Sep 2015 11:53:29 +0100 [thread overview]
Message-ID: <1443610409.16718.181.camel@citrix.com> (raw)
In-Reply-To: <560BD6A702000078000A703F@prv-mh.provo.novell.com>
On Wed, 2015-09-30 at 04:33 -0600, Jan Beulich wrote:
> > > > On 30.09.15 at 12:22, <ian.campbell@citrix.com> wrote:
> > The 3 options which (sub)arches have for the layout of their heaps is
> > a little subtle (in particular the two CONFIG_SEPARATE_XENHEAP=n
> > submodes) and can be a bit tricky to derive from the code.
> >
> > Therefore try and write down some guidance on what the various modes
> > are.
> >
> > Note that this is intended more as a high level overview rather than a
> > detailed guide to the full page allocator interfaces.
>
> Thanks for writing this up, just two minor things:
>
> > + * CONFIG_SEPARATE_XENHEAP=n W/ DIRECT MAP OF ALL RAM
> > + *
> > + * All of RAM is covered by a permanent contiguous mapping and there
> > + * is only a single heap.
> > + *
> > + * Memory allocated from the Xen heap is flagged (in
> > + * page_info.count_info) with PGC_xen_heap which may be used to
> > + * check and enforce correct usage of va()/pa() etc. Memory
>
> What is this "check and enforce" about? There are validation uses
> of the flag, but I don't recall any in virt<->phys address translation.
I think I misremembered/assumed.
Arm has an is_xen_heap_page check for the separate xenheap case.
I suppose s/may be/could be/ would be true (sort of) but I guess I'll just
drop that bit.
> > + * allocated from the Dom heap must still be explicitly mapped
> > + * before use (e.g. with map_domain_page) in particular in common
> > + * code.
> > + *
> > + * xenheap_max_mfn() should not be called by arch code.
> > + *
> > + * This mode of operation is most commonly used by 64-bit arches
> > + * which have sufficient free virtual address space to permanently
> > + * map the largest practical amount RAM currently expected on that
> > + * arch.
> > + *
> > + * CONFIG_SEPARATE_XENHEAP=n W/ ONLY DIRECT MAP OF ONLY PARTIAL RAM
>
> I think one of the two ONLY should be dropped.
Agreed.
Ian.
next prev parent reply other threads:[~2015-09-30 10:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 10:22 [PATCH DOCDAY] xen: write a high level description of the sub-arch choices for heap layout Ian Campbell
2015-09-30 10:33 ` Jan Beulich
2015-09-30 10:53 ` Ian Campbell [this message]
2015-09-30 11:10 ` Andrew Cooper
2015-09-30 11:28 ` Ian Campbell
2015-09-30 11:29 ` Andrew Cooper
2015-09-30 11:31 ` Ian Campbell
2015-09-30 11:37 ` Andrew Cooper
2015-09-30 11:39 ` Jan Beulich
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=1443610409.16718.181.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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 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.