* Peter Maydell (peter.mayd...@linaro.org) wrote:
> On Fri, 5 Jul 2019 at 11:13, Paolo Bonzini wrote:
> >
> > On 05/07/19 11:58, Peter Maydell wrote:
> > > On Fri, 5 Jul 2019 at 10:48, Paolo Bonzini wrote:
> > >> You're right, the compatibility causes wrong behavior for the default
> > >> -rtc se
On Fri, 5 Jul 2019 at 10:48, Paolo Bonzini wrote:
> You're right, the compatibility causes wrong behavior for the default
> -rtc settings (the RC pauses across migration). The right thing to do
> would be to store the base rather than the offset: that is, you store
> the time at which LR was writ
On Fri, 5 Jul 2019 at 11:32, Paolo Bonzini wrote:
>
> On 05/07/19 12:21, Peter Maydell wrote:
> > On Fri, 5 Jul 2019 at 11:13, Paolo Bonzini wrote:
> >> Yes, something like that but I would just bump the version. Version 1
> >> has the old meaning for the first field, version 2 has the new meani
On 05/07/19 12:21, Peter Maydell wrote:
> On Fri, 5 Jul 2019 at 11:13, Paolo Bonzini wrote:
>>
>> On 05/07/19 11:58, Peter Maydell wrote:
>>> On Fri, 5 Jul 2019 at 10:48, Paolo Bonzini wrote:
You're right, the compatibility causes wrong behavior for the default
-rtc settings (the RC pau
On Fri, 5 Jul 2019 at 10:48, Paolo Bonzini wrote:
> By the way, the data sheet says "the counter and match values are
> compared in a comparator. When both values are equal, the RTCINTR
> interrupt is asserted HIGH"; QEMU compares the RTC value (read from
> RTC_DR) and not the counter value, but L
On Fri, 5 Jul 2019 at 11:13, Paolo Bonzini wrote:
>
> On 05/07/19 11:58, Peter Maydell wrote:
> > On Fri, 5 Jul 2019 at 10:48, Paolo Bonzini wrote:
> >> You're right, the compatibility causes wrong behavior for the default
> >> -rtc settings (the RC pauses across migration). The right thing to d
On 05/07/19 11:58, Peter Maydell wrote:
> On Fri, 5 Jul 2019 at 10:48, Paolo Bonzini wrote:
>> You're right, the compatibility causes wrong behavior for the default
>> -rtc settings (the RC pauses across migration). The right thing to do
>> would be to store the base rather than the offset: that
On Fri, 5 Jul 2019 at 10:48, Paolo Bonzini wrote:
> You're right, the compatibility causes wrong behavior for the default
> -rtc settings (the RC pauses across migration). The right thing to do
> would be to store the base rather than the offset: that is, you store
> the time at which LR was writ
On 04/07/19 18:02, Peter Maydell wrote:
> I've had a report that the way the PL031 model handles time
> across a vm save/reload fails to correctly advance the guest
> RTC when the host RTC has advanced between the save and reload.
> I looked at the code and my correspondent's analysis (which
> I qu
I've had a report that the way the PL031 model handles time
across a vm save/reload fails to correctly advance the guest
RTC when the host RTC has advanced between the save and reload.
I looked at the code and my correspondent's analysis (which
I quote below, lightly edited) looks correct to me, bu
10 matches
Mail list logo
