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] xenoprof on linux pvops

To: 'Dulloor' <dulloor@xxxxxxxxx>, "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>, 'Jeremy Fitzhardinge' <jeremy@xxxxxxxx>
Subject: RE: [Xen-devel] xenoprof on linux pvops
From: "Han, Weidong" <weidong.han@xxxxxxxxx>
Date: Tue, 30 Jun 2009 14:31:16 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc:
Delivery-date: Mon, 29 Jun 2009 23:34:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <940bcfd20906291610u68e61258t55b7da72267dcdab@xxxxxxxxxxxxxx>
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: <940bcfd20906291610u68e61258t55b7da72267dcdab@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acn5DxlJSQeIddcWRbeBX9iE+zm6XgAPGGBA
Thread-topic: [Xen-devel] xenoprof on linux pvops
Hi Dulloor,
 
Which commit of jeremy's pv-ops tree and changeset of Xen unstable are you using for your porting? pv-ops dom0 cannot boot for me. You can find information in another thread "Xen cannot boot with pvops dom0".
 
Regards,
Weidong
 


From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Dulloor
Sent: 2009年6月30日 7:10
To: xen-devel@xxxxxxxxxxxxxxxxxxx; Jeremy Fitzhardinge
Subject: [Xen-devel] xenoprof on linux pvops

I have ported xenoprof to linux-pvops.

- All the changes/clean-ups are limited to linux modules (except a xen interface for kernel space mappings).
- Calls are switched to xen by checking for xen_initial_domain. Is there a better way of handling such modules with pvops ?

- What is the best way to go about checking in this code ? Do I submit all the patches to jeremy's tree (cause these changes wouldn't make sense anyway without privileged domain support) ?

-dulloor
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>