On Mon, Feb 29, 2016 at 08:21:39PM +, Mark Cave-Ayland wrote:
> On 29/02/16 03:57, David Gibson wrote:
>
> > On Fri, Feb 26, 2016 at 12:29:51PM +, Mark Cave-Ayland wrote:
> >> On 26/02/16 04:35, David Gibson wrote:
> >>
> Sign. And let me try that again, this time after caffeine:
> >>
On 29/02/16 03:57, David Gibson wrote:
> On Fri, Feb 26, 2016 at 12:29:51PM +, Mark Cave-Ayland wrote:
>> On 26/02/16 04:35, David Gibson wrote:
>>
Sign. And let me try that again, this time after caffeine:
cpu_start/resume():
cpu->tb_env->tb_offset =
muldi
On Fri, Feb 26, 2016 at 12:29:51PM +, Mark Cave-Ayland wrote:
> On 26/02/16 04:35, David Gibson wrote:
>
> >> Sign. And let me try that again, this time after caffeine:
> >>
> >> cpu_start/resume():
> >> cpu->tb_env->tb_offset =
> >> muldiv64(qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL),
On 26/02/16 04:35, David Gibson wrote:
>> Sign. And let me try that again, this time after caffeine:
>>
>> cpu_start/resume():
>> cpu->tb_env->tb_offset =
>> muldiv64(qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL),
>> cpu->tb_env->tb_freq, NANOSECONDS_PER_SECOND) +
>>
On Thu, Feb 25, 2016 at 09:50:20AM +, Mark Cave-Ayland wrote:
> On 25/02/16 05:00, Mark Cave-Ayland wrote:
>
> > On 25/02/16 04:33, Mark Cave-Ayland wrote:
> >
> >> cpu_start/resume():
> >> cpu->tb_env->tb_offset =
> >> qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL) * tb_env->tb_freq +
> >
On 25/02/16 05:00, Mark Cave-Ayland wrote:
> On 25/02/16 04:33, Mark Cave-Ayland wrote:
>
>> cpu_start/resume():
>> cpu->tb_env->tb_offset =
>> qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL) * tb_env->tb_freq +
>> cpu->tb_env->tb_offset -
>> qemu_clock_get_ns(QEMU_CLOCK_HOS
On 25/02/16 04:33, Mark Cave-Ayland wrote:
> cpu_start/resume():
> cpu->tb_env->tb_offset =
> qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL) * tb_env->tb_freq +
> cpu->tb_env->tb_offset -
> qemu_clock_get_ns(QEMU_CLOCK_HOST)
Actually just realised this is slightly wrong and
On Mon, Jan 25, 2016 at 06:20:21PM +0100, BALATON Zoltan wrote:
> On Mon, 25 Jan 2016, David Gibson wrote:
> >Remember, we only ever compute the guest timebase value at the moment
> >the guest requests it - actually maintaining a current timebase value
> >makes sense in hardware, but would be nuts
On Mon, 25 Jan 2016, David Gibson wrote:
Remember, we only ever compute the guest timebase value at the moment
the guest requests it - actually maintaining a current timebase value
makes sense in hardware, but would be nuts in software.
The timebase is a function of real, wall-clock time, and th
