Oracle Solaris 11.2 设备驱动教程

oracle

需积分: 5 132 浏览量更新于2024-06-24 收藏 873KB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"Oracle Solaris 11.2 Device Driver Tutorial-116 是一份教程文档，主要关注Oracle Solaris 11.2操作系统中的设备驱动程序开发。这份教程可能涵盖了如何编写、调试和管理设备驱动，以确保操作系统与硬件设备的无缝交互。文档由Oracle公司及其关联公司在2012年和2014年发布，并受版权保护，使用者需遵循特定的许可证协议。" Oracle Solaris 11.2是Oracle公司推出的开源操作系统版本，它包含了对最新硬件的支持以及先进的系统管理功能。在Oracle Solaris 11.2中，设备驱动扮演着至关重要的角色，它们是操作系统与硬件设备之间的桥梁，允许操作系统访问并控制硬件资源。设备驱动程序通常分为内核模块和用户空间组件两部分。内核模块直接与硬件交互，处理I/O请求，而用户空间组件则提供系统调用接口，供应用程序使用。在Oracle Solaris 11.2中，开发者可能需要了解以下关键概念： 1. **动态驱动加载（Dynamic Driver Loading）**：Oracle Solaris支持KMF（Kernel Module Framework），允许在运行时加载和卸载设备驱动，提高了系统的灵活性和可维护性。 2. **Solaris DDI（Device Driver Interface）**：DDI是Oracle Solaris提供的设备驱动程序开发接口，它定义了一系列函数调用，用于驱动程序与操作系统内核的交互。 3. **Solaris EVMS（Event Multithreading Services）**：用于设备驱动的事件驱动模型，帮助驱动程序更有效地处理并发事件。 4. **Solaris Zones**：在Oracle Solaris 11.2中，设备驱动可能需要考虑如何在Zone（轻量级虚拟化环境）之间共享和隔离硬件资源。 5. **调试工具**：如`dtrace`，是一个强大的诊断工具，可用于实时分析驱动程序的行为，找出性能瓶颈或错误。 6. **包管理和依赖性**：在Oracle Solaris中，设备驱动通常作为软件包发布，需要正确处理与其他系统组件的依赖关系。 7. **许可证协议**：文档中提到，使用、复制和分发该软件需遵循特定的许可证协议，可能包含对逆向工程、反编译等行为的限制，以保护知识产权。 8. **政府使用条款**：对于美国政府或其他授权使用此软件的实体，可能存在特定的使用条款和限制。通过Oracle Solaris 11.2 Device Driver Tutorial-116，开发者可以学习到如何根据Solaris的DDI规范来编写高效、可靠的设备驱动，理解如何在操作系统内核中注册和管理设备，以及如何处理中断和I/O操作。此外，还可能涉及性能优化、故障排查和驱动程序更新等方面的知识。这份教程对于那些希望深入理解Oracle Solaris内核机制，以及希望在该平台上开发和维护设备驱动的工程师来说，是一份宝贵的参考资料。

资源详情

资源推荐

Kernel Overview

16 Device Driver Tutorial • July 2014

CPU to resume execution of the calling thread. See Chapter 8, “Interrupt Handlers,” in “Writing

Device Drivers for Oracle Solaris 11.2 ”.

Drivers must work with user process (virtual) addresses, system (kernel) addresses, and I/O bus

addresses. Drivers sometimes copy data from one address space to another address space and

sometimes just manipulate address-mapping tables. See “Bus Architectures” in “Writing Device

Drivers for Oracle Solaris 11.2 ”.

User and Kernel Address Spaces on x86 and

SPARC Machines

On SPARC machines, the system panics when a kernel module attempts to directly access user

address space. You must make sure your driver does not attempt to directly access user address

space on a SPARC machine.

On x86 machines, the system does not enter an error state when a kernel module attempts to

directly access user address space. You still should make sure your driver does not attempt

to directly access user address space on an x86 machine. Drivers should be written to be as

portable as possible. Any driver that directly accesses user address space is a poorly written

driver.

Caution - A driver that works on an x86 machine might not work on a SPARC machine because

the driver might access an invalid address.

Do not access user data directly. A driver that directly accesses user address space is using

poor programming practice. Such a driver is not portable and is not supportable. Use the

ddi_copyin(9F) and ddi_copyout(9F) routines to transfer data to and from user address

space. These two routines are the only supported interfaces for accessing user memory.

“Modifying Data Stored in Kernel Memory” on page 77 shows an example driver that uses

ddi_copyin(9F) and ddi_copyout(9F).

The mmap(2) system call maps pages of memory between a process's address space and a file or

shared memory object. In response to an mmap(2) system call, the system calls the devmap(9E)

entry point to map device memory into user space. This information is then available for direct

access by user applications.

Device Drivers

A device driver is a loadable kernel module that manages data transfers between a device and

the OS. Loadable modules are loaded at boot time or by request and are unloaded by request.

Devices as Files

Chapter1 • Introduction to Device Drivers 19

/platform/`uname

-m`/kernel

