[PATCH] x86, x86_64: dual core proc-cpuinfo and sibling-map fix

- broken sibling_map setup in x86_64

- grouping all the core and HT related cpuinfo fields.
  We are reasonably sure that adding new cpuinfo fields after "siblings" field,
  will not cause any app failure. Thats because today's /proc/cpuinfo
  format is completely different on x86, x86_64 and we haven't heard of any
  x86 app breakage because of this issue. Grouping these fields will 
  result in more or less common format on all architectures (ia64, x86 and 
  x86_64) and will cause less confusion.

Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

1 files changed, 3 insertions, 8 deletions

diff --git a/arch/x86_64/kernel/setup.c b/arch/x86_64/kernel/setup.c
index 7ba443584a0c..b18c114c7648 100644
--- a/arch/x86_64/kernel/setup.c
+++ b/arch/x86_64/kernel/setup.c
@@ -1152,6 +1152,8 @@ static int show_cpuinfo(struct seq_file *m, void *v)
                 seq_printf(m, "physical id\t: %d\n", phys_proc_id[cpu]);
                 seq_printf(m, "siblings\t: %d\n",
                                 c->x86_num_cores * smp_num_siblings);
+                seq_printf(m, "core id\t\t: %d\n", cpu_core_id[cpu]);
+                seq_printf(m, "cpu cores\t: %d\n", c->x86_num_cores);
         }
 #endif  
 
@@ -1195,15 +1197,8 @@ static int show_cpuinfo(struct seq_file *m, void *v)
                         }
         }
 
-        seq_printf(m, "\n");
+        seq_printf(m, "\n\n");
 
-#ifdef CONFIG_SMP
-        /* Put new fields at the end to lower the probability of
-           breaking user space parsers. */
-        seq_printf(m, "core id\t\t: %d\n", cpu_core_id[c - cpu_data]);
-        seq_printf(m, "cpu cores\t: %d\n", c->x86_num_cores);
-#endif
-        seq_printf(m, "\n");
         return 0;
 }