On 22.07.2015 16:03, Peter Maydell wrote:
> On 22 July 2015 at 13:56, Claudio Fontana wrote:
>>
>> I can if you want check if this patch actually fixes the problem without the
>> KVM workaround.
>> Is this the version I am supposed to test, or should I wait for the next
>> respin?
>
> Fixed ver
On 22 July 2015 at 13:56, Claudio Fontana wrote:
>
> I can if you want check if this patch actually fixes the problem without the
> KVM workaround.
> Is this the version I am supposed to test, or should I wait for the next
> respin?
Fixed version went into master earlier this week, so test that
On 17.07.2015 17:39, Christoffer Dall wrote:
> On Fri, Jul 17, 2015 at 03:29:56PM +0100, Peter Maydell wrote:
>> On 16 July 2015 at 12:34, Christoffer Dall
>> wrote:
>>> Some registers like the CNTVCT register should only be written to the
>>> kernel as part of machine initialization or on vmload
On Fri, Jul 17, 2015 at 03:29:56PM +0100, Peter Maydell wrote:
> On 16 July 2015 at 12:34, Christoffer Dall
> wrote:
> > Some registers like the CNTVCT register should only be written to the
> > kernel as part of machine initialization or on vmload operations, but
> > never during runtime, as thi
On 16 July 2015 at 12:34, Christoffer Dall wrote:
> Some registers like the CNTVCT register should only be written to the
> kernel as part of machine initialization or on vmload operations, but
> never during runtime, as this can potentially make time go backwards or
> create inconsistent time obs
Some registers like the CNTVCT register should only be written to the
kernel as part of machine initialization or on vmload operations, but
never during runtime, as this can potentially make time go backwards or
create inconsistent time observations between VCPUs.
Introduce a list of registers tha
