This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Some (small) c++ compilation profiling data (oprofile)
- From: Andi Kleen <ak at suse dot de>
- To: Will Cohen <wcohen at redhat dot com>
- Cc: Andi Kleen <ak at suse dot de>, gcc at gcc dot gnu dot org
- Date: Fri, 17 May 2002 23:40:01 +0200
- Subject: Re: Some (small) c++ compilation profiling data (oprofile)
- References: <Pine.LNX.4.43.0205171925370.8523-100000@thinkpad.objectsecurity.cz.suse.lists.egcs> <3CE54609.8050006@redhat.com.suse.lists.egcs> <p737km2zdn0.fsf@oldwotan.suse.de> <3CE576DD.5060701@redhat.com>
On Fri, May 17, 2002 at 05:32:13PM -0400, Will Cohen wrote:
> The APIC may not be in the mobile Pentium III processor, but somewhere
> in the supporting chipset used on the Dell Inspiron 4100 there is an
> APIC. The /var/log/messages has entries indicating it is finding APIC
> and the profiling I am doing is definitely using the Pentium III
> performance monitoring hardware, not the RTC based sampling.
That's the global APIC. Local APIC is a different thing.
But when it works then it is ok of course.
You can check if you have a local one by looking at /proc/cpuinfo
for apic in the flags line. Normally p3-mobile doesn't have one and
oprofile may know this.
-Andi