BIOS与硬盘ppt课件_第1页
BIOS与硬盘ppt课件_第2页
BIOS与硬盘ppt课件_第3页
BIOS与硬盘ppt课件_第4页
BIOS与硬盘ppt课件_第5页
已阅读5页,还剩55页未读 继续免费阅读

下载本文档

版权说明:本文档由用户提供并上传,收益归属内容提供方,若内容存在侵权,请进行举报或认领

文档简介

1、BIOS与硬盘产品工程部马翀 硬盘的故事 SAS/SATA规范引见 BIOS启动规范 硬盘分区格式 BIOS的硬盘接口总结 & 回答以下问题硬盘的故事 - IDE/ATAIDE并不是第一个将控制器集成到硬盘中的技术- 广达(Quantum)推出了3.5 inch Hard card, 但是有很多的问题- 将硬盘控制器整体放在独立的硬盘坞上,经过线缆直接衔接到系统总线上1986年,Compaq与两家公司协作研发出现代IDE的前身,这两家公司分别是:- Western Digital(西数)- Control Data Corporation , 如今属于Seagate(希捷) 1990年,ANS

2、I经过了AT Attachment Interface审查并发布了第一个ATA规范,ATA-1IDE/ATAProgrammed I/O (PIO) ModesIDE/ATADirect Memory Access (DMA) Modes and Bus Mastering DMABlock Transfers- 添加了支持块传输的命令,由此提高性能Logical Block Addressing (LBA)- 支持“逻辑块地址, LBA的运用同时也需求BIOS端的支持Improved Identify Drive Command - 允许软件经过指令的方式来获取硬盘包括几何以及各方面参数的详

3、细信息Faster PIO ModesFaster DMA ModesATA - 2Improved Reliability- 添加了高速数据传输的可靠性Self-Monitoring Analysis and Reporting Technology (SMART)- Head Flying Height- Number of Remapped Sectors- ECC Use and Error Counts- Spin-Up Time- Temperature- Data ThroughputSecurity Feature- 使硬盘具有加密维护的功能ATA - 3ATAPI AT At

4、tachment Packet Interface -SFF - Small Form Factor committee 首先提出ATAPI规范,使得非硬盘类设备可以在ATA接口下运用ATAPI协议进展任务,如光驱,磁带驱动器,软驱 -90年代末期, T13接手了ATAPI的命令集以及协议Cyclical Redundancy Checking (CRC)High-Performance IDE CableUltra DMA (UDMA) ModesATA/ATAPI - 4CHS Cylinder-Head-SectorCHS & LBA C Cylinder 10-bit, 0 1023

5、H Head 8-bit, 0 255 S Sector 6-bit, 1 63通常8G是BIOS中可以寻址的上限, 8GB = 8192MB并不准确,准确的上限是8192 256 * 1024 * 512MBCHS to LBA mappingBefore ATA/ATAPI 7- T13 - INCITS - ANSIAfter ATA/ATAPI 7 Comes up- 有太多版本的ATA/ATAPI ATA/ATAPIsSATA-IO: Serial ATA International Organization 硬盘的故事 - SATASATA Revision 1.0- 1.5G/s

6、速度,不支持NCQ- 吞吐率峰值和PATA/133接近- 硬盘同时具有两种电源接口- 8b/10b编码AHCI Advanced Host Controller Interface- AHCI是一种PCI类设备,用于在系统内存与SATA设备间传输数据 - AHCI最多支持32个端口 - 支持ATA和ATAPI设备,且需求具有PIO和DMA传输方式 - AHCI可以选择支持传统I/O区间,或者Native IDE/Bus Master IDESATA Rev 1.0 & AHCIBDA BIOS Data AreaBus Master IDE/Native IDESATA 2.0相比于上一个版本

7、在速度上有很大提升SATA 3.0- 6Gbit/s 可伸缩速度- 依然可以经过SAS STP协议兼容SAS控制器- isochronous NCQ- 提升电源管理才干- LIF 1.8寸兼容接口- 与 INCITS-ACS规范同步SATA Rev 2.0/SATA Rev 3.0硬盘的故事 - SCSISCSI从SASI承继而来,Shugart Associate System Interface;1982年,ANSI开发了SASI规范,后更名为SCSI;SCSI 是一种智能的点对点接口,它隐藏了物理格式的复杂性同一总线可以支持8到16块硬盘从1986年开场,SCSI被Amiga, Appl

