On 08/04/2016 02:12 PM, Julien Grall wrote:
> Hello Razvan,
>
> On 04/08/16 10:00, Razvan Cojocaru wrote:
>> On 08/04/2016 11:51 AM, Jan Beulich wrote:
>> On 04.08.16 at 10:21, wrote:
Looking at xen/common/domctl.c, it appears that during handling of
XEN_DOMCTL_setvcpucontext, a dom
On 08/04/2016 02:08 PM, Julien Grall wrote:
>
>
> On 04/08/16 09:21, Razvan Cojocaru wrote:
>> Hello,
>
> Hello Razvan,
>
>> Looking at xen/common/domctl.c, it appears that during handling of
>> XEN_DOMCTL_setvcpucontext, a domain_pause() happens unconditionally:
>>
>> 465 if ( ret ==
Hello Razvan,
On 04/08/16 10:00, Razvan Cojocaru wrote:
On 08/04/2016 11:51 AM, Jan Beulich wrote:
On 04.08.16 at 10:21, wrote:
Looking at xen/common/domctl.c, it appears that during handling of
XEN_DOMCTL_setvcpucontext, a domain_pause() happens unconditionally:
465 if ( ret == 0 )
On 04/08/16 09:21, Razvan Cojocaru wrote:
Hello,
Hello Razvan,
Looking at xen/common/domctl.c, it appears that during handling of
XEN_DOMCTL_setvcpucontext, a domain_pause() happens unconditionally:
465 if ( ret == 0 )
466 {
467 domain_pause(d);
468
On 08/04/2016 11:51 AM, Jan Beulich wrote:
On 04.08.16 at 10:21, wrote:
>> Looking at xen/common/domctl.c, it appears that during handling of
>> XEN_DOMCTL_setvcpucontext, a domain_pause() happens unconditionally:
>>
>> 465 if ( ret == 0 )
>> 466 {
>> 467 domain
>>> On 04.08.16 at 10:21, wrote:
> Looking at xen/common/domctl.c, it appears that during handling of
> XEN_DOMCTL_setvcpucontext, a domain_pause() happens unconditionally:
>
> 465 if ( ret == 0 )
> 466 {
> 467 domain_pause(d);
> 468 ret = arch_set_info
Hello,
Looking at xen/common/domctl.c, it appears that during handling of
XEN_DOMCTL_setvcpucontext, a domain_pause() happens unconditionally:
465 if ( ret == 0 )
466 {
467 domain_pause(d);
468 ret = arch_set_info_guest(v, c);
469 domain_un
