From: Julien Grall <julien.grall@citrix.com>
To: "Mazen Ezzeddine (Student)" <emm09@mail.aub.edu>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: ARM-Xen customization of stage two translation.
Date: Wed, 20 May 2015 12:52:44 +0100 [thread overview]
Message-ID: <555C758C.3060503@citrix.com> (raw)
In-Reply-To: <1432122444328.21832@mail.aub.edu>
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
next prev parent reply other threads:[~2015-05-20 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 8:39 ARM-Xen customization of stage two translation Mazen Ezzeddine (Student)
2015-05-20 10:33 ` Julien Grall
[not found] ` <1432122444328.21832@mail.aub.edu>
2015-05-20 11:52 ` Julien Grall [this message]
2015-05-20 12:05 ` Mazen Ezzeddine (Student)
2015-05-20 12:11 ` 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=555C758C.3060503@citrix.com \
--to=julien.grall@citrix.com \
--cc=emm09@mail.aub.edu \
--cc=xen-devel@lists.xenproject.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.