drivers

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
drivers [2018/05/18 09:35] admindrivers [2018/05/18 09:53] (current) – [Debugging] admin
Line 29: Line 29:
 An issue with I/O memory accesses is memory reordering, which may require memory barriers (rmb(), wmb(), mw()). An issue with I/O memory accesses is memory reordering, which may require memory barriers (rmb(), wmb(), mw()).
  
 +===== User space memory handling =====
 User-space applications can access physical addresses directly through /dev/mem. User-space applications can access physical addresses directly through /dev/mem.
 +
 +  * Process heap (sbrk, brk)
 +  * Direct/Abstract (mmap)
 +  * Allocators (malloc, calloc, realloc, free)
 +
  
 ====== Modules ====== ====== Modules ======
Line 103: Line 109:
  
 Threaded interrupts are executed inside a thread (allows to block inside the handler). There is support for interrupt handler execution priority. Threaded interrupts are executed inside a thread (allows to block inside the handler). There is support for interrupt handler execution priority.
 +
 +UIO allows the handling from interrupt in user space.
  
 ====== Concurrency ====== ====== Concurrency ======
Line 133: Line 141:
   * Kernel markers   * Kernel markers
   * LTTng with LTTV   * LTTng with LTTV
 +  * printk
 +  * kernel configs
 +  * debugfs/sysfs
 +  * ftrace
 +  * Kdb
 +  * Kgdb
 +  * jtag + gdb
 +  * emulation (QEmu)
  
 +Userspace:
 +  * printf
 +  * strace
 +  * ltrace
 +  * valgrind
 +  * gdb
 ====== Userspace drivers ====== ====== Userspace drivers ======
 http://2net.co.uk/slides/ew2016-userspace-drivers-slides.pdf http://2net.co.uk/slides/ew2016-userspace-drivers-slides.pdf
  
  
  • drivers.1526636126.txt.gz
  • Last modified: 8 years ago
  • by admin