[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] xenoprof on linux pvops


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
  • From: Dulloor <dulloor@xxxxxxxxx>
  • Date: Mon, 29 Jun 2009 19:10:14 -0400
  • Cc:
  • Delivery-date: Mon, 29 Jun 2009 16:10:46 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=kEs3xL+0AZeg+APF+BOrji2LfjAPyqKwYfywCbpqLq1/Y8rIRNKyyxNCv8dOU8trtC agdVUMvUpUbD1dyMz0JKeMd6fzNn6PPEDPT0p8Vrk75xPFDfLsagdCffpwys4luJTy/x SO5ITQLHbst7jpELEkef2D3nMLwxZkh57lgj4=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.