8、e Macintosh和Sun公司的电脑产品线以及PC效力器系统;很多厂商在低端产品线上依然选择PATAT10担任实践的开发任务SCSI - Small Computer System InterfaceATA & SCSI Hot SwappingBandwidth 5120 Mbit/sWidth16-bitConnector68-pins; 80-pinsAlternativeUltra-5SpecSCSI-3 SPI-5 (2003)Clock160 MHz DDRParallel SCSI Ultra-640 SCSI硬盘的故事 Serial SCSISerial attached

9、SCSI运用作过修正的SATA数据线和电源线,但需求SAS控制器支持iSCSIiSCSI运用网络物理硬件,普通是以太网接口和线缆作为物理层传输USB Attached SCSI运用USB作为物理层传输数据FC-ALFiber Channel Serial SCSISAS/SATA 规范引见SAS Protocol LayerSAS Physical LayerSAS Physical LayerPHY层定义了8b10b编码以及OOB信号- 将8比特编码成含有十个比特的字符- 字母符号具有特殊的意义,它包括描画信息以及控制变量SAS PHY LayerSAS PHY LayerSATA OOB

10、SequenceSAS PHY Layer OOBSAS To SATA PHY OOB SequenceSAS PHY Layer - OOBSAS To SAS PHY OOB SequenceCOMSAS Burst ProcessSAS Speed NegationSATA Speed NegationPrimitivesPrimitives是第一个字符为K28.3或者K28.5的双字SAS Link LayerAddress Frames Address frames are used for the identification sequence and for connectio

11、n requests.a) performs and identification sequence by transmitting an IDENTIFY address frame b) performs a hard reset sequence by transmitting a HARD_RESET primitive sequenceConnectionsOverviewSAS Port LayerState Machine ExampleHow To Bind A Disk Notation To Its Relative PhyID- How Linux Kernel Allo

12、cates Disk Notation?- How Linux Kernel Notifies Disk Notation Allocation Program When A Disk Is Found?- Why The Sequence Is Still Disordered Even If We Do Not Hot Plug?- W/A To Bind?ExampleAnalysisOverviewSAS Transport LayerSSPSTP A SATA device phy transmits a Register - Device to Host FIS after com

13、pleting the link reset sequence The expander device shall update a set of shadow registers with the contents of this FIS and shall not deliver it to any STP initiator port. SMP initiator ports may read the shadow register contents using the SMP REPORT PHY SATA function The expander device originates

14、 a Broadcast(Change) after receiving the Register - Device to Host FISSMPSCSI application layer- SCSI transport protocol services- Application client error handling- Device server error handling- Task router and task manager error handling- SCSI transport protocol event notifications- SCSI commands-

15、 SCSI mode parameters- SCSI log parameters- SCSI diagnostic parameters- SCSI power conditions- SCSI vital product dataATA application layerManagement application layer- READY LED signal behavior- Management protocol services- SMP functionsSAS Application LayerSATA Speed NegationSATA Speed NegationBI

16、OS 启动规范BIOS Boot Specification The purpose of this specification is to describe a methodology by which the BIOS willidentify all IPL (Initial Program Load) devices in the system, prioritize them in theorder the user selects, and then sequentially go through each device and attempt toboot. The BIOS m

17、ust become more intelligent about booting because the Plug andPlay BIOS Specification places additional requirements on the BIOS during the bootprocess, and there are now more devices that are bootable such as CD-ROM, networkremote boot, PCMCIA, etc. It is important that this specification define a

18、boot schemethat is generic and flexible enough to allow booting from virtually any existing IPLdevice, and for the definition of future IPL devices as well.IPL Device An Initial Program Load Device is any device in the system that can boot and load an O/S. In standard AT machines, this is the floppy

19、 drive or hard drive.BAIDA BIOS Aware IPL Device is any device that can boot an O/S, but requires the BIOS to have specific code to support it. Some examples are: the first floppy drive, the first hard drive, ATAPI CD-ROM, PCMCIA, embedded network adapter, etc.BDAThe BIOS Data Area is a data storage

20、 area in RAM. The BDA is used by the BIOS to manage the various peripherals and resources in the system. The BDA starts at segment address 0040h.BCVA Boot Connection Vector is a pointer that points to code inside the option ROM that will perform device initialization, detect if a peripheral (such as

21、 a SCSI hard drive) is attached, and optionally hook INT 13h. The BCV resides in a PnP option ROM Expansion Header. An example of an option ROM with a BCV is a PnP ISA SCSI controller.BEVA Bootstrap Entry Vector is a pointer that points to code inside an option ROM that will directly load an O/S. Th

22、e BEV resides in a PnP option ROM Expansion Header. An example of an option ROM with a BEV is a PnP ISA ethernet controller.PnPPlug and Play is a term used to identify anything defined by the Plug and Play BIOS specification or the Plug and Play ISA specification. The term will typically be used to

