From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@citrix.com>,
"Chris (Christopher) Brand" <chris.brand@broadcom.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>,
Tim Deegan <tim@xen.org>
Subject: Re: [PATCH] xen: arm: Document xenheap_megabytes limitation
Date: Fri, 24 Jul 2015 12:05:18 +0100 [thread overview]
Message-ID: <1437735918.24746.65.camel@citrix.com> (raw)
In-Reply-To: <55B11B1D.1070608@citrix.com>
On Thu, 2015-07-23 at 17:49 +0100, Julien Grall wrote:
> Hi Chris,
>
> Thank you for patch.
>
> On 23/07/15 17:31, Chris (Christopher) Brand wrote:
> > In setup_mm(), the value passed as xenheap_megabytes gets
> > converted to pages and passed to setup_xenheap_mappings(),
> > which in turn passes it to create_32mb_mappings(), which
> > contains an ASSERT that the value passed is a multiple of
> > 32MB. So specifying any value that is not an integer multiple
> > of 32 will cause Xen to hit this assert and fail to boot.
> >
> > Signed-off-by: Chris Brand <chris.brand@broadcom.com>
>
> I wondering if it would worth to add a check in the code to ensure
> that
> it's a multiple of 32MB?
Arguably we have that in the form of the assert/panic, but perhaps
there should be a nicer message.
> Nonetheless:
>
> Reviewed-by: Julien Grall <julien.grall@citrix.com>
Acked + applied.
prev parent reply other threads:[~2015-07-24 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 16:31 [PATCH] xen: arm: Document xenheap_megabytes limitation Chris (Christopher) Brand
2015-07-23 16:49 ` Julien Grall
2015-07-24 11:05 ` Ian Campbell [this message]
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=1437735918.24746.65.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=chris.brand@broadcom.com \
--cc=julien.grall@citrix.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--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.