From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: ARM-Xen customization of stage two translation. Date: Wed, 20 May 2015 12:52:44 +0100 Message-ID: <555C758C.3060503@citrix.com> References: <1432111140692.73283@mail.aub.edu>,<555C62E5.3020809@citrix.com> <1432122444328.21832@mail.aub.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yv2Yq-0005zU-GF for xen-devel@lists.xenproject.org; Wed, 20 May 2015 11:53:20 +0000 In-Reply-To: <1432122444328.21832@mail.aub.edu> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Mazen Ezzeddine (Student)" , xen-devel List-Id: xen-devel@lists.xenproject.org Hello, Please keep xen-devel CCed and avoid to top-post. On 20/05/15 12:47, Mazen Ezzeddine (Student) wrote: > Thanks Jlien, > > Mainly it belongs to a device. I can't see why it would be problematic for a device and not for RAM or vice-versa? could you please hint me on what is the difference? Because you have to do it differently. For avoiding DOM0 to use a device, you can blacklist it per platform (see blacklist_dev xen/arch/arm/platforms/vexpress.c). While for the RAM you can update your device tree (see /memreserve/). Regards, -- Julien Grall