summaryrefslogtreecommitdiffstats
path: root/drivers/w1
diff options
context:
space:
mode:
authorMandeep Singh Baines <msb@chromium.org>2011-07-27 01:08:54 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2011-07-27 01:49:45 +0200
commitc958474b6d721ff09e4abf143efc07365d63aea5 (patch)
tree9fbf1f273fcb39d72d5e66a17ed9f0f45c4e7cb6 /drivers/w1
parentpanic: panic=-1 for immediate reboot (diff)
downloadlinux-c958474b6d721ff09e4abf143efc07365d63aea5.tar.xz
linux-c958474b6d721ff09e4abf143efc07365d63aea5.zip
panic, vt: do not force oops output when panic_timeout < 0
Don't force output if you intend to reboot immediately. In this patch, I'm disabling the functionality enabled by vc->vc_panic_force_write if panic_timeout < 0 (i.e. no timeout). vc_panic_force_write is only enabled for fb video consoles if the FBINFO_CAN_FORCE_OUTPUT flag is set. For our application, we're using ram_oops to preserved the panic in memory. We want to reliably, and as fast as possible, machine_restart. The vc_panic_force_write flag results in a bunch of graphics driver code to be invoked which slows down restart and decreases reliability. Since we're already storing the panic in RAM and are going to reboot immediately, there is no benefit in mode switching back to the vc in order to display the panic output. The log buffer will get flushed by the console_unblank() call so remote management consoles should see all output. Signed-off-by: Mandeep Singh Baines <msb@chromium.org> Cc: Huang Ying <ying.huang@intel.com> Cc: Andi Kleen <ak@linux.intel.com> Cc: Hugh Dickins <hughd@google.com> Cc: Olaf Hering <olaf@aepfle.de> Cc: Jesse Barnes <jbarnes@virtuousgeek.org> Cc: Dave Airlie <airlied@gmail.com> Cc: Greg Kroah-Hartman <gregkh@suse.de> Acked-by: Alan Cox <alan@lxorguk.ukuu.org.uk> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/w1')
0 files changed, 0 insertions, 0 deletions