On 16/06/16 14:36, Jan Beulich wrote:
On 16.06.16 at 14:11, wrote:
>> On 16/06/16 13:15, Jan Beulich wrote:
>> On 15.06.16 at 13:34, wrote:
+if ( VM_ASSIST(v->domain, runstate_update_flag) )
+{
+off = offsetof(struct vcpu_runstate_info, state_entry_time) +
>>> On 16.06.16 at 14:11, wrote:
> On 16/06/16 13:15, Jan Beulich wrote:
> On 15.06.16 at 13:34, wrote:
>>> +if ( VM_ASSIST(v->domain, runstate_update_flag) )
>>> +{
>>> +off = offsetof(struct vcpu_runstate_info, state_entry_time) +
>>> + sizeof(v->runstate.state_
On 16/06/16 13:15, Jan Beulich wrote:
On 15.06.16 at 13:34, wrote:
>> In order to support reading another vcpu's mapped vcpu_runstate_info
>> an indicator for an occurring update of the runstate information is
>> needed.
>>
>> Add the possibility to activate setting this indicator in the high
>>> On 15.06.16 at 13:34, wrote:
> In order to support reading another vcpu's mapped vcpu_runstate_info
> an indicator for an occurring update of the runstate information is
> needed.
>
> Add the possibility to activate setting this indicator in the highest
> bit of state_entry_time via a vm_assi
In order to support reading another vcpu's mapped vcpu_runstate_info
an indicator for an occurring update of the runstate information is
needed.
Add the possibility to activate setting this indicator in the highest
bit of state_entry_time via a vm_assist hypercall. When activated the
update indica
