Re: Notes on stubdoms and latency on ARM

[Dario Faggioli <dario.faggioli@citrix.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1268 bytes --]

On Mon, 2017-06-19 at 11:26 -0700, Volodymyr Babchuk wrote:
> On 19 June 2017 at 02:37, George Dunlap <george.dunlap@citrix.com>
> wrote:
> > If you want this "EL0 app" thing to be able to provide extra
> > security
> > over just running the code inside of Xen, then the code must not be
> > able
> > to DoS the host by spinning forever instead of returning.
> 
> Right. This is a problem. Fortunately, it is running with interrupts
> enabled, so next timer tick will switch back to XEN. There you can
> terminate app which is running too long.
> 
What timer tick? Xen does not have one. A scheduler may setup one, if
it's necessary for its own purposes, but that's entirely optional. For
example, Credit does have one; Credit2, RTDS and null do not.

Basically, (one of the) main purposes of this new "EL0 app mechanism"
is playing behind the scheduler back. Well, fine, but then you're not
allowed to assume that the scheduler will rescue you if something goes
wrong.

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

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