From: Juergen Gross <jgross@suse.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: roger.pau@citrix.com, stefano.stabellini@eu.citrix.com,
ian.jackson@eu.citrix.com, Ian.Campbell@citrix.com,
xen-devel@lists.xen.org
Subject: Re: [PATCH v3 1/9] libxc: reorganize domain builder guest memory allocator
Date: Wed, 28 Oct 2015 18:05:34 +0100 [thread overview]
Message-ID: <5631005E.5050700@suse.com> (raw)
In-Reply-To: <20151028162147.GA8097@zion.uk.xensource.com>
On 10/28/2015 05:21 PM, Wei Liu wrote:
> On Wed, Oct 28, 2015 at 04:51:05PM +0100, Juergen Gross wrote:
> [...]
>>>> +static int xc_dom_alloc_pad(struct xc_dom_image *dom, xen_vaddr_t end)
>>>> +{
>>>> + unsigned int page_size = XC_DOM_PAGE_SIZE(dom);
>>>> + xen_pfn_t pages;
>>>> +
>>>> + if ( end & (page_size - 1) )
>>>> {
>>>> xc_dom_panic(dom->xch, XC_INTERNAL_ERROR,
>>>> "%s: segment start isn't page aligned (0x%" PRIx64 ")",
>>>
>>> "segment end"?
>>
>> No. This function is called to add a padding allocation before the start
>> of a new segment, which has to start at page boundary. Maybe a comment
>> should clarify this. :-)
>>
>
> Heh, I worked out this function was used to add padding segment but
> was confused by the dissonance.
>
> A simpler solution might be just change "end" to "start"? I think it is
> sensible because it is the start of the padding.
Hmm, or use "boundary" for the variable and in the message. :-)
Juergen
next prev parent reply other threads:[~2015-10-28 17:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 13:11 [PATCH v3 0/9] libxc: support building large pv-domains Juergen Gross
2015-10-13 13:11 ` [PATCH v3 1/9] libxc: reorganize domain builder guest memory allocator Juergen Gross
2015-10-28 15:32 ` Wei Liu
2015-10-28 15:51 ` Juergen Gross
2015-10-28 16:21 ` Wei Liu
2015-10-28 17:05 ` Juergen Gross [this message]
2015-10-13 13:11 ` [PATCH v3 2/9] xen: add generic flag to elf_dom_parms indicating support of unmapped initrd Juergen Gross
2015-10-28 15:33 ` Wei Liu
2015-10-28 15:49 ` Jan Beulich
2015-10-13 13:11 ` [PATCH v3 3/9] libxc: rename domain builder count_pgtables to alloc_pgtables Juergen Gross
2015-10-28 15:34 ` Wei Liu
2015-10-13 13:11 ` [PATCH v3 4/9] libxc: introduce domain builder architecture specific data Juergen Gross
2015-10-28 15:37 ` Wei Liu
2015-10-13 13:11 ` [PATCH v3 5/9] libxc: use domain builder architecture private data for x86 pv domains Juergen Gross
2015-10-28 15:38 ` Wei Liu
2015-10-13 13:11 ` [PATCH v3 6/9] libxc: create unmapped initrd in domain builder if supported Juergen Gross
2015-10-28 16:11 ` Wei Liu
2015-10-28 17:07 ` Juergen Gross
2015-10-13 13:11 ` [PATCH v3 7/9] libxc: split p2m allocation in domain builder from other magic pages Juergen Gross
2015-10-28 16:11 ` Wei Liu
2015-10-13 13:11 ` [PATCH v3 8/9] libxc: rework of domain builder's page table handler Juergen Gross
2015-10-29 12:48 ` Wei Liu
2015-10-29 13:18 ` Juergen Gross
2015-10-29 14:02 ` Wei Liu
2015-10-29 14:13 ` Juergen Gross
2015-10-29 15:03 ` Wei Liu
2015-10-29 15:34 ` Juergen Gross
2015-10-13 13:11 ` [PATCH v3 9/9] libxc: create p2m list outside of kernel mapping if supported Juergen Gross
2015-10-29 13:07 ` Wei Liu
2015-10-29 13:19 ` Juergen Gross
2015-10-26 11:15 ` [PATCH v3 0/9] libxc: support building large pv-domains 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=5631005E.5050700@suse.com \
--to=jgross@suse.com \
--cc=Ian.Campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.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 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).