These modules are specific to the platform identified by the command

uname -m. These modules are specific to a hardware class but more

generic than modules in the uname -i kernel directory.

/usr/kernel

These are user modules. Modules that are not essential to booting belong

in this directory. This tutorial instructs you to put all your drivers in the /

usr/kernel directory.

One benefit of organizing drivers into different directories is that you can selectively load

different groups of drivers on startup when you boot interactively at the boot prompt as shown

in the following example. See the boot(1M) man page for more information.

Type b [file-name] [boot-flags] <ENTER> to boot with options

or i <ENTER> to enter boot interpreter

or <ENTER> to boot with defaults

<<< timeout in 5 seconds >>>

Select (b)oot or (i)nterpreter: b -a

bootpath: /pci@0,0/pci8086,2545@3/pci8086,

Enter default directory for modules [/platform/i86pc/kernel /kernel

/usr/kernel]: /platform/i86pc/kernel /kernel

In this example, the /usr/kernel location is omitted from the list of directories to search

for modules to load. You might want to do this if you have a driver in /usr/kernel that

causes the kernel to panic during startup or on attach. Instead of omitting all /usr/kernel

modules, a better method for testing drivers is to put them in their own directory. Use the

moddir kernel variable to add this test directory to your kernel modules search path. The

moddir kernel variable is described in kernel(1M) and system(4). Another method for

working with drivers that might have startup problems is described in “Device Driver Testing

Tips” on page 106.

Devices as Files

In UNIX, almost everything can be treated as a file. UNIX user applications access devices as

if the devices were files. Files that represent devices are called special files or device nodes.

Device special files are divided into two classes: block devices and character devices. See

“Character and Block Devices” on page 21 for more information.

Every I/O service request initially refers to a named file. Most I/O operations that read or write

data perform equally well on ordinary or special files. For example, the same read(2) system

call reads bytes from a file created with a text editor and reads bytes from a terminal device.

Control signals also are handled as files. Use the ioctl(9E) function to manipulate control

signals.

Devices as Files

20 Device Driver Tutorial • July 2014

Devices Directories

The Oracle Solaris OS includes both /dev and /devices directories for device drivers. Almost

all the drivers in the /dev directory are links to the /devices directory. The /dev directory is

UNIX standard. The /devices directory is specific to the Oracle Solaris OS.

By convention, file names in the /dev directory are more readable. For example, the /dev

directory might contain files with names such as kdb and mouse that are links to files such as /

devices/pseudo/conskbd@0:kbd and /devices/pseudo/consms@0:mouse. The prtconf(1M)

command shows device names that are very similar to the file names in the /devices directory.

In the following example, only selected output of the command is shown.

% prtconf -P

conskbd, instance #0

consms, instance #0

Entries in the /dev directory that are not links to the /devices directory are device nodes or

special files created by mknod(1M) or mknod(2). These are zero-length files that just have a

major number and minor number attached to them. Linking to the physical name of the device

in the /devices directory is preferred to using mknod(1M).

Prior to the Oracle Solaris 10 OS, /devices was an on-disk filesystem composed of

subdirectories and files. Beginning with the Oracle Solaris 10 OS, /devices is a virtual

filesystem that creates these subdirectories and special files on demand.

For more information about the devices file system, see the devfs(7FS) man page.

Device Tree

The device files in the /devices directory are also called the device tree.

The device tree shows relationships among devices. In the device tree, a directory represents

a nexus device. A nexus is a device that can be a parent of other devices. In the following

example, pci@1f,0 is a nexus device. Only selected output from the command is shown.

# ls -l /devices

drwxr-xr-x 4 root sys 512 date time pci@1f,0/

crw------- 1 root sys 111,255 date time pci@1f,0:devctl

You can use prtconf(1M) or prtpicl(1M) to see a graphic representation of the device tree.

See “Overview of the Device Tree” in “Writing Device Drivers for Oracle Solaris 11.2 ” for

more information about the device tree.

剩余115页未读，继续阅读

weixin_40191861_zj

粉丝: 77
资源: 1万+

Oracle Solaris 11.2 设备驱动教程

Oracle Solaris 11.1 Device Driver Tutorial-116

如何删除虚拟环境tutorial-env

有这个报错Error: [Errno 40] Too many levels of symbolic links: '/root/tutorial-env/bin/python'

stable baselines3 tutorial - getting started

bootstrapfx使用教程视频地址

python gui 教程推荐

帮我写一个美妆商城里面的每日一化妆教程页面包括js文件和wxml文件

handsontable中文文档

提供下Oracle官方Java教程

给我一些学习c++stl的教程

servlet参考文献

想学习pandas，有哪些知名的博客或网站呢

Java入门与进阶头歌实验

flask bootstrap 详细案例

ug871-vivado-high-level-synthesis-tutorial.pdf

android13 Its 环境搭建

JAVA图书管理系统MySQL创建GUI代码

用自动化编码器实现低剂量CT重建pytorch代码

Unity VEG学习视频推荐

最新资源