linux-kernel - Re: FW: Linux question

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 for Android: free password hash cracker in your pocket

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

Message-ID: <47D2C7D7.2080301@tmr.com>
Date:	Sat, 08 Mar 2008 12:07:35 -0500
From:	Bill Davidsen <davidsen@....com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Justin Banks <justinb@...bone.com>,
	"Miller, Mike (OS Dev)" <Mike.Miller@...com>,
	linux-kernel@...r.kernel.org
Subject: Re: FW: Linux question

Andi Kleen wrote:
> Bill Davidsen <davidsen@....com> writes:
>
>   
>> Here's an interesting question, why isn't there an "online" file for
>> each CPU?
>>     
>
> There are still some problems with off lining CPU #0 on x86 at least,
> that is why it is not allowed. iirc they weren't very difficult so it
> would be probably fixable with some effort.
>   

If that's the case I would think that making it read-only would be a 
better solution, since I found this while creating a little tool to scan 
and see what's online and what's not. Obviously there can be exception 
cases for CPU0 and x86, but I would think that having the CPU0 for x86 
be read-only would be a quirk, and handled in the kernel.

-- 
Bill Davidsen <davidsen@....com>
  "Woe unto the statesman who makes war without a reason that will still
  be valid when the war is over..." Otto von Bismark 


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