终端分析.docVIP

终端分析 在linux系统中，所有的输入和输出都尽可能的做成象从普通文件的输入输出一样。但是，终端I/O是比较困难的情况之一。 通常，一个进程通过从它的双亲进程继承文件描述符0,1和2，被自动的附属于一个终端。这时，open()函数已经由进程完成，并且所附属的终端将是该进程的控制终端。 O_CREAT,O_EXCL,O_EXCL,O_TRUCN和O_APPEND标志用到终端文件时没有任何意义。但是，有两个新的标志有用 O_NOCTTY 停止这个终端作为控制终端。 O_NONBLOCK 使open(),read()和write()不被阻塞。 为了简化分析，我们主要分析主机console，即主设备号为4的设备，对应下图的Memory-mapped interface. 各种终端类型： 数据结构 struct tty_struct tty.h 当一个tty打开时，它所有的状态存于此结构。有些信息即使tty关闭了也要维护， 如baud rate,所以它们被存放于另一个结构termios中。tty_struct用一个struct 指向它。由于本结构动态分配，所以它不能大于4096字节。 /* * Where all of the state associated with a tty is kept while the tty * is open. Since the termios state should be kept even if the tty * has been closed for things like the baud rate, etc it is * not stored here, but rather a pointer to the real state is stored * here. Possible the winsize structure should have the same * treatment, but (1) the default 80x24 is usually right and (2) it's * most often used by a windowing system, which will set the correct * size each time the window is created or resized anyway. * IMPORTANT: since this structure is dynamically allocated, it must * be no larger than 4096 bytes. Changing TTY_BUF_SIZE will change * the size of this structure, and it needs to be done with care. * - TYT, 9/14/92 */ struct tty_struct { int magic; struct tty_driver driver; //驱动程序 struct tty_ldisc ldisc; //主要读写都是通过调用ldisc中的函数实现。 struct termios *termios, *termios_locked; int pgrp; //相关进程的组识别号。 int session; //会话号。 kdev_t device; //设备号 unsigned long flags; int count; struct winsize winsize; unsigned char stopped:1, hw_stopped:1, packet:1; unsigned char ctrl_status; struct tty_struct *link; struct fasync_struct *fasync; struct tty_flip_buffer flip;/*用于存放键盘传来的字符*/ int max_flip_cnt; struct wait_queue *write_wait; /*写等待队列*/ struct wait_queue read_wait; /*读等待队列*/ void *disc_data; void *driver_data; #define N_TTY_BUF_SIZE 4096 /* * The following is data for the N_TTY line discipline. For * historical reas