All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Naresh Rapolu <nrapolu@purdue.edu>
Cc: xen-devel@lists.xensource.com,
	Stephen Spector <stephen.spector@citrix.com>
Subject: Re: boot_cpu_data differs between Xen hypervisor boot and normal pv_ops kernel boot
Date: Wed, 31 Mar 2010 11:14:10 -0700	[thread overview]
Message-ID: <4BB390F2.8080206@goop.org> (raw)
In-Reply-To: <4BB36A40.1080903@purdue.edu>

On 03/31/2010 08:29 AM, Naresh Rapolu wrote:
>
> When I looked into the source code,  
> arch/x86/kernel/cpu/perf_event.c,   at run-time boot_cpu_data  
> structure seems to differ  in these two forms of booting.
> Due to this, Iam not able to use the hardware performance counters in  
> my Xeon 5530 processor  as  hardware events(cache-misses etc) are 
> being disabled.
>
> Is there any reason for this ?

The PMU hardware features are not virtualized, and are not available to 
guest domains.  I don't think Xen has much of a useful API to expose 
these features, though oprofile was working at one point.

I agree it would be very useful to work out how to get good "perf" 
support in a Xen domain.

(Stephen: It might be an interesting SoC project.)

     J

      parent reply	other threads:[~2010-03-31 18:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31 15:29 boot_cpu_data differs between Xen hypervisor boot and normal pv_ops kernel boot Naresh Rapolu
2010-03-31 15:43 ` Pasi Kärkkäinen
2010-03-31 17:51   ` Naresh Rapolu
2010-03-31 18:14 ` Jeremy Fitzhardinge [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BB390F2.8080206@goop.org \
    --to=jeremy@goop.org \
    --cc=nrapolu@purdue.edu \
    --cc=stephen.spector@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.