/* * Definitions for the KLSI KL5KUSB105 serial port adapter */ /* vendor/product pairs that are known to contain this chipset */ #define PALMCONNECT_VID 0x0830 #define PALMCONNECT_PID 0x0080 #define KLSI_VID 0x05e9 #define KLSI_KL5KUSB105D_PID 0x00c0 /* Vendor commands: */ /* port table -- the chip supports up to 4 channels */ /* baud rates */ enum { kl5kusb105a_sio_b115200 = 0, kl5kusb105a_sio_b57600 = 1, kl5kusb105a_sio_b38400 = 2, kl5kusb105a_sio_b19200 = 4, kl5kusb105a_sio_b14400 = 5, kl5kusb105a_sio_b9600 = 6, kl5kusb105a_sio_b4800 = 8, /* unchecked */ kl5kusb105a_sio_b2400 = 9, /* unchecked */ kl5kusb105a_sio_b1200 = 0xa, /* unchecked */ kl5kusb105a_sio_b600 = 0xb /* unchecked */ }; /* data bits */ #define kl5kusb105a_dtb_7 7 #define kl5kusb105a_dtb_8 8 /* requests: */ #define KL5KUSB105A_SIO_SET_DATA 1 #define KL5KUSB105A_SIO_POLL 2 #define KL5KUSB105A_SIO_CONFIGURE 3 /* values used for request KL5KUSB105A_SIO_CONFIGURE */ #define KL5KUSB105A_SIO_CONFIGURE_READ_ON 3 #define KL5KUSB105A_SIO_CONFIGURE_READ_OFF 2 /* Interpretation of modem status lines */ /* These need sorting out by individually connecting pins and checking * results. FIXME! * When data is being sent we see 0x30 in the lower byte; this must * contain DSR and CTS ... */ #define KL5KUSB105A_DSR ((1<<4) | (1<<5)) #define KL5KUSB105A_CTS ((1<<5) | (1<<4)) #define KL5KUSB105A_WANTS_TO_SEND 0x30 #if 0 #define KL5KUSB105A_DTR /* Data Terminal Ready */ #define KL5KUSB105A_CTS /* Clear To Send */ #define KL5KUSB105A_CD /* Carrier Detect */ #define KL5KUSB105A_DSR /* Data Set Ready */ #define KL5KUSB105A_RxD /* Receive pin */ #define KL5KUSB105A_LE #define KL5KUSB105A_RTS #define KL5KUSB105A_ST #define KL5KUSB105A_SR #define KL5KUSB105A_RI /* Ring Indicator */ #endif ch/x86/util/unwind-libdw.c?id=79c6f448c8b79c321e4a1f31f98194e4f6b6cae7'>treecommitdiff
path: root/tools/perf/arch/x86/util/unwind-libdw.c
diff options
context:
space:
mode:
authorSteven Rostedt (VMware) <rostedt@goodmis.org>2017-01-30 19:27:10 -0500
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2017-01-31 09:13:49 -0500
commit79c6f448c8b79c321e4a1f31f98194e4f6b6cae7 (patch)
tree370efda701f03cccf21e02bb1fdd3b852547d75c /tools/perf/arch/x86/util/unwind-libdw.c
parent0c744ea4f77d72b3dcebb7a8f2684633ec79be88 (diff)
tracing: Fix hwlat kthread migration
The hwlat tracer creates a kernel thread at start of the tracer. It is pinned to a single CPU and will move to the next CPU after each period of running. If the user modifies the migration thread's affinity, it will not change after that happens. The original code created the thread at the first instance it was called, but later was changed to destroy the thread after the tracer was finished, and would not be created until the next instance of the tracer was established. The code that initialized the affinity was only called on the initial instantiation of the tracer. After that, it was not initialized, and the previous affinity did not match the current newly created one, making it appear that the user modified the thread's affinity when it did not, and the thread failed to migrate again. Cc: stable@vger.kernel.org Fixes: 0330f7aa8ee6 ("tracing: Have hwlat trace migrate across tracing_cpumask CPUs") Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'tools/perf/arch/x86/util/unwind-libdw.c')