summaryrefslogtreecommitdiffstats
path: root/fs
diff options
context:
space:
mode:
authorVenkatesh Pallipadi <venkatesh.pallipadi@intel.com>2007-01-22 20:40:34 -0800
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-01-23 07:52:05 -0800
commit58d9ce7d751fa11c6c8ea5dcd4d63b320aae1363 (patch)
tree4b188a931722c9f510f625eadb5ab02fc1ad55cd /fs
parentbbe1a59b3a3d4af3869647d294618a23f6c9c6a4 (diff)
downloadop-kernel-dev-58d9ce7d751fa11c6c8ea5dcd4d63b320aae1363.zip
op-kernel-dev-58d9ce7d751fa11c6c8ea5dcd4d63b320aae1363.tar.gz
[PATCH] Revert nmi_known_cpu() check during boot option parsing
Commit f2802e7f571c05f9a901b1f5bd144aa730ccc88e and its x86 version (b7471c6da94d30d3deadc55986cc38d1ff57f9ca) adds nmi_known_cpu() check while parsing boot options in x86_64 and i386. With that, "nmi_watchdog=2" stops working for me on Intel Core 2 CPU based system. The problem is, setup_nmi_watchdog is called while parsing the boot option and identify_cpu is not done yet. So, the return value of nmi_known_cpu() is not valid at this point. So revert that check. This should not have any adverse effect as the nmi_known_cpu() check is done again later in enable_lapic_nmi_watchdog(). Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com> Cc: Don Zickus <dzickus@redhat.com> Cc: Andi Kleen <ak@suse.de> Cc: Ingo Molnar <mingo@elte.hu> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud