From: Julien Grall <julien.grall@arm.com>
To: 조현권 <chkwon91@gmail.com>,
xen-devel@lists.xen.org,
"Stefano Stabellini" <sstabellini@kernel.org>
Subject: Re: Question about device tree block
Date: Thu, 9 Jun 2016 14:02:14 +0100 [thread overview]
Message-ID: <575968D6.8050307@arm.com> (raw)
In-Reply-To: <CA+CgW8cb3+SVx+ZTsWS6yT1o3f4p9VGe5g867bHB95ED6mOucw@mail.gmail.com>
On 09/06/16 00:40, 조현권 wrote:
> Hi i have a question about device tree block area
Hello,
> In the function setup_mm xen copy original device tree block to the end
> of xen heap space
>
> Original device tree block area seems useless during domain0 creation
> but xen discard it with kernel modules after dom0 memory allocation finished
>
> Is there any special reason??
There is no specific reason. It is just easier to discard all the
modules in the same place. Note that we do the same for the XSM module too.
>
> +) what is the job of kernel module?
I am not sure to understand the question here.
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-06-09 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+CgW8djneOvigA8tcX_i3FrA+vS0gq=PCDtRJP9xvZkrzHcLA@mail.gmail.com>
[not found] ` <CA+CgW8cz4zJ_mqH6kH68oSXqKWks68uJbTEL=8SFKYOYsvq_cA@mail.gmail.com>
[not found] ` <CA+CgW8dysbn1JmkurRfQOD+gZGN578CADoPQQg8pgd52cxdp8A@mail.gmail.com>
[not found] ` <CA+CgW8dC8kusmU2Ej6iQ11JBxvdikS=-ABHc81gLuKtnTqMwog@mail.gmail.com>
[not found] ` <CA+CgW8eKg5O8j8iBiJt5b=hO7cO5D1KD7f8eYVUCuqh8gfcEEQ@mail.gmail.com>
[not found] ` <CA+CgW8c7tXVoCnn8mdJ28xOm0Sf1RjJA6p+s9p24mBkPohf=oA@mail.gmail.com>
[not found] ` <CA+CgW8dzVVm7h34mfnGtqq4BoRVsiMJgZsFDzuKvJTV-2JhmQA@mail.gmail.com>
2016-06-08 23:40 ` Question about device tree block 조현권
2016-06-09 13:02 ` Julien Grall [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=575968D6.8050307@arm.com \
--to=julien.grall@arm.com \
--cc=chkwon91@gmail.com \
--cc=sstabellini@kernel.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 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).