Re: [Xen-devel] [PATCH v6 04/10] xen: Introduce XENMEM_soft_reset operation

2015-05-26 Thread Jan Beulich
>>> On 26.05.15 at 10:05, wrote: > No, not really. Protecting against a misbehaving control domain > (guaranteeing the correctness of the operation) is going > to be incomplete anyway. I think we just need to make this operation > safe so even the control domain won't be able to compromise the > h

Re: [Xen-devel] [PATCH v6 04/10] xen: Introduce XENMEM_soft_reset operation

2015-05-26 Thread Vitaly Kuznetsov
Tim Deegan writes: > At 12:06 +0200 on 25 May (143265), Vitaly Kuznetsov wrote: >> Tim Deegan writes: >> >> > At 17:26 +0100 on 22 May (1432315574), Jan Beulich wrote: >> >> >>> On 22.05.15 at 17:36, wrote: >> >> > On 13.05.15 at 11:49, wrote: >> >> >>> +if ( !source_d->is_dying )

Re: [Xen-devel] [PATCH v6 04/10] xen: Introduce XENMEM_soft_reset operation

2015-05-25 Thread Tim Deegan
At 12:06 +0200 on 25 May (143265), Vitaly Kuznetsov wrote: > Tim Deegan writes: > > > At 17:26 +0100 on 22 May (1432315574), Jan Beulich wrote: > >> >>> On 22.05.15 at 17:36, wrote: > >> > On 13.05.15 at 11:49, wrote: > >> >>> +if ( !source_d->is_dying ) > >> >>> +{ > >> >>> +

Re: [Xen-devel] [PATCH v6 04/10] xen: Introduce XENMEM_soft_reset operation

2015-05-25 Thread Vitaly Kuznetsov
Tim Deegan writes: > At 17:26 +0100 on 22 May (1432315574), Jan Beulich wrote: >> >>> On 22.05.15 at 17:36, wrote: >> > On 13.05.15 at 11:49, wrote: >> >>> +if ( !source_d->is_dying ) >> >>> +{ >> >>> +/* >> >>> + * Make sure no allocation/remapping for the source do

Re: [Xen-devel] [PATCH v6 04/10] xen: Introduce XENMEM_soft_reset operation

2015-05-25 Thread Tim Deegan
At 17:26 +0100 on 22 May (1432315574), Jan Beulich wrote: > >>> On 22.05.15 at 17:36, wrote: > > On 13.05.15 at 11:49, wrote: > >>> +if ( !source_d->is_dying ) > >>> +{ > >>> +/* > >>> + * Make sure no allocation/remapping for the source domain is > >>> ongoing > >>>

Re: [Xen-devel] [PATCH v6 04/10] xen: Introduce XENMEM_soft_reset operation

2015-05-22 Thread Jan Beulich
>>> On 22.05.15 at 17:36, wrote: > On 13.05.15 at 11:49, wrote: >>> +if ( !source_d->is_dying ) >>> +{ >>> +/* >>> + * Make sure no allocation/remapping for the source domain is >>> ongoing >>> + * and set is_dying flag to prevent such actions in future. >>> +

Re: [Xen-devel] [PATCH v6 04/10] xen: Introduce XENMEM_soft_reset operation

2015-05-22 Thread Vitaly Kuznetsov
"Jan Beulich" writes: On 13.05.15 at 11:49, wrote: >> --- a/xen/common/memory.c >> +++ b/xen/common/memory.c >> @@ -580,6 +580,234 @@ static long >> memory_exchange(XEN_GUEST_HANDLE_PARAM(xen_memory_exchange_t) arg) >> return rc; >> } >> >> +static long >> memory_soft_reset(XEN_GU

Re: [Xen-devel] [PATCH v6 04/10] xen: Introduce XENMEM_soft_reset operation

2015-05-22 Thread Jan Beulich
>>> On 13.05.15 at 11:49, wrote: > --- a/xen/common/memory.c > +++ b/xen/common/memory.c > @@ -580,6 +580,234 @@ static long > memory_exchange(XEN_GUEST_HANDLE_PARAM(xen_memory_exchange_t) arg) > return rc; > } > > +static long > memory_soft_reset(XEN_GUEST_HANDLE_PARAM(xen_memory_soft_r

[Xen-devel] [PATCH v6 04/10] xen: Introduce XENMEM_soft_reset operation

2015-05-13 Thread Vitaly Kuznetsov
New operation reassigns all memory pages from source domain to the destination domain mapping them at exactly the same GFNs. Pages mapped more than once (e.g. grants) are being copied. Signed-off-by: Vitaly Kuznetsov --- xen/common/memory.c | 232 +