23、reference some device or behavior that is specific to PnP technology.BIOS Boot Specification - Terms BAIDs包括第一个软驱、第一个硬盘以及BIOS内置所支持的设备,BIOS经过int19来启动OSDevices with PnP Expansion Header需求有一个Option ROM,并且有55AA的签名;OpROM将会被加载在内存的C0000hEFFFFh并且2K对齐;ROM中带有PnP扩展头,内部含有重要的配置信息Legacy IPL Devices规范ISA卡,具有一个Opti

24、on ROM, 有55AA的签名;OpROM将会被加载在内存的C0000hEFFFFh并且2K对齐;有能够会Hook INT19BIOS Boot Specification - IPL 当系统BIOS识别或枚举了一切的BAIDs和BEV设备后,需求确定的是选择哪一个设备来启动,这就需求由IPL Priority来决议;BBS IPL PriorityBIOS会将IPL Priority存储在NV Memory中,当BIOS调用INT19时,会把优先级读取出来,按照顺序进展启动,当一个设备启动失败后会经过调用INT18将控制权还给系统BIOS,然后尝试启动下一个设备;Example为了完全控制

25、IPL设备启动的顺序,就需求控制INT13的安装顺序,首先被安装INT13的设备,将会被分配到更小的硬盘号80,81An INT 13h Device Controller installs one or more drives into the BIOS INT 13h services by hooking the INT 13h software interrupt and chaining to the old vector.Each controller may install INT 13h support for one or more drives.When INT 13h i

26、s hooked, the old vector will be saved.A controller will only respond to requests which specify the drive number for which it has control, and will pass on requests to other drive numbers to the old vector.A controller may not know if it has any drives attached until it is called to install. If no d

27、rives are attached, then the controller should not hook INT 13h.The number of hard drives currently installed is stored in the BDA at address 0040:0075. When a controller installs support for additional drives, this location must be incremented by the number of drives that are to be added.A controll

28、er must install INT 13h support by using sequentially increasing drive numbers starting after the drives previously installed. For example, if two drives are already installed when the controller gets called, they will occupy drive numbers 80h and 81h. The next available numbers for the controller t

29、o occupy would be 82h, 83h, etc.A controller checks if the location at 0040:0075 is zero to determine if it is the first to install. If it is first, the controller must copy the INT 13h vector over the INT 40h vector so that floppy services are handled properly.The first controller to install will g

30、et drive number 80h. The controller then knowsthat it controls the hard drive boot device.BBS BCV PriorityBIOS Boot Specification PnP headerPnP header example SCU OpROMsignatureEntry PointPNP Header OffsetPNP Header SignatureSCU Identify which PHY the disk associates to硬盘分区格式存储设备包括软盘,光驱,硬盘等第一个扇区,大小为

31、512字节MBR Master Boot RecordPartition ID- 0 x1 FAT12; 0 x4 FAT16; 0 x7 NTFS; 0 x8E Linux LVM; 0 xEE EFI Protective MBR由于位数限制,MBR只能支持 = 2.199TB,导致以MBR为根底的底盘分区方式无法支持2.2TB以上的硬盘;GPT分区格式可以支持 ,是EFI规范的一部分,目前UEFI为根底的BIOS均支持GPT分区格式;GPT GUID Partition TableHybrid GPT/MBR- Protective MBR可以支持3个主分区- Windows 2021R2运用了Hybrid GPT/MBRBIOS的硬盘接口INT19Legacy - INT 19Intel Ethernet CardINT 13HLegacy INT 13EFI BIOS Hard Drive ArchitectureBoot ManagerDXE CoreLoad File ProtocolSimple File ProtocolEFI FILE ProtocolMBRGPTEL ToritoEFI Block I/O ProtocolDisk I

温馨提示

  • 1. 本站所有资源如无特殊说明,都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
  • 2. 本站的文档不包含任何第三方提供的附件图纸等,如果需要附件,请联系上传者。文件的所有权益归上传用户所有。
  • 3. 本站RAR压缩包中若带图纸,网页内容里面会有图纸预览,若没有图纸预览就没有图纸。
  • 4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
  • 5. 人人文库网仅提供信息存储空间,仅对用户上传内容的表现方式做保护处理,对用户上传分享的文档内容本身不做任何修改或编辑,并不能对任何下载内容负责。
  • 6. 下载文件中如有侵权或不适当内容,请与我们联系,我们立即纠正。
  • 7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

最新文档

评论

0/150

提交评论