summaryrefslogtreecommitdiff
path: root/tools/testing/selftests/ftrace/Makefile
diff options
context:
space:
mode:
authorEric Dumazet <edumazet@google.com>2017-02-04 15:24:51 -0800
committerDavid S. Miller <davem@davemloft.net>2017-02-05 16:11:57 -0500
commit617f01211bafed65b5cb2fa5b671e839c7f2af86 (patch)
treefe5a66293642fd8c2a42c90e5a3aeb34826a06bf /tools/testing/selftests/ftrace/Makefile
parent3976001c9db0354a0bcbd77e324fdf1bc04e110f (diff)
8139too: use napi_complete_done()
Use napi_complete_done() instead of __napi_complete() to : 1) Get support of gro_flush_timeout if opt-in 2) Not rearm interrupts for busy-polling users. 3) use standard NAPI API. Signed-off-by: Eric Dumazet <edumazet@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/testing/selftests/ftrace/Makefile')
0 files changed, 0 insertions, 0 deletions
s patch series addresses both of these issues. The queues are fixed by simply zeroing the memory before use. PIO errors from userspace will result in a SIGBUS being sent to the user process. The MEM errors form userspace will result in a SIGKILL and also cause the offending pages to be claimed so they are no longer used in future tasks. SIGKILL is used to ensure that the process does not try to coredump and result in an attempt to read the memory again from within kernel space. Although there is a HV call to scrub the memory (mem_scrub), there is no easy way to guarantee that the real memory address(es) are not used by other tasks. Clearing the error with mem_scrub would zero the memory and cause the other processes to proceed with bad data. The handling of other non-resumable errors remain unchanged and will cause a panic. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/usb/dwc3/trace.c')