#!/usr/bin/python # # show_deltas: Read list of printk messages instrumented with # time data, and format with time deltas. # # Also, you can show the times relative to a fixed point. # # Copyright 2003 Sony Corporation # # GPL 2.0 applies. import sys import string def usage(): print ("""usage: show_delta [] This program parses the output from a set of printk message lines which have time data prefixed because the CONFIG_PRINTK_TIME option is set, or the kernel command line option "time" is specified. When run with no options, the time information is converted to show the time delta between each printk line and the next. When run with the '-b' option, all times are relative to a single (base) point in time. Options: -h Show this usage help. -b Specify a base for time references. can be a number or a string. If it is a string, the first message line which matches (at the beginning of the line) is used as the time reference. ex: $ dmesg >timefile $ show_delta -b NET4 timefile will show times relative to the line in the kernel output starting with "NET4". """) sys.exit(1) # returns a tuple containing the seconds and text for each message line # seconds is returned as a float # raise an exception if no timing data was found def get_time(line): if line[0]!="[": raise ValueError # split on closing bracket (time_str, rest) = string.split(line[1:],']',1) time = string.atof(time_str) #print "time=", time return (time, rest) # average line looks like: # [ 0.084282] VFS: Mounted root (romfs filesystem) readonly # time data is expressed in seconds.useconds, # convert_line adds a delta for each line last_time = 0.0 def convert_line(line, base_time): global last_time try: (time, rest) = get_time(line) except: # if any problem parsing time, don't convert anything return line if base_time: # show time from base delta = time - base_time else: # just show time from last line delta = time - last_time last_time = time return ("[%5.6f < %5.6f >]" % (time, delta)) + rest def main(): base_str = "" filein = "" for arg in sys.argv[1:]: if arg=="-b": base_str = sys.argv[sys.argv.index("-b")+1] elif arg=="-h": usage() else: filein = arg if not filein: usage() try: lines = open(filein,"r").readlines() except: print ("Problem opening file: %s" % filein) sys.exit(1) if base_str: print ('base= "%s"' % base_str) # assume a numeric base. If that fails, try searching # for a matching line. try: base_time = float(base_str) except: # search for line matching string found = 0 for line in lines: try: (time, rest) = get_time(line) except: continue if string.find(rest, base_str)==1: base_time = time found = 1 # stop at first match break if not found: print ('Couldn\'t find line matching base pattern "%s"' % base_str) sys.exit(1) else: base_time = 0.0 for line in lines: print (convert_line(line, base_time),) main() id=39cb2c9a316e77f6dfba96c543e55b6672d5a37e'>llc_s_ev.h
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2017-01-29 13:50:06 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2017-01-29 13:50:06 -0800
commit39cb2c9a316e77f6dfba96c543e55b6672d5a37e (patch)
tree98fe974ee4e20121253de7f61fc8d01bdb3821c1 /include/net/llc_s_ev.h
parent2c5d9555d6d937966d79d4c6529a5f7b9206e405 (diff)
drm/i915: Check for NULL i915_vma in intel_unpin_fb_obj()
I've seen this trigger twice now, where the i915_gem_object_to_ggtt() call in intel_unpin_fb_obj() returns NULL, resulting in an oops immediately afterwards as the (inlined) call to i915_vma_unpin_fence() tries to dereference it. It seems to be some race condition where the object is going away at shutdown time, since both times happened when shutting down the X server. The call chains were different: - VT ioctl(KDSETMODE, KD_TEXT): intel_cleanup_plane_fb+0x5b/0xa0 [i915] drm_atomic_helper_cleanup_planes+0x6f/0x90 [drm_kms_helper] intel_atomic_commit_tail+0x749/0xfe0 [i915] intel_atomic_commit+0x3cb/0x4f0 [i915] drm_atomic_commit+0x4b/0x50 [drm] restore_fbdev_mode+0x14c/0x2a0 [drm_kms_helper] drm_fb_helper_restore_fbdev_mode_unlocked+0x34/0x80 [drm_kms_helper] drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper] intel_fbdev_set_par+0x18/0x70 [i915] fb_set_var+0x236/0x460 fbcon_blank+0x30f/0x350 do_unblank_screen+0xd2/0x1a0 vt_ioctl+0x507/0x12a0 tty_ioctl+0x355/0xc30 do_vfs_ioctl+0xa3/0x5e0 SyS_ioctl+0x79/0x90 entry_SYSCALL_64_fastpath+0x13/0x94 - i915 unpin_work workqueue: intel_unpin_work_fn+0x58/0x140 [i915] process_one_work+0x1f1/0x480 worker_thread+0x48/0x4d0 kthread+0x101/0x140 and this patch purely papers over the issue by adding a NULL pointer check and a WARN_ON_ONCE() to avoid the oops that would then generally make the machine unresponsive. Other callers of i915_gem_object_to_ggtt() seem to also check for the returned pointer being NULL and warn about it, so this clearly has happened before in other places. [ Reported it originally to the i915 developers on Jan 8, applying the ugly workaround on my own now after triggering the problem for the second time with no feedback. This is likely to be the same bug reported as https://bugs.freedesktop.org/show_bug.cgi?id=98829 https://bugs.freedesktop.org/show_bug.cgi?id=99134 which has a patch for the underlying problem, but it hasn't gotten to me, so I'm applying the workaround. ] Cc: Daniel Vetter <daniel.vetter@intel.com> Cc: Jani Nikula <jani.nikula@linux.intel.com> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com> Cc: Chris Wilson <chris@chris-wilson.co.uk> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Cc: Imre Deak <imre.deak@intel.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/net/llc_s_ev.h')