Re: [Xen-devel] [ARM] Native application design and discussion (I hope)

[Julien Grall <julien.grall@xxxxxxx>]

Hello Volodymyr,

On 20/04/17 21:20, Volodymyr Babchuk wrote:
> On 12 April 2017 at 22:17, Stefano Stabellini <sstabellini@xxxxxxxxxx> wrote:
> > On Wed, 12 Apr 2017, Dario Faggioli wrote:
> > > On Tue, 2017-04-11 at 13:32 -0700, Stefano Stabellini wrote:
> > > > On Fri, 7 Apr 2017, Stefano Stabellini wrote:
> > We would have one app per emulator. Each app would register an MMIO
> > range or instruction set to emulate. On a guest trap, Xen figures out
> > which app it needs to run.
> I't is not best approach, I think. For example we need one SMC handler for
> all domains. Because that SMC handler should track execution state of different
> guests to help TEE with scheduling. You know, TEE can't block in secure state,
> so it returns back and blocks in kernel driver. SMC handler need to know
> which guest it needs to wake up when times comes.
>
> The same story with virtual coprocessors, I think.
>
> On other hand, MMIO handler can be one per domain. So, it should be
> configurable. Or, maybe we need per-app MMIO handler and one global SMC handler.
> Perhaps, we need to think about all possible use cases.
Could you explain what would be the benefits to run this global SMC 
handler in EL0?
After all, it will require access to the host SMC. So what will you 
protect against?
Cheers,

--
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel