linux-kernel - Re: New Intel feature flags.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 23 Sep 2006 21:28:21 -0400
From:	Dave Jones <davej@...hat.com>
To:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>, ak@...e.de
Subject: Re: New Intel feature flags.

On Sun, Sep 24, 2006 at 03:21:06AM +0200, Michal Piotrowski wrote:
 > Hi Dave,
 > 
 > On 24/09/06, Dave Jones <davej@...hat.com> wrote:
 > > Add supplemental SSE3 instructions flag, and Direct Cache Access flag.
 > > As described in "Intel Processor idenfication and the CPUID instruction
 > > AP485 Sept 2006"
 > >
 > > Signed-off-by: Dave Jones <davej@...hat.com>
 > >
 > > --- local-git/arch/i386/kernel/cpu/proc.c~      2006-09-23 20:46:35.000000000 -0400
 > > +++ local-git/arch/i386/kernel/cpu/proc.c       2006-09-23 20:48:02.000000000 -0400
 > > @@ -46,8 +46,8 @@ static int show_cpuinfo(struct seq_file
 > >
 > >                 /* Intel-defined (#2) */
 > >                 "pni", NULL, NULL, "monitor", "ds_cpl", "vmx", "smx", "est",
 > > -               "tm2", NULL, "cid", NULL, NULL, "cx16", "xtpr", NULL,
 > > -               NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL,
 > > +               "tm2", "ssse3", "cid", NULL, NULL, "cx16", "xtpr", NULL,
 > 
 > ssse3? Typo?

No. It stands for Supplemental SSE3.  SSE is already indicated by 'pni'.

	Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/