From: Artem Mygaiev <Artem_Mygaiev@epam.com>
To: "andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: "sstabellini@kernel.org" <sstabellini@kernel.org>,
"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"George.Dunlap@eu.citrix.com" <George.Dunlap@eu.citrix.com>,
"tim@xen.org" <tim@xen.org>,
"julien.grall@arm.com" <julien.grall@arm.com>,
"JBeulich@suse.com" <JBeulich@suse.com>,
"ian.jackson@citrix.com" <ian.jackson@citrix.com>
Subject: Re: [PATCH 2/2] docs/hypervisor-guide: Code Coverage
Date: Thu, 4 Apr 2019 12:07:39 +0000 [thread overview]
Message-ID: <b59b01933577e78c305e425cd3bf17efa88d4a3a.camel@epam.com> (raw)
In-Reply-To: <1554303600-27933-3-git-send-email-andrew.cooper3@citrix.com>
Hello Andrew
Minor note below.
On Wed, 2019-04-03 at 16:00 +0100, Andrew Cooper wrote:
[snip]
> + For ARM builds, while Xen will compile with ``CONFIG_COVERAGE``
> enabled, the
> + resulting binary will not successfully boot if it exceeds 2MB in
> size.
> + Xen's early memory management code needs adjusting to resolve this
> issue.
Julien mentioned that on staging the binary is 1.5MB only so we must be
able to run it without changes to Xen mem management. I will ask
someone to try it today or tomorrow and get back with results
-- Artem
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-04-04 12:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 14:59 [PATCH 0/2] docs: Improve coverage docs Andrew Cooper
2019-04-03 14:59 ` [PATCH 1/2] docs/sphinx: Introduce a hypervisor guide section Andrew Cooper
2019-04-04 12:10 ` Wei Liu
2019-04-03 15:00 ` [PATCH 2/2] docs/hypervisor-guide: Code Coverage Andrew Cooper
2019-04-04 12:07 ` Artem Mygaiev [this message]
2019-04-04 12:29 ` Julien Grall
2019-04-04 12:46 ` Andrew Cooper
2019-04-04 13:26 ` Julien Grall
2019-04-04 12:10 ` Wei Liu
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=b59b01933577e78c305e425cd3bf17efa88d4a3a.camel@epam.com \
--to=artem_mygaiev@epam.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--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 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.