Char Drivers Sarah Diesburg COP5641. Resources LDD Chapter 3 Red font in slides where up-to-date code diverges from book LDD module source code for 3.2.x.

Slides:



Advertisements
Similar presentations
Linux device-driver issues
Advertisements

Device Drivers. Linux Device Drivers Linux supports three types of hardware device: character, block and network –character devices: R/W without buffering.
RT_FIFO, Device driver.
Sogang University Advanced Operating Systems (Linux Device Drivers) Advanced Operating Systems (Linux Device Drivers) Sang Gue Oh, Ph.D.
R4 Dynamically loading processes. Overview R4 is closely related to R3, much of what you have written for R3 applies to R4 In R3, we executed procedures.
CS 450 Module R4. R4 Overview Due on March 11 th along with R3. R4 is a small yet critical part of the MPX system. In this module, you will add the functionality.
Building and Running Modules Sarah Diesburg COP 5641.
The Linux Kernel: Memory Management
Memory management.
Operating system services Program execution I/O operations File-system manipulation Communications Error detection Resource allocation Accounting Protection.
User-Level Memory Management in Linux Programming
Daemon Processes Long lived utility processes Often started at system boot and ended when system shuts down Run in the background with no controlling terminal.
1 UNIX 1 History of UNIX 2 Overview of UNIX 3 Processes in UNIX 4 Memory management in UNIX 5 The UNIX file system 6 Input/output in UNIX.
63 UQC152H3 Advanced OS Writing a Device Driver. 64 The SCULL Device Driver Simple Character Utility for Loading Localities 6 devices types –Scull-03.
Files. System Calls for File System Accessing files –Open, read, write, lseek, close Creating files –Create, mknod.
CE6105 Linux 作業系統 Linux Operating System 許 富 皓. Chapter 2 Memory Addressing.
Inter Process Communication:  It is an essential aspect of process management. By allowing processes to communicate with each other: 1.We can synchronize.
Home: Phones OFF Please Unix Kernel Parminder Singh Kang Home:
CSE 451 Section 4 Project 2 Design Considerations.
1 I/O Management in Representative Operating Systems.
Char Drivers Linux Kernel Programming CIS 4930/COP 5641.
Data Types in the Kernel Sarah Diesburg COP 5641.
Data Structures in the Kernel Sarah Diesburg COP 5641.
M. Muztaba Fuad Advanced Operating System Project Device Drivers.
File System. NET+OS 6 File System Architecture Design Goals File System Layer Design Storage Services Layer Design RAM Services Layer Design Flash Services.
POSIX: Files Introduction to Operating Systems: Discussion 1 Read Solaris System Interface Guide: Ch. 5.1 Basic File I/O.
Loadable Kernel Modules Dzintars Lepešs The University of Latvia.
Operating System Program 5 I/O System DMA Device Driver.
Real-Time Concepts for Embedded Systems Author: Qing Li with Caroline Yao ISBN: CMPBooks.
CS 6560 Operating System Design Lecture 13 Finish File Systems Block I/O Layer.
Concurrency and Race Conditions Sarah Diesburg COP 5641.
OPERATING SYSTEM OVERVIEW. Contents Basic hardware elements.
Real-time Systems Lab, Computer Science and Engineering, ASU Linux Modules and Device Drivers (ESP – Fall 2014) Computer Science & Engineering Department.
CSC 322 Operating Systems Concepts Lecture - 25: by Ahmed Mumtaz Mustehsan Special Thanks To: Tanenbaum, Modern Operating Systems 3 e, (c) 2008 Prentice-Hall,
SIMULATED UNIX FILE SYSTEM Implementation in C Tarek Youssef Bipanjit Sihra.
Chapter 4. INTERNAL REPRESENTATION OF FILES
Operating Systems Lecture 7 OS Potpourri Adapted from Operating Systems Lecture Notes, Copyright 1997 Martin C. Rinard. Zhiqing Liu School of Software.
Kernel Modules. Kernel Module Pieces of code that can be loaded and unloaded into the kernel upon demand. Compiled as an independent program With appropriate.
1 Linux Operating System 許 富 皓. 2 Memory Addressing.
1 File Systems: Consistency Issues. 2 File Systems: Consistency Issues File systems maintains many data structures  Free list/bit vector  Directories.
UNIX Files File organization and a few primitives.
Using the /proc File System with “scull” Sarah Diesburg COP 5641.
1 Chapter 10 : Case Study - UNIX History Overview Processes Memory management Input/output in The unix file system Security Note: This case study covers.
Files & File system. A Possible File System Layout Tanenbaum, Modern Operating Systems 3 e, (c) 2008 Prentice-Hall, Inc. All rights reserved
CS 241 Section Week #9 (11/05/09). Topics MP6 Overview Memory Management Virtual Memory Page Tables.
K ERNEL D EVELOPMENT CSC585 Class Project Dawn Nelson December 2009.
Interfacing Device Drivers with the Kernel
B LOCK L AYER S UBSYSTEM Linux Kernel Programming CIS 4930/COP 5641.
Linux File system Implementations
Ted Baker  Andy Wang COP 5641 / CIS 4930
4P13 Week 12 Talking Points Device Drivers 1.Auto-configuration and initialization routines 2.Routines for servicing I/O requests (the top half)
Lab 12 Department of Computer Science and Information Engineering National Taiwan University Lab12 – Driver 2014/12/16 1 /21.
COMP 3438 – Part I - Lecture 5 Character Device Drivers
4P13 Week 9 Talking Points
Silberschatz, Galvin and Gagne ©2011 Operating System Concepts Essentials – 8 th Edition Chapter 2: The Linux System Part 2.
I/O Software CS 537 – Introduction to Operating Systems.
MINIX Presented by: Clinton Morse, Joseph Paetz, Theresa Sullivan, and Angela Volk.
Linux Kernel Development Memory Management Pavel Sorokin Gyeongsang National University
Finish up OS topics Group plans. Today Finish up and review Linux device driver stuff – Walk example again – See how it all goes together – Discuss talking.
Lecture 3 Module Programming and Device Driver (Homework#1 included) Kyu Ho Park Sept. 15, 2015.
1 COMP 3500 Introduction to Operating Systems Project 4 – Processes and System Calls Part 4: Managing File System State Dr. Xiao Qin Auburn University.
File System Design David E. Culler CS162 – Operating Systems and Systems Programming Lecture 23 October 22, 2014 Reading: A&D a HW 4 out Proj 2 out.
Input/Output (I/O) Important OS function – control I/O
Linux Kernel Driver.
Scull device 사용 예 강서일( ) 최정욱( ).
An overview of the kernel structure
Chapter 2: The Linux System Part 2
chapter 3-Char Device Driver
CSE 333 – Section 3 POSIX I/O Functions.
Internal Representation of Files
Presentation transcript:

Char Drivers Sarah Diesburg COP5641

Resources LDD Chapter 3 Red font in slides where up-to-date code diverges from book LDD module source code for 3.2.x de.html de.html

Resources LXR – Cross-referenced Linux Go to Click on Linux and later Select your kernel version from drop-down menu

Resources Get kernel manpages! #> wget manual-3.2_ ~bpo60+1_all.debhttp://ftp.at.debian.org/debian-backports//pool/main/l/linux/linux- manual-3.2_ ~bpo60+1_all.deb #> dpkg -i linux-manual-3.2_ ~bpo60+1_all.deb

Goal Write a complete char device driver scull Simple Character Utility for Loading Localities Not hardware dependent Just acts on some memory allocated from the kernel

The Design of scull Implements various devices scull0 to scull3 Four device drivers, each consisting of a memory area Global  Data contained within the device is shared by all the file descriptors that opened it Persistent  If the device is closed and reopened, data isn’t lost

The Design of scull scullpipe0 to scullpipe3 Four FIFO devices Act like pipes Show how blocking and nonblocking read and write can be implemented Without resorting to interrupts

The Design of scull scullsingle Similar to scull0 Allows only one process to use the driver at a time scullpriv Private to each virtual console

The Design of scull sculluid Can be opened multiple times by one user at a time Returns “Device Busy” if another user is locking the device scullwuid Blocks open if another user is locking the device

Major and Minor Numbers Char devices are accessed through names in the file system Special files/nodes in /dev >cd /dev >ls –l crw root root 5, 1 Apr 12 16:50 console brw-rw root disk 8, 0 Apr 12 16:50 sda brw-rw root disk 8, 1 Apr 12 16:50 sda1

Major and Minor Numbers Char devices are accessed through names in the file system Special files/nodes in /dev >cd /dev >ls –l crw root root 5, 1 Apr 12 16:50 console brw-rw root disk 8, 0 Apr 12 16:50 sda brw-rw root disk 8, 1 Apr 12 16:50 sda1 Char drivers are identified by a “c” Block drivers are identified by a “b” Major numbers Minor numbers

Major and Minor Numbers Major number identifies the driver associated with the device /dev/sda and /dev/sda1 are managed by driver 8 Minor number is used by the kernel to determine which device is being referred to

The Internal Representation of Device Numbers dev_t type, defined in Macros defined in 12 bits for the major number Use MAJOR(dev_t dev) to obtain the major number 20 bits for the minor number Use MINOR(dev_t dev) to obtain the minor number Use MKDEV(int major, int minor) to turn them into a dev_t

Allocating and Freeing Device Numbers To obtain one or more device numbers, use int register_chrdev_region(dev_t first, unsigned int count, char *name); first Beginning device number Minor device number is often 0 count Requested number of contiguous device numbers name Name of the device

Allocating and Freeing Device Numbers To obtain one or more device numbers, use int register_chrdev_region(dev_t first, unsigned int count, char *name); Returns 0 on success, error code on failure

Allocating and Freeing Device Numbers Kernel can allocate a major number on the fly int alloc_chrdev_region(dev_t *dev, unsigned int firstminor, unsigned int count, char *name); dev Output-only parameter that holds the first number on success firstminor Requested first minor number Often 0

Allocating and Freeing Device Numbers To free your device numbers, use int unregister_chrdev_region(dev_t first, unsigned int count);

Dynamic Allocation of Major Numbers Some major device numbers are statically assigned See Documentation/devices.txt To avoid conflicts, use dynamic allocation

scull_load Shell Script #!/bin/sh module=“scull” device=“scull” mode=“664” # invoke insmod with all arguments we got and use a pathname, # as newer modutils don’t look in. by default /sbin/insmod./$module.ko $* || exit 1 # remove stale nodes rm –f /dev/${device}[0-3] major=$(awk “\$2==\”$module\” {print \$1}” /proc/devices) Textbook typos

scull_load Shell Script mknod /dev/${device}0 c $major 0 mknod /dev/${device}1 c $major 1 mknod /dev/${device}2 c $major 2 mknod /dev/${device}3 c $major 3 # give appropriate group/permissions, and change the group. # Not all distributions have staff, some have “wheel” instead. group=“staff” grep –q ‘^staff:’ /etc/group || group=“wheel” chgrp $group /dev/${device}[0-3] chmod $mode /dev/${device}[0-3]

Overview of Data Structures struct scull_dev struct cdev struct file_operations scull_fops cdev_add() data struct i_node struct file One struct file per open() data

Some Important Data Structures file_operations file inode Defined in

File Operations struct file_operations { struct module *owner; /* pointer to the module that owns the structure prevents the module from being unloaded while in use */ loff_t (*llseek) (struct file *, loff_t, int); /* change the current position in a file returns a 64-bit offset, or a negative value on errors */ ssize_t (*read) (struct file *, char __user *, size_t, loff_t *); /* returns the number of bytes read, or a negative value on errors */ ssize_t (*aio_read) (struct kiocb *, const struct iovec *, unsigned long, loff_t); /* might return before a read completes */

File Operations ssize_t (*write) (struct file *, const char __user *, size_t, loff_t *); /* returns the number of written bytes, or a negative value on error */ ssize_t (*aio_write) (struct kiocb *, const struct iovec *, unsigned long, loff_t); int (*readdir) (struct file *, void *, filldir_t); /* this function pointer should be NULL for devices */ unsigned int (*poll) (struct file *, struct poll_table_struct *); /* query whether a read or write to file descriptors would block */ int (*unlocked_ioctl) (struct file *, unsigned int, unsigned long); int (*compat_ioctl) (struct file *, unsigned int, unsigned long); /* provides a way to issue device-specific commands (e.g., formatting) */

File Operations int (*mmap) (struct file *, struct vm_area_struct *); /* map a device memory to a process’s address */ int (*open) (struct inode *, struct file *); /* first operation performed on the device file if not defined, opening always succeeds, but driver is not notified */ int (*flush) (struct file *, fl_owner_t id); /* invoked when a process closes its copy of a file descriptor for a device not to be confused with fsync */ int (*release) (struct inode *, struct file *); /* invoked when the file structure is being released */ int (*fsync) (struct file *, loff_t, loff_t, int datasync); /* flush pending data for a file */ int (*aio_fsync) (struct kiocb *, int datasync); /* asynchronous version of fsync */ int (*fasync) (int, struct file *, int); /* notifies the device of a change in its FASYNC flag */

File Operations int (*flock) (struct file *, int, struct file_lock *); /* file locking for regular files, almost never implemented by device drivers */ ssize_t (*splice_read) (struct file *, loff_t *, struct pipe_inode_info *, size_t, unsigned int); ssize_t (*splice_write) (struct pipe_inode_info *, file *, loff_t *, size_t, unsigned int); /* implement gather/scatter read and write operations */ ssize_t (*sendpage) (struct file *, struct page *, int, size_t, loff_t *, int); /* called by kernel to send data, one page at a time usually not used by device drivers */

File Operations unsigned long (*get_unmapped_area) (struct file *, unsigned long, unsigned long, unsigned long, unsigned long); /* finds a location in the process’s memory to map in a memory segment on the underlying device used to enforce alignment requirements most drivers do not use this function */ int (*check_flags) (int); /* allows a module to check flags passed to an fcntl call */ int (*setlease) (struct file *, long, struct file_lock *); /* Establishes a lease on a file. Most drivers do not use this function */ long (*fallocate) (struct file *file, int mode, loff_t offset, loff_t len) /* Guarantees reserved space on storage for a file. Most drivers do not use this function */ };

scull device driver Implements only the most important methods struct file_operations scull_fops = {.owner = THIS_MODULE,.llseek = scull_llseek,.read = scull_read,.write = scull_write,.unlocked_ioctl = scull_ioctl,.open = scull_open,.release = scull_release, };

The File Structure struct file Nothing to do with the FILE pointers Defined in the C Library Represents an open file A pointer to file is often called filp

The File Structure Some important fields fmode_t f_mode; Identifies the file as either readable or writable loff_t f_pos; Current reading/writing position (64-bits) unsigned int f_flags; File flags, such as O_RDONLY, O_NONBLOCK, O_SYNC

The File Structure Some important fields struct file_operations *f_op; Operations associated with the file Dynamically replaceable pointer  Equivalent of method overriding in OO programming void *private_data; Can be used to store additional data structures Needs to be freed during the release method

The File Structure Some important fields struct dentry *f_dentry; Directory entry associated with the file Used to access the inode data structure  filp->f_dentry->d_inode

The i-node Structure There can be numerous file structures (multiple open descriptors) for a single file Only one inode structure per file

The i-node Structure Some important fields dev_t i_rdev; Contains device number For portability, use the following macros  unsigned int iminor(struct inode *inode);  unsigned int imajor(struct inode *inode); struct cdev *i_cdev; Contains a pointer to the data structure that refers to a char device file

Char Device Registration Need to allocate struct cdev to represent char devices #include /* first way */ struct cdev *my_cdev = cdev_alloc(); my_cdev->ops = &my_fops; /* second way, for embedded cdev structure, call this function – (see scull driver) */ void cdev_init(struct cdev *cdev, struct file_operations *fops);

Char Device Registration Either way Need to initialize file_operations and set owner to THIS_MODULE Inform the kernel by calling int cdev_add(struct cdev *dev, dev_t num, unsigned int count); num: first device number count: number of device numbers Remove a char device, call this function void cdev_del(struct cdev *dev);

Device Registration in scull scull represents each device with struct scull_dev struct scull_dev { struct scull_qset *data; /* pointer to first quantum set */ int quantum; /* the current quantum size */ int qset; /* the current array size */ unsigned long size; /* amount of data stored here */ unsigned int access_key; /* used by sculluid & scullpriv */ struct semaphore sem; /* mutual exclusion semaphore */ struct cdev cdev; /* char device structure */ };

Char Device Initialization Steps Register device driver name and numbers Allocation of the struct scull_dev objects Initialization of scull cdev objects Calls cdev_init to initialize the struct cdev component Sets cdev.owner to this module Sets cdev.ops to scull_fops Calls cdev_add to complete registration

Char Device Cleanup Steps Clean up internal data structures cdev_del scull devices Deallocate scull devices Unregister device numbers

Device Registration in scull To add struct scull_dev to the kernel static void scull_setup_cdev(struct scull_dev *dev, int index) { int err, devno = MKDEV(scull_major, scull_minor + index); cdev_init(&dev->cdev, &scull_fops); dev->cdev.owner = THIS_MODULE; dev->cdev.ops = &scull_fops; /* redundant? */ err = cdev_add(&dev->cdev, devno, 1); if (err) { printk(KERN_NOTICE “Error %d adding scull%d”, err, index); }

The open Method In most drivers, open should Check for device-specific errors Initialize the device (if opened for the first time) Update the f_op pointer, as needed Allocate and fill data structure in filp->private_data

The open Method int scull_open(struct inode *inode, struct file *filp) { struct scull_dev *dev; /* device info */ /* #include container_of(pointer, container_type, container_field returns the starting address of struct scull_dev */ dev = container_of(inode->i_cdev, struct scull_dev, cdev); filp->private_data = dev; /* now trim to 0 the length of the device if open was write-only */ if ((filp->f_flags & O_ACCMODE) == O_WRONLY) { scull_trim(dev); /* ignore errors */ } return 0; /* success */ }

The release Method Deallocate filp->private_data Shut down the device on last close One release call per open Potentially multiple close calls per open due to fork/dup scull has no hardware to shut down int scull_release(struct inode *inode, struct file *filp) { return 0; }

scull ’s Memory Usage Dynamically allocated #include void *kmalloc(size_t size, int flags); Allocate size bytes of memory For now, always use GFP_KERNEL Return a pointer to the allocated memory, or NULL if the allocation fails void kfree(void *ptr);

scull ’s Memory Usage Quantum set, SCULL_QSET = 1K quanta SCULL_QUANTUM = 1KB struct scull_qset { void **data; struct scull_qset *next; };

scull ’s Memory Usage int scull_trim(struct scull_dev *dev) { struct scull_qset *next, *dptr; int qset = dev->qset; /* dev is not NULL */ int i; for (dptr = dev->data; dptr; dptr = next) { if (dptr->data) { for (i = 0; i data[i]); kfree(dptr->data); dptr->data = NULL; } next = dptr->next; kfree(dptr); } dev->size = 0; dev->data = NULL; dev->quantum = scull_quantum; dev->qset = scull_qset; return 0; }

Race Condition Protection Different processes may try to execute operations on the same scull device concurrently There would be trouble if both were able to access the data of the same device at once scull avoids this using per-device semaphore All operations that touch the device’s data need to lock the semaphore

Race Condition Protection Some semaphore usage rules No double locking No double unlocking Always lock at start of critical section Don’t release until end of critical section Don’t forget to release before exiting return, break, or goto If you need to hold two locks at once, lock them in a well-known order, unlock them in the reverse order (e.g., lock1, lock2, unlock2, unlock1)

Semaphore Usage Examples Initialization sema_init(&scull_devices[i].sem, 1); Critial section if (down_interruptible(&dev->sem)) return –ERESTARTSYS; scull_trim(dev); /* ignore errors */ up(&dev->sem);

Semaphore vs. Spinlock Semaphores may block Calling process is blocked until the lock is released Spinlock may spin (loop) Calling processor spins until the lock is released Never call “down” unless it is OK for the current thread to block Do not call “down” while holding a spinlock Do not call “down” within an interrupt handler

read and write ssize_t (*read) (struct file *filp, char __user *buff, size_t count, loff_t *offp); ssize_t (*write) (struct file *filp, const char __user *buff, size_t count, loff_t *offp); filp : file pointer buff : a user-space pointer May not be valid in kernel mode Might be swapped out Could be malicious count : size of requested transfer offp : file position pointer

read and write To safely access user-space buffer Use kernel-provided functions #include unsigned long copy_to_user(void __user *to, const void *from, unsigned long count); unsigned long copy_from_user(void *to, const void __user *from, unsigned long count);  Check whether the user-space pointer is valid  Return the amount of memory still to be copied

read and write

The read Method Return values Equals to the count argument, we are done Positive < count, retry 0, end-of-file Negative, check Common errors  - EINTR (interrupted system call)  - EFAULT (bad address) No data, but will arrive later read system call should block

The read Method Each scull_read deals only with a single data quantum I/O library will reiterate the call to read additional data If read position > device size, return 0 (end-of- file)

The read Method ssize_t scull_read(struct file *filp, char __user *buf, size_t count, loff_t *f_pos) { struct scull_dev *dev = filp->private_data; struct scull_qset *dptr; /* the first listitem */ int quantum = dev->quantum, qset = dev->qset; int itemsize = quantum * qset; /* bytes in the listitem */ int item, s_pos, q_pos, rest; ssize_t retval = 0; if (down_interruptible(&dev->sem)) return –ERESTARTSYS; if (*fpos >= dev->size) goto out; if (*f_pos + count > dev->size) count = dev->size - *fpos;

The read Method /* find listitem, qset index, and offset in the quantum */ item = (long) *f_pos / itemsize; rest = (long) *f_pos % itemsize; s_pos = rest / quantum; q_pos = rest % quantum; /* follow the list up to the right position (defined elsewhere */ dptr = scull_follow(dev, item); if (dptr == NULL || !dptr->data || !dptr->data[s_pos]) goto out; /* don’t fill holes */ /* read only up to the end of this quantum */ if (count > quantum – q_pos) count = quantum – q_pos;

The read Method if (copy_to_user(buf, dptr->data[s_pos] + q_pos, count)) { retval = -EFAULT; goto out; } *f_pos += count; retval = count; out: up(&dev->sem); return retval; }

The write Method Return values Equals to the count argument, we are done Positive < count, retry 0, nothing was written Negative, check

The write Method ssize_t scull_write(struct file *filp, const char __user *buf, size_t count, loff_t *f_pos) { struct scull_dev *dev = filp->private_data; struct scull_qset *dptr; int quantum = dev->quantum, qset = dev->qset; int itemsize = quantum * qset; int item, s_pos, q_pos, rest; ssize_t retval = -ENOMEM; /* default error value */ if (down_interruptible(&dev->sem)) return –ERESTARTSYS;

The write Method /* find listitem, qset index and offset in the quantum */ item = (long) *f_pos / itemsize; rest = (long) *f_pos % itemsize; s_pos = rest / quantum; q_pos = rest % quantum; /* follow the list up the right position */ dptr = scull_follow(dev, item);

The write Method if (dptr == NULL) goto out; if (!dptr->data) { dptr->data = kmalloc(qset*sizeof(char *), GFP_KERNEL); if (!dptr->data) { goto out; } memset(dptr->data, 0, qset*sizeof(char *)); } if (!dptr->data[s_pos]) { dptr->data[s_pos] = kmalloc(quantum, GPF_KERNEL); if (!dptr->data[s_pos]) goto out; }

The write Method /* write only up to the end of this quantum */ if (count > quantum – q_pos) count = quantum – q_pos; if (copy_from_user(dptr->data[s_pos] + q_pos, buf, count)) { return –EFAULT; goto out; }

The write Method *f_pos += count; retval = count; /* update the size */ if (dev->size < *f_pos) dev->size = *f_pos; out: up(&dev->sem); return retval; }

readv and writev Vector versions of read and write Take an array of structures Each contains a pointer to a buffer and a length

Playing with the New Devices With open, release, read, and write, a driver can be compiled and tested Use free command to see the memory usage of scull Use strace to monitor various system calls and return values strace ls –l > /dev/scull0 to see quantized reads and writes