Re: [Xen-users] Debian + XEN 3.2. + Windows VM || ping problems

[Andrew Lyon <andrew.lyon@xxxxxxxxx>]

On Tue, Apr 7, 2009 at 3:28 PM, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:
> On Tue, Apr 7, 2009 at 2:37 PM, Sebastian Plagemann
> <sebastian.plagemann@xxxxxx> wrote:
>> Hi,
>> just one question: what does this timer_mode do?
>>
>> Thanks
>> Sebastian
>
> Details of the bug you hit can be found at
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=895 , but I've
> never found a description of what the difference is between the
> available timer modes, I just use mode 1 for windows hvm's.
>
> Andy
>

I just found this explanation:

Timer_mode 0/1 track exact number of timer interrupt which need be
injected to guest. If timer interrupts cannot be injected on time,
pending_count++. The difference is that for mode 0, guest TSC is also
hold back if there are timer interrupts pending, while for mode 1 guest
TSC always equals to (host TSC - constant offset)

Time mode 2/3 don't inject each pending time interrupt to guest, hoping
guest OS itself can handle time interrupt lost and adjust time using
platform timer (e.g. HPET)'s counter.

Andy

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users