<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=Content-Type content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<title>Stefan email sig</title>
<style>
<!--
 /* Font Definitions */
 @font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Verdana;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:black;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.apple-style-span
        {mso-style-name:apple-style-span;}
span.E-MailFormatvorlage18
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#002060;}
p.parstyle, li.parstyle, div.parstyle
        {mso-style-name:parstyle;
        margin:0cm;
        margin-bottom:.0001pt;
        line-height:10.2pt;
        font-size:9.0pt;
        font-family:"Verdana","sans-serif";
        color:black;}
p.stress, li.stress, div.stress
        {mso-style-name:stress;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        mso-line-height-alt:10.85pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:#2E4096;
        font-weight:bold;}
p.nostress, li.nostress, div.nostress
        {mso-style-name:nostress;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:#777574;}
p.highlight, li.highlight, div.highlight
        {mso-style-name:highlight;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:#2E4096;
        font-weight:bold;}
span.parstyle1
        {mso-style-name:parstyle1;
        font-family:"Verdana","sans-serif";
        letter-spacing:0pt;
        font-weight:normal;
        font-style:normal;}
span.stress1
        {mso-style-name:stress1;
        color:#2E4096;
        font-weight:bold;}
span.nostress1
        {mso-style-name:nostress1;
        color:#777574;}
span.highlight1
        {mso-style-name:highlight1;
        color:#2E4096;
        font-weight:bold;}
span.E-MailFormatvorlage27
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#002060;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page Section1
        {size:612.0pt 792.0pt;
        margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=white lang=DE link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#002060'>XScale is not a x86/IA32 architecture.<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#002060'>On a system running OKL4 you cannot access any BIOS functions, because
they are all real mode implementations while OKL4 is running in protected mode.<o:p></o:p></span></p>

<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#002060'><o:p>&nbsp;</o:p></span></p>

<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#002060'>Frank<o:p></o:p></span></p>

<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'>

<div>

<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>

<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext'> developer-bounces@okl4.org
[mailto:developer-bounces@okl4.org] <b>On Behalf Of </b>Stefan M. Petters<br>
<b>Sent:</b> Thursday, January 07, 2010 10:58 AM<br>
<b>To:</b> Frank Kaiser<br>
<b>Cc:</b> Peter Nguyen; developer<br>
<b>Subject:</b> Re: [okl4-developer] PMCs<o:p></o:p></span></p>

</div>

</div>

<p class=MsoNormal><o:p>&nbsp;</o:p></p>

<p class=MsoNormal>Hi,<br>
<br>
Frank Kaiser wrote: <o:p></o:p></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#002060'>Hello</span><o:p></o:p></p>

<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#002060'>&nbsp;</span><o:p></o:p></p>

<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#002060'>Most of modern x86 processors provide the TSC for performance
monitoring. According to what I remember from INTEL’s x86 architecture
documentation it is guaranteed that the TSC will not overflow within 10 years.
This is far beyond a system’s uninterrupted operating time, therefore I see no
reason for an overflow interrupt etc.</span><o:p></o:p></p>

<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#002060'>The common approach is to read and store the TSC at a tracepoint
and calculate time differences between associated tracepoints. The main
difficulty is to determine the absolute timebase, because this is highly
dependent on the specific CPU and chipset in use, and on the system’s clocking.</span><o:p></o:p></p>

<p class=MsoNormal>TSCs count CPU core clock cycles. So it becomes somewhat
iffy when you start frequency scaling. On some XScale processors you have the
option of saving power by gating the core clock. IIRC that means also the TSC
will be halted.<br>
Unless you do the energy saving thing, it becomes pretty trivial to find out
the core CPU frequency.<br>
Under Linux <br>
cat /proc/cpuinfo<br>
will tell you&nbsp; and BIOS usually also does.<br>
On Windows you can look up the System info.<br>
<br>
Regards,<br>
&nbsp;&nbsp;&nbsp; Stefan.<o:p></o:p></p>

<div>

<p class=MsoNormal>-- <o:p></o:p></p>

<div>

<p class=MsoNormal><span class=stress1><span style='font-size:9.0pt;font-family:
"Verdana","sans-serif"'>Stefan M. Petters</span></span><span style='font-size:
9.0pt;font-family:"Verdana","sans-serif"'><br>
</span><span class=nostress1><span style='font-size:9.0pt;font-family:"Verdana","sans-serif"'>CISTER
Research Unit</span></span><span style='font-size:9.0pt;font-family:"Verdana","sans-serif"'><br>
<span class=parstyle1>&nbsp;</span><br>
</span><span class=highlight1><span style='font-size:9.0pt;font-family:"Verdana","sans-serif"'>ISEP
- IPP</span></span><span class=parstyle1><span style='font-size:9.0pt'> | Rua
Dr. António Bernardino de Almeida 431</span></span><span style='font-size:9.0pt;
font-family:"Verdana","sans-serif"'><br>
<span class=parstyle1>4200-072 Porto | Portugal </span><br>
<span class=parstyle1>T +351 22 83 40 529 | <a
href="http://www.cister.isep.ipp.pt/people/stefan+m%2E+petters">Homepage</a> </span></span><o:p></o:p></p>

</div>

</div>

</div>

</div>

</body>

</html>