linux-kernel - Re: [PATCH] MIPS: nofpu and nodsp only affect CPU0

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: <20100510201959.GB28820@linux-mips.org>
Date:	Mon, 10 May 2010 21:19:59 +0100
From:	Ralf Baechle <ralf@...ux-mips.org>
To:	Kevin Cernekee <cernekee@...il.com>
Cc:	linux-mips@...ux-mips.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MIPS: nofpu and nodsp only affect CPU0

On Sun, May 02, 2010 at 02:43:52PM -0700, Kevin Cernekee wrote:

> The "nofpu" and "nodsp" kernel command line options currently do not
> affect CPUs that are brought online later in the boot process or
> hotplugged at runtime.  It is desirable to apply the nofpu/nodsp options
> to all CPUs in the system, so that surprising results are not seen when
> a process migrates from one CPU to another.

I like this patch; this solution is also cleaner than iterating over the
cpu data array.  However as it constitutes a change in established kernel
behaviour I prefer to queue this patch for 2.6.35 rather than applying it
immediately.

Thanks!

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