diff options
| author | Peter Zijlstra <peterz@infradead.org> | 2020-09-02 16:25:58 +0300 |
|---|---|---|
| committer | Thomas Gleixner <tglx@linutronix.de> | 2020-09-04 16:12:55 +0300 |
| commit | 389cd0cd8b3790b555c3679da946f4aa4fba3bab (patch) | |
| tree | fc93289f3e070a93ab0ba91a56271faec478317b /scripts/bpf_helpers_doc.py | |
| parent | f0b67c39c190e19bc1604a13bcc985c4445a4b2f (diff) | |
| download | linux-389cd0cd8b3790b555c3679da946f4aa4fba3bab.tar.xz | |
x86/debug: Remove the historical junk
Remove the historical junk and replace it with a WARN and a comment.
The problem is that even though the kernel only uses TF single-step in
kprobes and KGDB, both of which consume the event before this, QEMU/KVM has
bugs in this area that can trigger this state so it has to be dealt with.
Suggested-by: Brian Gerst <brgerst@gmail.com>
Suggested-by: Andy Lutomirski <luto@amacapital.net>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Tested-by: Daniel Thompson <daniel.thompson@linaro.org>
Link: https://lore.kernel.org/r/20200902133201.170216274@infradead.org
Diffstat (limited to 'scripts/bpf_helpers_doc.py')
0 files changed, 0 insertions, 0 deletions