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

Re: [Xen-devel] Re: xenoprof on linux pvops


  • To: "Langsdorf, Mark" <mark.langsdorf@xxxxxxx>
  • From: Dulloor <dulloor@xxxxxxxxx>
  • Date: Thu, 2 Jul 2009 00:38:24 -0700
  • Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "<xen-devel@xxxxxxxxxxxxxxxxxxx>" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 02 Jul 2009 00:39:07 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:x-mailer:mime-version:subject:date:cc; b=Wf5n6WMJGUXsH4xKEfxFp3zNfv+EfqPpPxv1TOidh7fusyLtP01CVII6dxtcg5Fh7l eYQx34AzhfhIbC60hSbGXkpPuY/LjUqLhMz6WV3LuW/Fw243tU6bkicIkUa/Ouc30o1K 1WXzV9TBLzM8rltprpjMqwFNRWpE1yL5cFGUA=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I have tested on multiple Intel platforms. I didn't see this issue. I don't have an AMD.

Jeremy, I am away this week. I will give you access to my git repo by mid next week.

-dulloor

On Jul 1, 2009, at 9:46 AM, "Langsdorf, Mark" <mark.langsdorf@xxxxxxx> wrote:

On 06/29/09 16:10, Dulloor wrote:
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 ?

On my AMD system, I'm seeing warning from xen_apic_write
coming from perf_counters_lapic_init().  Do your patches
resolve the issue?

-Mark Langsdorf
Operating System Research Center
AMD


_______________________________________________
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®.