On Thu, 19 May 2016, Juergen Gross wrote:
> On 19/05/16 12:48, Stefano Stabellini wrote:
> > On Thu, 19 May 2016, Jan Beulich wrote:
> > On 19.05.16 at 12:40, wrote:
> >>> On Thu, 19 May 2016, Juergen Gross wrote:
> > Alternatively, the easiest way will probably be to add a new VMASSIST,
>
On 19/05/16 12:48, Stefano Stabellini wrote:
> On Thu, 19 May 2016, Jan Beulich wrote:
> On 19.05.16 at 12:40, wrote:
>>> On Thu, 19 May 2016, Juergen Gross wrote:
> Alternatively, the easiest way will probably be to add a new VMASSIST,
> which allows the guest to opt into the new beha
On Thu, May 19, 2016 at 12:21:57PM +0200, Dario Faggioli wrote:
> Since, AFAIUI, you're interested in non-Linux guests' perspective, I'm
> adding Roger (and avoiding trimming, for his benefit), who can tell us
> what he thinks of this all, from the FreeBSD point of view.
Thanks, AFAIK vcpu_runstat
On Thu, 19 May 2016, Jan Beulich wrote:
> >>> On 19.05.16 at 12:40, wrote:
> > On Thu, 19 May 2016, Juergen Gross wrote:
> >> > Alternatively, the easiest way will probably be to add a new VMASSIST,
> >> > which allows the guest to opt into the new behaviour.
> >>
> >> Aah, nice. Yes, this seems
>>> On 19.05.16 at 12:40, wrote:
> On Thu, 19 May 2016, Juergen Gross wrote:
>> > Alternatively, the easiest way will probably be to add a new VMASSIST,
>> > which allows the guest to opt into the new behaviour.
>>
>> Aah, nice. Yes, this seems to be a sensible option.
>
> If you are referring t
On Thu, 19 May 2016, Juergen Gross wrote:
> > Alternatively, the easiest way will probably be to add a new VMASSIST,
> > which allows the guest to opt into the new behaviour.
>
> Aah, nice. Yes, this seems to be a sensible option.
If you are referring to VM_ASSIST, it is only available on x86. I
Since, AFAIUI, you're interested in non-Linux guests' perspective, I'm
adding Roger (and avoiding trimming, for his benefit), who can tell us
what he thinks of this all, from the FreeBSD point of view.
On Thu, May 19, 2016 at 10:49 AM, Juergen Gross wrote:
> On 19/05/16 10:09, Andrew Cooper wrote
On 19/05/16 10:09, Andrew Cooper wrote:
> On 19/05/2016 08:53, Juergen Gross wrote:
>> A guest kernel can use the vcpu_op hypercall sub-op
>> VCPUOP_register_runstate_memory_area to get a copy of the
>> vcpu_runstate_info of a vcpu mapped into its memory. As this structure
>> has no update indicato
On 19/05/2016 08:53, Juergen Gross wrote:
> A guest kernel can use the vcpu_op hypercall sub-op
> VCPUOP_register_runstate_memory_area to get a copy of the
> vcpu_runstate_info of a vcpu mapped into its memory. As this structure
> has no update indicator it is only save to be read by the vcpu it is
