From: Julien Grall <julien.grall@linaro.org>
To: Andrii Tseglytskyi <andrii.tseglytskyi@globallogic.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: run time memory trap question
Date: Mon, 17 Feb 2014 14:16:36 +0000 [thread overview]
Message-ID: <530219C4.3050304@linaro.org> (raw)
In-Reply-To: <CAH_mUMP4kebPOn7xdSCgD4PqoxdkHYHHwghQukyAk+QLKO95SA@mail.gmail.com>
On 02/17/2014 02:06 PM, Andrii Tseglytskyi wrote:
> Hi Julien,
Hi Andrii,
>
> > Can anyone clarify - is it possible to make a run time memory trap in
> > Xen hypervisor?
>
> I guess you are talking about ARM? If so, it's not possible right now.
>
>
> Does it mean, that it is possible on x86 ?
Yes, you can look at register_io_handler in xen/arch/x86/hvm/intercept.c
It's used a static array, but I don't think this is the solution for
ARM. We don't know in advance the maximum number of MMIO region to handle.
>
> I think yes, we might need that for a couple of new features in Xen such
> as: clock drivers and multiple devices in a same page (see UARTs on
> cubieboard 2).
>
>
> This sounds good. For now I need this or similar solution for my
> development. I'll try to make it generic and post it to this list as
> soon as it is ready.
Great, thank you.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-02-17 14:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 11:33 run time memory trap question Andrii Tseglytskyi
2014-02-17 12:02 ` Julien Grall
2014-02-17 14:06 ` Andrii Tseglytskyi
2014-02-17 14:16 ` Julien Grall [this message]
2014-02-17 15:01 ` Andrii Tseglytskyi
2014-02-17 15:02 ` Stefano Stabellini
2014-02-17 15:19 ` Julien Grall
2014-02-17 15:38 ` Andrii Tseglytskyi
2014-02-17 15:56 ` Julien Grall
2014-02-18 11:05 ` Ian Campbell
2014-02-18 17:52 ` Andrii Tseglytskyi
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=530219C4.3050304@linaro.org \
--to=julien.grall@linaro.org \
--cc=andrii.tseglytskyi@globallogic.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.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 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.