This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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

To: Sebastian Plagemann <sebastian.plagemann@xxxxxx>, xen-users List <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Debian + XEN 3.2. + Windows VM || ping problems
From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Date: Tue, 7 Apr 2009 15:37:36 +0100
Delivery-date: Tue, 07 Apr 2009 07:38:22 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=VCNwoRze1wC268o08uxCfYXBI2xIn2zzhbss+cZ2mxc=; b=thIyQOWpeCXPBjsEXdPiF9Z4prLJVVAgqETfix8peeMyLxJnXuOV5vROy7Mn6Z2DI4 ap8LaIFJlf8pKg8qUidzQoUEoFJpWNRyzsE4CiXa6XBDlBnYlm4EutX+HXXCVH4YRCDr MzW0wJaIBkmlx1Fh2w1vqeoA/IBVDLg/ZThAQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=UShY4zueUW0hEqV/OHba/SRJhw5cnyqpl4RzyEeCrAeDEbPGJ/ZrfW5jr3PeKgJ7CX P+MbTG2Uc/ANeBEWQhapt2WbHWSQLZ6RbWjRNFcncbQcelbtGgv5Y6N+c/fWXfy2yTSW s7pWccRlxJCDpOPey+KIMJ8o4dhUeZ9UI9RfM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <f4527be0904070728u35916219j43ab0a6406cdcb4@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <49DB36FE.5040802@xxxxxx> <f4527be0904070610u727fdb89nea8dba6d79c3c8bc@xxxxxxxxxxxxxx> <49DB5704.20507@xxxxxx> <f4527be0904070728u35916219j43ab0a6406cdcb4@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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.


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>