> On Feb 15, 2019, at 2:02 PM, Jan Beulich wrote:
>
On 15.02.19 at 14:51, wrote:
>
>>
>>> On Feb 15, 2019, at 1:47 PM, Andrew Cooper
>>> wrote:
>>>
>>> On 15/02/2019 13:37, George Dunlap wrote:
>> The one issue is that domain_pause_except_self() currently is actually a
>>> On 15.02.19 at 14:51, wrote:
>
>> On Feb 15, 2019, at 1:47 PM, Andrew Cooper wrote:
>>
>> On 15/02/2019 13:37, George Dunlap wrote:
>>>
> The one issue is that domain_pause_except_self() currently is actually a
> deadlock risk if two different vcpus start it at the same time. I
On 2/15/19 3:37 PM, George Dunlap wrote:
On Feb 15, 2019, at 1:24 PM, Jan Beulich wrote:
On 15.02.19 at 13:52, wrote:
On Feb 12, 2019, at 11:42 AM, Razvan Cojocaru wrote:
HVMOP_altp2m_set_domain_state does not domain_pause(), presumably
on purpose (as it was originally supposed to
> On Feb 15, 2019, at 1:47 PM, Andrew Cooper wrote:
>
> On 15/02/2019 13:37, George Dunlap wrote:
>>
The one issue is that domain_pause_except_self() currently is actually a
deadlock risk if two different vcpus start it at the same time. I think
the
attached patch
On 15/02/2019 13:37, George Dunlap wrote:
>
>>> The one issue is that domain_pause_except_self() currently is actually a
>>> deadlock risk if two different vcpus start it at the same time. I think
>>> the
>>> attached patch (compile-tested only) should fix this issue; after this
>>> patch
>>> On 15.02.19 at 14:37, wrote:
>> On Feb 15, 2019, at 1:24 PM, Jan Beulich wrote:
>> And two cosmetic remarks - there's no need to re-specify
>> __must_check on the function definition, as the function
>> declaration ought to be in scope anyway. And there's a stray
>> blank inside the likely()
> On Feb 15, 2019, at 1:24 PM, Jan Beulich wrote:
>
On 15.02.19 at 13:52, wrote:
>>> On Feb 12, 2019, at 11:42 AM, Razvan Cojocaru
>>> wrote:
>>>
>>> HVMOP_altp2m_set_domain_state does not domain_pause(), presumably
>>> on purpose (as it was originally supposed to cater to a in-guest
On Feb 12, 2019, at 11:42 AM, Razvan Cojocaru wrote:
HVMOP_altp2m_set_domain_state does not domain_pause(), presumably
on purpose (as it was originally supposed to cater to a in-guest
agent, and a domain pausing itself is not a good idea).
Sorry to come in here on v4 and suggest changing
>>> On 15.02.19 at 13:52, wrote:
>> On Feb 12, 2019, at 11:42 AM, Razvan Cojocaru
>> wrote:
>>
>> HVMOP_altp2m_set_domain_state does not domain_pause(), presumably
>> on purpose (as it was originally supposed to cater to a in-guest
>> agent, and a domain pausing itself is not a good idea).
>
> On Feb 12, 2019, at 11:42 AM, Razvan Cojocaru
> wrote:
>
> HVMOP_altp2m_set_domain_state does not domain_pause(), presumably
> on purpose (as it was originally supposed to cater to a in-guest
> agent, and a domain pausing itself is not a good idea).
Sorry to come in here on v4 and suggest
On 2/14/19 8:06 PM, George Dunlap wrote:
> On 2/12/19 11:42 AM, Razvan Cojocaru wrote:
>> HVMOP_altp2m_set_domain_state does not domain_pause(), presumably
>> on purpose (as it was originally supposed to cater to a in-guest
>> agent, and a domain pausing itself is not a good idea).
>>
>> This can
On 2/12/19 11:42 AM, Razvan Cojocaru wrote:
> HVMOP_altp2m_set_domain_state does not domain_pause(), presumably
> on purpose (as it was originally supposed to cater to a in-guest
> agent, and a domain pausing itself is not a good idea).
>
> This can lead to domain crashes in the
On 2/12/19 2:57 PM, Jan Beulich wrote:
On 12.02.19 at 12:42, wrote:
HVMOP_altp2m_set_domain_state does not domain_pause(), presumably
on purpose (as it was originally supposed to cater to a in-guest
agent, and a domain pausing itself is not a good idea).
This can lead to domain crashes in the
>>> On 12.02.19 at 12:42, wrote:
> HVMOP_altp2m_set_domain_state does not domain_pause(), presumably
> on purpose (as it was originally supposed to cater to a in-guest
> agent, and a domain pausing itself is not a good idea).
>
> This can lead to domain crashes in the vmx_vmexit_handler() code
>
14 matches
Mail list logo
