#include "util.h" #include "../debug.h" /* * Default error logging functions */ static int perf_stdio__error(const char *format, va_list args) { fprintf(stderr, "Error:\n"); vfprintf(stderr, format, args); return 0; } static int perf_stdio__warning(const char *format, va_list args) { fprintf(stderr, "Warning:\n"); vfprintf(stderr, format, args); return 0; } static struct perf_error_ops default_eops = { .error = perf_stdio__error, .warning = perf_stdio__warning, }; static struct perf_error_ops *perf_eops = &default_eops; int ui__error(const char *format, ...) { int ret; va_list args; va_start(args, format); ret = perf_eops->error(format, args); va_end(args); return ret; } int ui__warning(const char *format, ...) { int ret; va_list args; va_start(args, format); ret = perf_eops->warning(format, args); va_end(args); return ret; } /** * perf_error__register - Register error logging functions * @eops: The pointer to error logging function struct * * Register UI-specific error logging functions. Before calling this, * other logging functions should be unregistered, if any. */ int perf_error__register(struct perf_error_ops *eops) { if (perf_eops != &default_eops) return -1; perf_eops = eops; return 0; } /** * perf_error__unregister - Unregister error logging functions * @eops: The pointer to error logging function struct * * Unregister already registered error logging functions. */ int perf_error__unregister(struct perf_error_ops *eops) { if (perf_eops != eops) return -1; perf_eops = &default_eops; return 0; } x/net-next.git/?h=nds-private-remove'>summaryrefslogtreecommitdiff
path: root/tools/perf/bench/futex-hash.c
diff options
context:
space:
mode:
authorDaniel Vetter <daniel.vetter@ffwll.ch>2017-01-12 17:15:56 +0100
committerDaniel Vetter <daniel.vetter@ffwll.ch>2017-01-30 10:17:32 +0100
commite6e7b48b295afa5a5ab440de0a94d9ad8b3ce2d0 (patch)
tree77cadb6d8aad1b52c34e4afa8c9deef603bbe2ed /tools/perf/bench/futex-hash.c
parent4e5b54f127426c82dc2816340c26d951a5bb3429 (diff)
drm: Don't race connector registration
I was under the misconception that the sysfs dev stuff can be fully set up, and then registered all in one step with device_add. That's true for properties and property groups, but not for parents and child devices. Those must be fully registered before you can register a child. Add a bit of tracking to make sure that asynchronous mst connector hotplugging gets this right. For consistency we rely upon the implicit barriers of the connector->mutex, which is taken anyway, to ensure that at least either the connector or device registration call will work out. Mildly tested since I can't reliably reproduce this on my mst box here. Reported-by: Dave Hansen <dave.hansen@intel.com> Cc: Dave Hansen <dave.hansen@intel.com> Acked-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> Link: http://patchwork.freedesktop.org/patch/msgid/1484237756-2720-1-git-send-email-daniel.vetter@ffwll.ch
Diffstat (limited to 'tools/perf/bench/futex-hash.c')