From: shiraz.linux.kernel@gmail.com (shiraz hashim)
To: linux-arm-kernel@lists.infradead.org
Subject: questions about arm trustzone
Date: Fri, 11 Mar 2011 18:32:26 +0530 [thread overview]
Message-ID: <AANLkTinQf+psOnb_r38PdOzRMArcxOdKkQgO3g_3SCGS@mail.gmail.com> (raw)
In-Reply-To: <bb0c3855a121603232d022b4062752a6@mail.gmail.com>
Hello Santosh,
On Tue, Jan 25, 2011 at 5:16 PM, Santosh Shilimkar
<santosh.shilimkar@ti.com> wrote:
[...]
> The code above won't give major details of how the monitor mode is
> implemented. ?But as Russell said, it's pretty much vendor specific.
>
> On OMAP, We have standard API interfaces to enter into monitor
> world. One of the parameter denotes the kind of service, is
> requested.
Sorry if following are very naive.
What should be the attributes of a monitor implementation.
- Should it be un-modifiable.
- Does it run in normal (non-secure) mode ?
- Who programs the monitor (and its vector addresses) ?
- Would monitor intend to provide fixed services and how does it
decides that the request for a particular service is valid enough to
enter secure world ?
- Are monitors debuggable ?
thanks in advance for any kind help.
--
regards
Shiraz Hashim
prev parent reply other threads:[~2011-03-11 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 2:15 questions about arm trustzone sen wang
2011-01-25 7:49 ` David Brown
2011-01-25 9:19 ` sen wang
2011-01-25 10:26 ` Russell King - ARM Linux
2011-01-25 11:46 ` Santosh Shilimkar
2011-01-25 12:00 ` Russell King - ARM Linux
2011-01-25 12:24 ` Dave Martin
2011-01-25 12:45 ` Russell King - ARM Linux
2011-01-25 13:25 ` Dave Martin
2011-03-11 13:02 ` shiraz hashim [this message]
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=AANLkTinQf+psOnb_r38PdOzRMArcxOdKkQgO3g_3SCGS@mail.gmail.com \
--to=shiraz.linux.kernel@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).