summaryrefslogtreecommitdiff
path: root/bpf.vim
blob: bb6322a5b57f009550789c7fbf956fa28080ed15 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
" Vim syntax file
" Language: Berkeley Packet Filter
" Maintainer: Daniel Borkmann
" Latest Revision: 08/16/2011
"
" In order to make syntax highlighting for BPFs work in vim, copy this file
" to ~/.vim/syntax/ and activate it in vim by entering:
"
"    :set syntax=bpf
"
" If you want to automatically load the BPF syntax highlighting for *.bpf 
" files create the ~/.vim/filetype.vim with the following content:
"
"    my filetype file
"    if exists("did_load_filetypes")
"      finish
"    endif
"
"    augroup filetypedetect
"      au! BufRead,BufNewFile *.bpf  setfiletype bpf
"    augroup END
"

if exists("b:current_syntax")
  finish
endif

syn keyword bpfTodo contained TODO FIXME XXX NOTE
syn keyword bpfKeywords ldb ldh ld ldi ldx ldxi ldxb st stx jmp ja jeq jneq jne skipwhite
syn keyword bpfKeywords jlt jle jgt jge jset add sub mul div mod neg and or xor skipwhite
syn keyword bpfKeywords lsh rsh ret tax txa skipwhite

syn match bpfLabel /[a-zA-Z0-9_]\+/
syn match bpfSpChar /[:,#\[\]\(\)+*&]\?/ contains=bpfNumber,bpfLabel
syn match bpfNumber /\(0[xX]\x\+\|\d\+\)/
syn match bpfComment ";.*$" contains=bpfTodo

hi def link bpfTodo Todo
hi def link bpfComment Comment
hi def link bpfKeywords Keyword
hi def link bpfLabel Type
hi def link bpfNumber Number
hi def link bpfSpChar Special

let b:current_syntax = "bpf"
69b67162c397a1a1c1e02f6ce'>diff)
x86/mce: Make timer handling more robust
Erik reported that on a preproduction hardware a CMCI storm triggers the BUG_ON in add_timer_on(). The reason is that the per CPU MCE timer is started by the CMCI logic before the MCE CPU hotplug callback starts the timer with add_timer_on(). So the timer is already queued which triggers the BUG. Using add_timer_on() is pretty pointless in this code because the timer is strictlty per CPU, initialized as pinned and all operations which arm the timer happen on the CPU to which the timer belongs. Simplify the whole machinery by using mod_timer() instead of add_timer_on() which avoids the problem because mod_timer() can handle already queued timers. Use __start_timer() everywhere so the earliest armed expiry time is preserved. Reported-by: Erik Veijola <erik.veijola@intel.com> Tested-by: Borislav Petkov <bp@alien8.de> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Reviewed-by: Borislav Petkov <bp@alien8.de> Cc: Tony Luck <tony.luck@intel.com> Link: http://lkml.kernel.org/r/alpine.DEB.2.20.1701310936080.3457@nanos Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'tools/perf/tests/keep-tracking.c')