WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] late lapic timer interrupts for hvm guest

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] late lapic timer interrupts for hvm guest
From: Juergen Gross <juergen.gross@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 28 Oct 2008 08:45:53 +0100
Delivery-date: Tue, 28 Oct 2008 00:46:18 -0700
Domainkey-signature: s=s768; d=fujitsu-siemens.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Message-ID:Date:From:Organization: User-Agent:MIME-Version:To:Subject:Content-Type: Content-Transfer-Encoding; b=HeW9onTxSAj4nVNOOGI9eKGEY3ociD+9XJhlECJXrrz10EIdyMWDRrbU uf4J/imGrIh+0EnP/mcAlBYms6tLLfH4tpoHXAscCNxF8qBlrqiuD4/CN swZYQCccoJuVQAG;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Fujitsu Siemens Computers
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724)
Hi,

When using lapic as timer source the hypervisor delivers timer interrupts
late.
In the source xen/arch/x86/hvm/vpt.c function create_periodic_time creates a
timer element with a "bonus" of 50% of the desired time until the interrupt:

    pt->scheduled = NOW() + period;
    /*
     * Offset LAPIC ticks from other timer ticks. Otherwise guests which use
     * LAPIC ticks for process accounting can see long sequences of process
     * ticks incorrectly accounted to interrupt processing.
     */
    if ( pt->source == PTSRC_lapic )
        pt->scheduled += period >> 1;

We have ported our mainframe OS BS2000 to x86_64/XEN and we are using the
lapic timer as the main timer interrupt source (one shot mode). Finally I've
found the above coding which seems to be the root cause of late interrupts.

I think the problem mentioned in the comment won't occur if the guest uses
the lapic timer in one shot mode with varying timer values (like BS2000). Or
am I wrong here?

Juergen

--
Juergen Gross                             Principal Developer
IP SW OS6                      Telephone: +49 (0) 89 636 47950
Fujitsu Siemens Computers         e-mail: juergen.gross@xxxxxxxxxxxxxxxxxxx
Otto-Hahn-Ring 6                Internet: www.fujitsu-siemens.com
D-81739 Muenchen         Company details: www.fujitsu-siemens.com/imprint.html

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

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