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] Re: [Xen-users] About profiling xen

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-users] About profiling xen
From: Marco Tizzoni <marco.tizzoni@xxxxxxxxx>
Date: Thu, 1 Oct 2009 23:55:35 +0200
Cc: "Fajar A." <fajar@xxxxxxxxx>, Fasiha Ashraf <feehapk@xxxxxxxxxxx>, xen <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 01 Oct 2009 14:56:38 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type:content-transfer-encoding; bh=tGIJ8eZ0q/SKMkwDCVQbHUwjq/sXBw5RE0/lLTMak7Y=; b=o4TJWepHvIT86es8Iv0k9fjNh+Fhe+ai/ofIf74McFtJq/oUI5AKkmWRmWCmZpfry9 pJQQs8Z5gtEvs8LmA68IYHpmKXllXOjEB2DJwfgo9i6tIyf0K1Bi11t4F3A8wleP+pET 1uGEJPzYn0tCzltywPnTLigAbcSLnS8YCENcY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=jVmVjWPBWv33tfBh2RmvbqpyBzLF6ZEPUofav/U5nykltMsYSsc7VJhUKTe1SK9jox 4kl1axHZB8NsAQXXuW6xP4AcBRRXDqY2u+tV9mguaSsouFOPwRDJVcCmmNVWGsmFRQue 2F9qxyfU0kIEjHeIPBFka18g5ay3mSl+KcTVA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AC521DC.2020106@xxxxxxxx>
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: <196324.1267.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <f9611b0f0909300045o55e22378xea270e9873471f1d@xxxxxxxxxxxxxx> <f9611b0f0909300206v53577d1cw300ff6092b8ffede@xxxxxxxxxxxxxx> <4AC3E889.6060407@xxxxxxxx> <f9611b0f0910010035m40949fb3o5efe60469b4466b7@xxxxxxxxxxxxxx> <4AC516EC.3050704@xxxxxxxx> <f9611b0f0910011405h416d2372i3a4c7587b84a3fac@xxxxxxxxxxxxxx> <4AC51C48.40203@xxxxxxxx> <f9611b0f0910011426w4af0b164re00104fb5a66ebd9@xxxxxxxxxxxxxx> <4AC521DC.2020106@xxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Oct 1, 2009 at 11:40 PM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> On 10/01/09 14:26, Marco Tizzoni wrote:
>>> OK, good, that takes timers out of the equation.
>>>
>>> I guess the problem is the rate at which Xen will context switch between
>>> two domains.  Hm.
>>>
>>> Does anything change if you pin your domains to different cpus?
>>>
>> mmmh, no. I think without a finer timer the problem could not be solved.
>>
>
> Why's that?  You said that the timers "work as expected", which I read
> to mean that they will generate sub-millisecond events.  Did I
> misunderstand you?

Sorry, I was not clear. It works as I expect, i.e going not over 1000
hz (my dom0 kernel has been compiled with 1000hz).
Following a couple of run of your testtimer:

hal9k-dom0 ~ # ./testtimer .000001 |head -n10
1000 iterations at  0.000001 sec
0.000662
0.000946
0.000956
0.000960
0.000962
0.000956
0.000964
0.000963
0.000964
0.000964

hal9k-dom0 ~ # ./testtimer .00001 |head -n10
1000 iterations at  0.000010 sec
0.000407
0.000942
0.000941
0.000954
0.000956
0.000954
0.000955
0.000932
0.000955
0.000955

Hoping this clarify.

m-

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