From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?7KGw7ZiE6raM?= Subject: Question about device tree block Date: Thu, 9 Jun 2016 08:40:22 +0900 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0791449271779954700==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============0791449271779954700== Content-Type: multipart/alternative; boundary=001a1140a32a3f072d0534ccd4d1 --001a1140a32a3f072d0534ccd4d1 Content-Type: text/plain; charset=UTF-8 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? --001a1140a32a3f072d0534ccd4d1 Content-Type: text/html; charset=UTF-8

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?

--001a1140a32a3f072d0534ccd4d1-- --===============0791449271779954700== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9y Zy94ZW4tZGV2ZWwK --===============0791449271779954700==--