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 12:02:39 +0000 [thread overview]
Message-ID: <5301FA5F.8020602@linaro.org> (raw)
In-Reply-To: <CAH_mUMMtiujzBtvhSDos_SzjzuGeRpbZ6QkNn3PfPN3YjpnN5A@mail.gmail.com>
On 02/17/2014 11:33 AM, Andrii Tseglytskyi wrote:
> Hi,
Hello 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.
> To be more specific - I see the following function:
> *int handle_mmio(mmio_info_t *info)*, which is called from *static
> void do_trap_data_abort_guest(struct cpu_user_regs *regs, union hsr
> hsr)*
> Using these calls I can define memory region and create a trap for it.
> But in current implementation I can do it only during compile time.
> Is there any way to do similar in runtime - i.e. calculate memory
> region value in code and add an entry to mmio_handlers[] ?
> Is it a good idea - just to modify/extend existing code in
> xen/arch/arm/io.c file to make it possible ?
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).
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-02-17 12:02 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 [this message]
2014-02-17 14:06 ` Andrii Tseglytskyi
2014-02-17 14:16 ` Julien Grall
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=5301FA5F.8020602@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.