Use the cpuid instruction to generate the CPU brand string. And

base/cpu.cc

Index: base/cpu.cc
===================================================================
--- base/cpu.cc	(revision 159378)
+++ base/cpu.cc	(working copy)
@@ -84,8 +84,9 @@
 void CPU::Initialize() {
 #if defined(ARCH_CPU_X86_FAMILY)
   int cpu_info[4] = {-1};
-  char cpu_string[0x20];
-
+  char cpu_string[32];

[Mark Mentovai, 2012/10/03 18:34:02]

Now let’s make this stuff conform to Chromium style a little better. Don’t
declare variables until they’re used.
http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml?showone=Local_...

+  char cpu_brand[48];

[Mark Mentovai, 2012/10/03 18:34:02]

You can share a buffer for cpu_string and cpu_brand as long as it’s sized
appropriately, since the two buffers aren’t both needed at the same time.

If you share the buffer, you obviously won’t be able to use sizeof(BUF) where I
recommend you do that below, but the alternatives should be very obvious.

+  const int para_end = 0x80000004;

[Mark Mentovai, 2012/10/03 18:34:02]

Don’t abbreviate.
http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml?showone=Genera...

   // __cpuid with an InfoType argument of 0 returns the number of
   // valid Ids in CPUInfo[0] and the CPU identification string in
   // the other three array elements. The CPU identification string is
@@ -118,6 +119,21 @@
     has_ssse3_ = (cpu_info[2] & 0x00000200) != 0;
     has_sse41_ = (cpu_info[2] & 0x00080000) != 0;
     has_sse42_ = (cpu_info[2] & 0x00100000) != 0;
+
+    // get the brand string of the cpu.

[Mark Mentovai, 2012/10/03 18:34:02]

Comments should be written as sentences, and sentences start with capital
letters.
http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml?showone=Punctu...

[Mark Mentovai, 2012/10/03 18:34:02]

I don’t think there’s any reason for this to be in the |num_ids > 0|
conditional. The “basic” and “extended” groups of cpuid are totally distinct.

+    __cpuid(cpu_info, 0x80000000);
+
+    if (cpu_info[0] >= para_end) {
+      memset(cpu_brand, 0, sizeof(cpu_brand));

[Mark Mentovai, 2012/10/03 18:34:02]

You don’t need this memset, because you’re going to memcpy over cpu_brand
anyway.

+      char* cpu_brand_ptr = cpu_brand;
+
+      for (int parameter = 0x80000002; parameter <= para_end; parameter++) {
+        __cpuid(cpu_info, parameter);
+        memcpy(cpu_brand_ptr, cpu_info, sizeof(cpu_info));
+        cpu_brand_ptr += sizeof(cpu_info);
+      }
+      cpu_brand_ = cpu_brand;

[Mark Mentovai, 2012/10/03 18:34:02]

cpu_brand is not necessarily NUL-terminated as you’ve written things here
(although cpuid is SUPPOSED to return a NUL-terminated string, I wouldn’t rely
on that). See the comment above about NUL-termination for cpu_string, and
address this in the same way that you deal with that.

[jar (doing other things), 2012/10/04 17:42:03]

I couldn't find documentation that suggests the string comes null terminated. 
The sample documentation provides sample code that does the null termination,
and worse yet, the example given shows the CPU_vendor_ string to be:

GenuineIntel

which is 12 characters long... plus an unsupplied null termination byte.  Hence
that string is not supplied null terminated earlier, and probably this string is
not terminated here either.

[Mark Mentovai, 2012/10/04 18:00:45]

jar wrote:
The string in ebx-edx-ecx from cpuid 0 is not NUL-terminated, either in practice
or in documentation. As you say, it’s 12 characters long and the three 32-bit
registers only have room for 12 characters, so there’s no way for it to be
NUL-terminated.

The “brand string” returned by cpuid 0x80000002-0x80000004 is documented as
being NUL-terminated. Ref. Intel64 and IA-32 Architecture Software Developer’s
Manual, vol. 2A (Intel 253666,
http://download.intel.com/products/processor/manual/253666.pdf), August 2012,
vol. 2A page 3-168, CPUID/Methods for Returning Branding Information/How Brand
Stings Work. Ref. also AMD CPUID Specification (AMD 25481,
http://support.amd.com/us/Embedded_TechDocs/25481.pdf), September 2010, page 22,
2 CPUID Function Specification/CPUID Fn8000_000[4:2]_E[D,C,B,A]X Processor Name
String Identifier.

I still wouldn’t rely on that because we’re putting our buffer overflow (or not)
into the control of some external data or our ability to properly call cpuid and
memcpy in this loop. I’d always be precise with the lengths, which is what the
latest patch set does.

+    }
   }
 #endif
 }