<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: linux cpu id in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670829#M67128</link>
    <description>&lt;A href="http://softwareforums.intel.com/ids/board/message?board.id=42&amp;amp;message.id=782" target="_blank"&gt;http://softwareforums.intel.com/ids/board/message?board.id=42&amp;amp;message.id=782&lt;/A&gt;</description>
    <pubDate>Mon, 14 Nov 2005 05:40:40 GMT</pubDate>
    <dc:creator>Muthukumar_5</dc:creator>
    <dc:date>2005-11-14T05:40:40Z</dc:date>
    <item>
      <title>linux cpu id</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670828#M67127</link>
      <description>I am wondering why on a HP Proliant DL 140 with two Xeon cpu when HT is disabled the cat /proc/cpuinfo displays the two cpu with the same physical ID 0&lt;BR /&gt;&lt;BR /&gt;As the two cpu are physical (not logical HT is disabled) the cpu physical ID should be different (e.g 0 and 6)&lt;BR /&gt;&lt;BR /&gt;In my case DL 140 running redhat EL 3 with smp kernel 2.4.21.37 the ID are identical</description>
      <pubDate>Mon, 14 Nov 2005 04:55:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670828#M67127</guid>
      <dc:creator>Carrez_1</dc:creator>
      <dc:date>2005-11-14T04:55:25Z</dc:date>
    </item>
    <item>
      <title>Re: linux cpu id</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670829#M67128</link>
      <description>&lt;A href="http://softwareforums.intel.com/ids/board/message?board.id=42&amp;amp;message.id=782" target="_blank"&gt;http://softwareforums.intel.com/ids/board/message?board.id=42&amp;amp;message.id=782&lt;/A&gt;</description>
      <pubDate>Mon, 14 Nov 2005 05:40:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670829#M67128</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2005-11-14T05:40:40Z</dc:date>
    </item>
    <item>
      <title>Re: linux cpu id</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670830#M67129</link>
      <description>same type of cpuinfo informations are with this posting.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://lists.rlug.org/pipermail/rlug/2004-December/003237.html" target="_blank"&gt;http://lists.rlug.org/pipermail/rlug/2004-December/003237.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;hth.</description>
      <pubDate>Mon, 14 Nov 2005 05:42:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670830#M67129</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2005-11-14T05:42:05Z</dc:date>
    </item>
    <item>
      <title>Re: linux cpu id</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670831#M67130</link>
      <description>Check out the following Intel document: "Detecting Support for Hyper-Threading".&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.intel.com/cd/ids/developer/asmo-na/eng/dc/threading/knowledgebase/20416.htm?page=1" target="_blank"&gt;http://www.intel.com/cd/ids/developer/asmo-na/eng/dc/threading/knowledgebase/20416.htm?page=1&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Seems that on dual processors host all processors return same CPUID.&lt;BR /&gt;&lt;BR /&gt;The only difference between CPU is a serial number but cpuinfo does not return this info.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sergejs</description>
      <pubDate>Mon, 14 Nov 2005 05:44:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670831#M67130</guid>
      <dc:creator>Sergejs Svitnevs</dc:creator>
      <dc:date>2005-11-14T05:44:24Z</dc:date>
    </item>
    <item>
      <title>Re: linux cpu id</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670832#M67131</link>
      <description>CPUID are identical in case of logical cpu when HT is enabled and in that case the sibling is equal to 2 with a sibling map.&lt;BR /&gt;&lt;BR /&gt;But when HT is disabled, sibling is equal to 1 and I don't see why the cpuid should be equal as the two cpu are distinct and physical, the cpuid (returned by /proc/cpuinfo) should be different at least it works like this and the two physical cpu are different on a dell server with two Xeon processor and the same linux kernel.&lt;BR /&gt;&lt;BR /&gt;Now, I can add that I check the serial number ID using the linux command dmidecode and this command returns the two processor but with the same ID ie 29 0F 00 00 FF FB EB BF&lt;BR /&gt;&lt;BR /&gt;strange isn't it?&lt;BR /&gt;&lt;BR /&gt;same cpuid and same ID using dmidecode for two physical processor</description>
      <pubDate>Mon, 14 Nov 2005 06:38:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670832#M67131</guid>
      <dc:creator>Carrez_1</dc:creator>
      <dc:date>2005-11-14T06:38:25Z</dc:date>
    </item>
    <item>
      <title>Re: linux cpu id</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670833#M67132</link>
      <description>I highly recommend you to upgrade your bios-System ROM.&lt;BR /&gt;&lt;BR /&gt;You can get new software at:&lt;BR /&gt;&lt;A href="http://h18004.www1.hp.com/support/files/server/us/locate/101_5616.html" target="_blank"&gt;http://h18004.www1.hp.com/support/files/server/us/locate/101_5616.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sergejs</description>
      <pubDate>Mon, 14 Nov 2005 06:55:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670833#M67132</guid>
      <dc:creator>Sergejs Svitnevs</dc:creator>
      <dc:date>2005-11-14T06:55:28Z</dc:date>
    </item>
    <item>
      <title>Re: linux cpu id</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670834#M67133</link>
      <description>But I have already an BIOS up to date for the server DL140&lt;BR /&gt;&lt;BR /&gt;I load the BIOS upgrade from &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h18023.www1.hp.com/support/files/server/us/locate/101_5771.html" target="_blank"&gt;http://h18023.www1.hp.com/support/files/server/us/locate/101_5771.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;without any succes in resolve my problem&lt;BR /&gt;&lt;BR /&gt;another point the redhat EL 3 used is certified by HP to run on DL140 server...&lt;BR /&gt;&lt;BR /&gt;So either I can find a solution to check that the two cpu are correctly used (and in that case cpu physical ID should be different) or I am sure that there is a bug from HP maybe in the BIOS?&lt;BR /&gt;&lt;BR /&gt;sample codes find on &lt;A href="http://www.intel.com/cd/ids/developer/asmo-na/eng/dc/threading/knowledgebase/20416.htm?page=1" target="_blank"&gt;http://www.intel.com/cd/ids/developer/asmo-na/eng/dc/threading/knowledgebase/20416.htm?page=1&lt;/A&gt;&lt;BR /&gt;are not very usefull because unfortunatly I can not succeed to make it run and compile under linux&lt;BR /&gt;&lt;BR /&gt;But do someone agree with me when I say that without Hyperthreading two physical cpu should have two different physical id?</description>
      <pubDate>Mon, 14 Nov 2005 07:42:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670834#M67133</guid>
      <dc:creator>Carrez_1</dc:creator>
      <dc:date>2005-11-14T07:42:16Z</dc:date>
    </item>
    <item>
      <title>Re: linux cpu id</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670835#M67134</link>
      <description>I also have DL140 server with Debian 3.1 and HT enabled.&lt;BR /&gt;&lt;BR /&gt;/proc/cpuinfo output shows:&lt;BR /&gt;processor       : 0&lt;BR /&gt;vendor_id       : GenuineIntel&lt;BR /&gt;cpu family      : 15&lt;BR /&gt;model           : 2&lt;BR /&gt;model name      : Intel(R) Xeon(TM) CPU 2.40GHz&lt;BR /&gt;stepping        : 9&lt;BR /&gt;cpu MHz         : 2399.398&lt;BR /&gt;cache size      : 512 KB&lt;BR /&gt;fdiv_bug        : no&lt;BR /&gt;hlt_bug         : no&lt;BR /&gt;f00f_bug        : no&lt;BR /&gt;coma_bug        : no&lt;BR /&gt;fpu             : yes&lt;BR /&gt;fpu_exception   : yes&lt;BR /&gt;cpuid level     : 2&lt;BR /&gt;wp              : yes&lt;BR /&gt;flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht t&lt;BR /&gt;m pbe cid&lt;BR /&gt;bogomips        : 4784.12&lt;BR /&gt;&lt;BR /&gt;processor       : 1&lt;BR /&gt;vendor_id       : GenuineIntel&lt;BR /&gt;cpu family      : 15&lt;BR /&gt;model           : 2&lt;BR /&gt;model name      : Intel(R) Xeon(TM) CPU 2.40GHz&lt;BR /&gt;stepping        : 9&lt;BR /&gt;cpu MHz         : 2399.398&lt;BR /&gt;cache size      : 512 KB&lt;BR /&gt;fdiv_bug        : no&lt;BR /&gt;hlt_bug         : no&lt;BR /&gt;f00f_bug        : no&lt;BR /&gt;coma_bug        : no&lt;BR /&gt;fpu             : yes&lt;BR /&gt;fpu_exception   : yes&lt;BR /&gt;cpuid level     : 2&lt;BR /&gt;wp              : yes&lt;BR /&gt;flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht t&lt;BR /&gt;m pbe cid&lt;BR /&gt;bogomips        : 4797.23&lt;BR /&gt;&lt;BR /&gt;processor       : 2&lt;BR /&gt;vendor_id       : GenuineIntel&lt;BR /&gt;cpu family      : 15&lt;BR /&gt;model           : 2&lt;BR /&gt;model name      : Intel(R) Xeon(TM) CPU 2.40GHz&lt;BR /&gt;stepping        : 9&lt;BR /&gt;cpu MHz         : 2399.398&lt;BR /&gt;cache size      : 512 KB&lt;BR /&gt;fdiv_bug        : no&lt;BR /&gt;hlt_bug         : no&lt;BR /&gt;f00f_bug        : no&lt;BR /&gt;coma_bug        : no&lt;BR /&gt;fpu             : yes&lt;BR /&gt;fpu_exception   : yes&lt;BR /&gt;cpuid level     : 2&lt;BR /&gt;wp              : yes&lt;BR /&gt;flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht t&lt;BR /&gt;m pbe cid&lt;BR /&gt;bogomips        : 4797.23&lt;BR /&gt;&lt;BR /&gt;processor       : 3&lt;BR /&gt;vendor_id       : GenuineIntel&lt;BR /&gt;cpu family      : 15&lt;BR /&gt;model           : 2&lt;BR /&gt;model name      : Intel(R) Xeon(TM) CPU 2.40GHz&lt;BR /&gt;stepping        : 9&lt;BR /&gt;cpu MHz         : 2399.398&lt;BR /&gt;cache size      : 512 KB&lt;BR /&gt;fdiv_bug        : no&lt;BR /&gt;hlt_bug         : no&lt;BR /&gt;f00f_bug        : no&lt;BR /&gt;coma_bug        : no&lt;BR /&gt;fpu             : yes&lt;BR /&gt;fpu_exception   : yes&lt;BR /&gt;cpuid level     : 2&lt;BR /&gt;wp              : yes&lt;BR /&gt;flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht t&lt;BR /&gt;m pbe cid&lt;BR /&gt;bogomips        : 4797.23&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Processor ID 's are different.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sergejs</description>
      <pubDate>Mon, 14 Nov 2005 08:34:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670835#M67134</guid>
      <dc:creator>Sergejs Svitnevs</dc:creator>
      <dc:date>2005-11-14T08:34:11Z</dc:date>
    </item>
    <item>
      <title>Re: linux cpu id</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670836#M67135</link>
      <description>when I talk about processor cpu id I do not mean the number affected to each processor. You have a DL 140 running debian and HT enabled so you get 4 cpu (number 0 to 3) but in fact there is 4 logical cpu. Unfortunatly in your case the command /proc/cpuinfo does not give you access to the cpu physical id may be try dmesg to get the cpu physical id&lt;BR /&gt;&lt;BR /&gt;as a example cat /proc/cpuinfo in my case (with redhat)&lt;BR /&gt;&lt;BR /&gt;processor : 0&lt;BR /&gt;vendor_id : GenuineIntel&lt;BR /&gt;cpu family : 15&lt;BR /&gt;model  : 2&lt;BR /&gt;model name : Intel(R) Xeon(TM) CPU 3.06GHz&lt;BR /&gt;stepping : 9&lt;BR /&gt;cpu MHz  : 3065.913&lt;BR /&gt;cache size : 512 KB&lt;BR /&gt;physical id : 0&lt;BR /&gt;siblings : 1&lt;BR /&gt;runqueue : 0&lt;BR /&gt;fdiv_bug : no&lt;BR /&gt;hlt_bug  : no&lt;BR /&gt;f00f_bug : no&lt;BR /&gt;coma_bug : no&lt;BR /&gt;fpu  : yes&lt;BR /&gt;fpu_exception : yes&lt;BR /&gt;cpuid level : 2&lt;BR /&gt;wp  : yes&lt;BR /&gt;flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm&lt;BR /&gt;bogomips : 6121.06&lt;BR /&gt;&lt;BR /&gt;processor : 1&lt;BR /&gt;vendor_id : GenuineIntel&lt;BR /&gt;cpu family : 15&lt;BR /&gt;model  : 2&lt;BR /&gt;model name : Intel(R) Xeon(TM) CPU 3.06GHz&lt;BR /&gt;stepping : 9&lt;BR /&gt;cpu MHz  : 3065.913&lt;BR /&gt;cache size : 512 KB&lt;BR /&gt;physical id : 0&lt;BR /&gt;siblings : 1&lt;BR /&gt;runqueue : 1&lt;BR /&gt;fdiv_bug : no&lt;BR /&gt;hlt_bug  : no&lt;BR /&gt;f00f_bug : no&lt;BR /&gt;coma_bug : no&lt;BR /&gt;fpu  : yes&lt;BR /&gt;fpu_exception : yes&lt;BR /&gt;cpuid level : 2&lt;BR /&gt;wp  : yes&lt;BR /&gt;flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm&lt;BR /&gt;bogomips : 6121.06&lt;BR /&gt;&lt;BR /&gt;As you can see you can get the physical id of the cpu. And here the problem is that the cpu id are identical for two physical cpu&lt;BR /&gt;&lt;BR /&gt;now on a HT enabled system&lt;BR /&gt;&lt;BR /&gt;processor : 0&lt;BR /&gt;vendor_id : GenuineIntel&lt;BR /&gt;cpu family : 15&lt;BR /&gt;model  : 2&lt;BR /&gt;model name : Intel(R) Xeon(TM) CPU 3.06GHz&lt;BR /&gt;stepping : 9&lt;BR /&gt;cpu MHz  : 3065.930&lt;BR /&gt;cache size : 512 KB&lt;BR /&gt;physical id : 0&lt;BR /&gt;siblings : 2&lt;BR /&gt;runqueue : 0&lt;BR /&gt;fdiv_bug : no&lt;BR /&gt;hlt_bug  : no&lt;BR /&gt;f00f_bug : no&lt;BR /&gt;coma_bug : no&lt;BR /&gt;fpu  : yes&lt;BR /&gt;fpu_exception : yes&lt;BR /&gt;cpuid level : 2&lt;BR /&gt;wp  : yes&lt;BR /&gt;flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm&lt;BR /&gt;bogomips : 6121.06&lt;BR /&gt;&lt;BR /&gt;processor : 1&lt;BR /&gt;vendor_id : GenuineIntel&lt;BR /&gt;cpu family : 15&lt;BR /&gt;model  : 2&lt;BR /&gt;model name : Intel(R) Xeon(TM) CPU 3.06GHz&lt;BR /&gt;stepping : 9&lt;BR /&gt;cpu MHz  : 3065.930&lt;BR /&gt;cache size : 512 KB&lt;BR /&gt;physical id : 0&lt;BR /&gt;siblings : 2&lt;BR /&gt;runqueue : 0&lt;BR /&gt;fdiv_bug : no&lt;BR /&gt;hlt_bug  : no&lt;BR /&gt;f00f_bug : no&lt;BR /&gt;coma_bug : no&lt;BR /&gt;fpu  : yes&lt;BR /&gt;fpu_exception : yes&lt;BR /&gt;cpuid level : 2&lt;BR /&gt;wp  : yes&lt;BR /&gt;flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm&lt;BR /&gt;bogomips : 6121.06&lt;BR /&gt;&lt;BR /&gt;processor : 2&lt;BR /&gt;vendor_id : GenuineIntel&lt;BR /&gt;cpu family : 15&lt;BR /&gt;model  : 2&lt;BR /&gt;model name : Intel(R) Xeon(TM) CPU 3.06GHz&lt;BR /&gt;stepping : 9&lt;BR /&gt;cpu MHz  : 3065.930&lt;BR /&gt;cache size : 512 KB&lt;BR /&gt;physical id : 6&lt;BR /&gt;siblings : 2&lt;BR /&gt;runqueue : 2&lt;BR /&gt;fdiv_bug : no&lt;BR /&gt;hlt_bug  : no&lt;BR /&gt;f00f_bug : no&lt;BR /&gt;coma_bug : no&lt;BR /&gt;fpu  : yes&lt;BR /&gt;fpu_exception : yes&lt;BR /&gt;cpuid level : 2&lt;BR /&gt;wp  : yes&lt;BR /&gt;flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm&lt;BR /&gt;bogomips : 6121.06&lt;BR /&gt;&lt;BR /&gt;processor : 3&lt;BR /&gt;vendor_id : GenuineIntel&lt;BR /&gt;cpu family : 15&lt;BR /&gt;model  : 2&lt;BR /&gt;model name : Intel(R) Xeon(TM) CPU 3.06GHz&lt;BR /&gt;stepping : 9&lt;BR /&gt;cpu MHz  : 3065.930&lt;BR /&gt;cache size : 512 KB&lt;BR /&gt;physical id : 6&lt;BR /&gt;siblings : 2&lt;BR /&gt;runqueue : 2&lt;BR /&gt;fdiv_bug : no&lt;BR /&gt;hlt_bug  : no&lt;BR /&gt;f00f_bug : no&lt;BR /&gt;coma_bug : no&lt;BR /&gt;fpu  : yes&lt;BR /&gt;fpu_exception : yes&lt;BR /&gt;cpuid level : 2&lt;BR /&gt;wp  : yes&lt;BR /&gt;flags  : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm&lt;BR /&gt;bogomips : 6121.06&lt;BR /&gt;&lt;BR /&gt;and two logical cpu share the same physical id&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 14 Nov 2005 09:07:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670836#M67135</guid>
      <dc:creator>Carrez_1</dc:creator>
      <dc:date>2005-11-14T09:07:57Z</dc:date>
    </item>
    <item>
      <title>Re: linux cpu id</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670837#M67136</link>
      <description>Carrez, are you running a normal or SMP kernel when you get these results ?</description>
      <pubDate>Tue, 15 Nov 2005 05:03:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670837#M67136</guid>
      <dc:creator>David Timms</dc:creator>
      <dc:date>2005-11-15T05:03:59Z</dc:date>
    </item>
    <item>
      <title>Re: linux cpu id</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670838#M67137</link>
      <description>I am running a smp kernel 2.4.21-37 but same result with smp kernel 2.4.21-27&lt;BR /&gt;&lt;BR /&gt;In order to get the two proc activated you obviously have to run a smp kernel</description>
      <pubDate>Tue, 15 Nov 2005 06:07:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670838#M67137</guid>
      <dc:creator>Carrez_1</dc:creator>
      <dc:date>2005-11-15T06:07:16Z</dc:date>
    </item>
    <item>
      <title>Re: linux cpu id</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670839#M67138</link>
      <description>What you are seeing is normal on HP systems running Linux.  The physical id field in /proc/cpuinfo file is usually set to zero.  The exception would have this value set to something else.&lt;BR /&gt;&lt;BR /&gt;I've tested this on HP Netservers and ProLiants of various models.  &lt;BR /&gt;&lt;BR /&gt;The real question should be, is this a concern?  I don't think so, as the processor field is populated. &lt;BR /&gt;&lt;BR /&gt;If you really have to check the physical id field, using lshw is my recommendation.</description>
      <pubDate>Wed, 16 Nov 2005 02:10:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670839#M67138</guid>
      <dc:creator>Craig Gilmore</dc:creator>
      <dc:date>2005-11-16T02:10:36Z</dc:date>
    </item>
    <item>
      <title>Re: linux cpu id</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670840#M67139</link>
      <description>So the behaviour (two cpu with the same physical ID) seems to be "normal" but in that case how explains that when HT is enabled the system detects four cpu (two logical processor by physical cpu) with the correct ID i.e cpu #0 and #1 (logical from the first physical processor) with ID 0 and cpu #2 and #3 (logical from the second physical processor) with ID 3 (I have also checked that with HT enabled the sibling map is correct)?&lt;BR /&gt;&lt;BR /&gt;In that case physical ID are different so I have still the question why when HT is disables physical ID are identical</description>
      <pubDate>Wed, 16 Nov 2005 06:46:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-cpu-id/m-p/3670840#M67139</guid>
      <dc:creator>Carrez_1</dc:creator>
      <dc:date>2005-11-16T06:46:55Z</dc:date>
    </item>
  </channel>
</rss>

