summaryrefslogtreecommitdiff
path: root/arch/x86/pci/amd_bus.c
diff options
context:
space:
mode:
authorFrederic Weisbecker <fweisbec@gmail.com>2009-05-03 05:03:57 +0400
committerIngo Molnar <mingo@elte.hu>2009-05-07 12:05:57 +0400
commit5928c3cc0ffcb6894bbab6be591b7ae1786b2d87 (patch)
tree75503a660dafe84dcd434912c5a0bdf97cad3c8a /arch/x86/pci/amd_bus.c
parente8808c1019b048a43686dbd25c188a035842c2e2 (diff)
downloadlinux-5928c3cc0ffcb6894bbab6be591b7ae1786b2d87.tar.xz
tracing/filters: support for operator reserved characters in strings
When we set a filter for an event, such as: echo "name == my_lock_name" > \ /debug/tracing/events/lockdep/lock_acquired/filter then the following order of token type is parsed: - space - operator - parentheses - operand Because the operators and parentheses have a higher precedence than the operand characters, which is normal, then we can't use any string containing such special characters: ()=<>!&| To get this support and also avoid ambiguous intepretation from the parser or the human, we can do it using double quotes so that we keep the usual languages habits. Then after this patch you can still declare string condition like before: echo name == myname But if you want to compare against a string containing an operator character, you can use double quotes: echo 'name == "&myname"' Don't forget to include the whole expression into single quotes or the double ones will be eaten by echo. [ Impact: support strings with special characters for tracing filters ] Cc: Tom Zanussi <tzanussi@gmail.com> Cc: Steven Rostedt <rostedt@goodmis.org> Cc: Li Zefan <lizf@cn.fujitsu.com> Cc: Zhaolei <zhaolei@cn.fujitsu.com> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Diffstat (limited to 'arch/x86/pci/amd_bus.c')
0 files changed, 0 insertions, 0 deletions