linux-kernel - Re: Via C3: other flags possible ?

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]

Message-Id: <200705201459.46357.ak@suse.de>
Date:	Sun, 20 May 2007 14:59:46 +0200
From:	Andi Kleen <ak@...e.de>
To:	Christian Volkmann <haveaniceday@...sv.de>
Cc:	Claas Langbehn <claas@...tdir.de>, linux-kernel@...r.kernel.org
Subject: Re: Via C3: other flags possible ?

> C7 Esther:
> Hmm, I expect the NX-Bit should be detected from linux during the
> boot. The NX function bit seems to be at the same place where it's
> located for other CPU.

> Unfortunately I have no C7 hardware and I am too much a beginner
> in kernel programming to prepare this "dry".
> 
> May be a "senior kernel programmer" can easy check if the C7 runs
> through the regular NX-function detection?

If it's in CPUID (nx in /proc/cpuinfo flags) it should just work.

NX also doesn't need to be handled in the early CPUID bits detection 
because the kernel can handle it not being there fine. Only bits
who when missing cause the kernel to panic early or crash need to
be tested there.

-Andi

-
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/