xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: 조현권 <chkwon91@gmail.com>
To: xen-devel@lists.xen.org
Subject: Question about device tree block
Date: Thu, 9 Jun 2016 08:40:22 +0900	[thread overview]
Message-ID: <CA+CgW8cb3+SVx+ZTsWS6yT1o3f4p9VGe5g867bHB95ED6mOucw@mail.gmail.com> (raw)
In-Reply-To: <CA+CgW8dzVVm7h34mfnGtqq4BoRVsiMJgZsFDzuKvJTV-2JhmQA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 358 bytes --]

Hi i have a question about device tree block area

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??

+) what is the job of kernel module?

[-- Attachment #1.2: Type: text/html, Size: 439 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

       reply	other threads:[~2016-06-08 23:40 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             ` 조현권 [this message]
2016-06-09 13:02               ` Question about device tree block Julien Grall

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=CA+CgW8cb3+SVx+ZTsWS6yT1o3f4p9VGe5g867bHB95ED6mOucw@mail.gmail.com \
    --to=chkwon91@gmail.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).