Re: [Xen-devel] [PATCH v2 1/8] public / x86: Introduce __HYPERCALL_dm_op...

2016-12-15 Thread Paul Durrant
> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 15 December 2016 15:23 > To: Paul Durrant > Cc: Andrew Cooper ; Ian Jackson > ; Jennifer Herbert ; > Wei Liu ; xen-de...@lists.xenproject.org; Daniel De > Graaf > Subject: Re: [PATCH v2 1/8] public / x86: Introduc

Re: [Xen-devel] [PATCH v2 1/8] public / x86: Introduce __HYPERCALL_dm_op...

2016-12-15 Thread Jan Beulich
>>> On 06.12.16 at 14:46, wrote: > ...as a set of hypercalls to be used by a device model. > > As stated in the new docs/designs/dm_op.markdown: > > "The aim of DMOP is to prevent a compromised device model from > compromising domains other then the one it is associated with. (And is > therefore

Re: [Xen-devel] [PATCH v2 1/8] public / x86: Introduce __HYPERCALL_dm_op...

2016-12-12 Thread Wei Liu
On Tue, Dec 06, 2016 at 01:46:12PM +, Paul Durrant wrote: > ...as a set of hypercalls to be used by a device model. [...] > +Introduction > + > + > +A previous proposal for a 'DMOP' was put forward by Ian Jackson on the 1st > +of August. This proposal seem very promising, however a

[Xen-devel] [PATCH v2 1/8] public / x86: Introduce __HYPERCALL_dm_op...

2016-12-06 Thread Paul Durrant
...as a set of hypercalls to be used by a device model. As stated in the new docs/designs/dm_op.markdown: "The aim of DMOP is to prevent a compromised device model from compromising domains other then the one it is associated with. (And is therefore likely already compromised)." See that file fo