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

Re: [Xen-devel] /proc/interrupts on unprivileged domains

To: Diwaker Gupta <diwakergupta@xxxxxxxxx>
Subject: Re: [Xen-devel] /proc/interrupts on unprivileged domains
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 15 Dec 2004 23:21:05 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 15 Dec 2004 23:22:23 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: Your message of "Wed, 15 Dec 2004 15:12:29 PST." <1b0b455704121515123da3c940@xxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> Hi everyone,
> 
> I'm trying to understand the values in /proc/interrupts of
> unprivileged domains. Specifically, I'm interested in the value of the
> timer interrupt. AFAIK, this value reflects the number of times this
> domain received the timer interrupt from Xen? Equivalently, the number
> of times the timer_interrupt() function (and thus the
> do_timer_interrupt) function of the guest OS (linux, in this case)
> were called? Please correct me if I'm wrong.

All correct.

> If that is indeed the case, then my real curiosity is this -- what
> parameters affect this number? Again, AFAIK Xen gives a timer
> interrupt periodically to a currently running domain, and also when a
> domain gets scheduled.

Xen gives a domain an interrupt every 10ms while it runs, and every
time the domain is rescheduled. It also gives an interrupt whenever
the domain's prgrammable one-shot timer expires (used by Linux to set
an appropriate  timeout whenever it blocks).

> But how does this indirectly depend on other
> parameters -- like the cpu frequency, the system time, the tsc
> timestamp value and so on.

It doesn't. :-)

 -- Keir


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

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