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] Is this a bug of xentrace?

To: Hui Kang <hkang@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Is this a bug of xentrace?
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Date: Mon, 11 May 2009 18:55:08 +0100
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 11 May 2009 10:55:57 -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:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=IXq38lRF5MT68VctBfs1djYmCdrUCOUqe+pR3B7uKa4=; b=pNTXooK1hoHnID2WIkgjWY2YiCH2luECeoXSTU25MZuhQt8pH9BLPKQoGVEILW59CI gG1HUqW+DJjVOCydwrH5OZ3WS39q27QWphT1iyP3kdS+5e5KuofW95BrYLehf7OIUZuB GXyh2b4S/2HcQL5Zx0Y4WpbMnwBaBdQTMt5FY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=fEX0BX9wp2qNuYy5mGK1Cd/Y1WFp0gIvu4X5oIgERwRIiJgjTm10bqLD4gcMkrUHCK HGStshplCi2UROErMbCxRHj846SiAfdq6WU1DEMi2rPk/wQnz2pIYFdC7vfivIbwLykS EnBhcDgE5Wwn0WGinis8PmTDNJOvsEcmMorag=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A085651.2020804@xxxxxxxxxxxxx>
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>
References: <4A05D1EF.2090405@xxxxxxxxxxxxx> <de76405a0905110142r5907dd23kfa82ecf359a8b7cc@xxxxxxxxxxxxxx> <4A085352.7010201@xxxxxxxxxxxxx> <4A085651.2020804@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Perhaps because it's not being scheduled out?  If it never blocks, and
there's no one else who wants that cpu, there's no reason not to just
leave it running.

If you make another idle VM, and pin it and the spinning domain to the
same cpu, you'll probably see them both show up, as the idle VM is
scheduled to handle timers and such.

 -George

On Mon, May 11, 2009 at 5:46 PM, Hui Kang <hkang@xxxxxxxxxxxxx> wrote:
> Ok, I know that 0x00007fff is for the idle domain, because when I use xenmon
> it has the same idle domain. However, I have one guest domain running an
> infinite loop program (while{ int temp = 676*1.5;}). This guest domain is
> listed by "xm list". But xenmon and xentrace can not detect this guest
> domain.
> However, when I stop the program in that domain, xentrace and xenmon can
> detect it. Why?
> Thanks.
>
> - Hui
>
> Hui Kang wrote:
>>
>> Yes, it is 0x00007fff. This is one line  in the parsed trace file.
>> CPU1  962569711226060 (+     574)  switch_infnext    [ new_domid =
>> 0x00007fff, time = 14321, r_time =30000000 ]
>> When I use "xm list", it shows the domain id is 5. There are only two
>> domains on the host.
>> Can any one point out what does "0x00007fff" this number mean? Thanks.
>>
>> - Hui
>>
>> George Dunlap wrote:
>>>
>>> Are you sure that's not 0x7fff? (Three f's, not four?)  0x7fff is the
>>> domain ID of the idle domain (scheduled when there is no other work on
>>> the system to do).
>>>
>>>  -George
>>>
>>> On Sat, May 9, 2009 at 7:56 PM, Hui Kang <hkang@xxxxxxxxxxxxx> wrote:
>>>
>>>>
>>>> Hi,
>>>> I am using xentrace to trace the events of guest domains on a host
>>>> physical
>>>> machine.  In the parsed trace file,
>>>> if the guest domain is created on the host machine, then the entry is
>>>> good
>>>> switch_infprev    [ old_domid = 0x00000002
>>>> // the guest domain has a id of 2.
>>>> switch_infnext    [ new_domid = 0x00000000
>>>>
>>>> However, if the guest domain is migrated from another host machine,  the
>>>> parsed trace file shows
>>>> switch_infprev    [ old_domid = 0x00007ffff
>>>> // the guest domain has a id of 2.
>>>> switch_infnext    [ new_domid = 0x00000000
>>>> Even the domain Id is 2, it shows 0x00007ffff.
>>>> Can anyone explain this? Thanks.
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>>> http://lists.xensource.com/xen-devel
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-devel
>>>
>>>
>>> .
>>>
>>>
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>>
>> .
>>
>
>

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

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