Designing Interoperability into IA-64 Systems: DIG64 Guidelines

Transcription

1 Designing Interoperability into IA-64 Systems: DIG64 Guidelines Michael Demshki - Intel, DIG64 Chair Melvin Benedict - Compaq, Hardware Architect Dong Wei - Hewlett-Packard, Platform Architect Tomm Aldridge - Intel, Architecture Manager 1

2 Agenda Introduction to DIG64 Guidelines for Migration of Legacy Technology Guidelines for Firmware Guidelines for Core System Getting Involved with the DIG64 2

3 What is an IA-64 system? Solution Operating Systems OSVs Firmware OSVs/IBVs Applications ISVs Software Tools Intel/ISVs/OSVs Processor Intel Chipsets Intel/Industry Hardware, I/O, Storage System Designs OEMs IHVs 3

4 Goals: Developer s Interface Guide for IA-64 Servers (DIG64) Define HW/SW compatibility for IA-64 system solutions: System building blocks SW interfaces Legacy Transitions Enable technology innovation Operating Systems OSVs Processor Intel SOFTWARE Firmware OSVs/IBVs Chipsets Intel/Industry Applications ISVs Hardware, I/O, Storage System Designs OEMs Software Tools Intel/ISVs/OSVs IHVs HARDWARE 4

5 What will DIG64 do? Developer Benefits: Accelerate time-to-market for for IA-64 solutions through concurrent development of of HW HW & SW SW Increase developer efficiency Enable focus on on innovation and and differentiation Provide a technology migration roadmap IT IT Benefits: Increase the the number of of interoperable solutions available to to IT IT Increase reliability of of solutions Lower qualification costs Lower support costs of of obsolete technology 5

6 Who Developed DIG64? Promoters and Contributors* *third party brands and names are the property of their respective owners Sun, Sun Microsystems, and Sun logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the US and other countries 6

7 DIG64 Scope Applications OS OS Loader Software Hardware / Firmware Configuration Pre-OS Boot Firmware Run- Time Services Firmware Interfaces (Configuration, Pre-OS, OS Run-time, Platform) DIG64 Scope Device Interfaces Processor, Chipset IO Bus M e m o r y Core System Components (Processor, Chipset, Memory, I/O Bus, Server Management) Component Interfaces (Networking, Communications, Storage) Technology Migration (Legacy Technologies, Replacement Technologies) 7

8 DIG64 Scope - continued DIG64 Release 1.0 is intended for Itanium - based products There will be subsequent DIG64 releases targeting McKinley and future IA-64 processor generations DIG64 is operating system-independent Oriented toward cross-platform interoperability DIG64 is not bounded by system size, scalability, architecture, or application DIG64 does not address: packaging, form factor, environmental design, or proprietary solutions 8

9 DIG64 Content: Key Standards & Implementation Requirements Standards & Initiatives Servers & Server Solutions ACPI 1.0 ACPI 1.0 EFI PCI PCI EFI RS SAPIC IA-64 USB ANSI Scope limited to published, adopted standards 9

10 DIG64 Product Compliance Compliant products will satisfy all required guidelines Compliance is determined through self testing Test suites and plugfests will be used to facilitate compliance testing A DIG64 web site and marketing programs will be established to promote compliant products 10

11 DIG64 Terminology Required: Features marked as required must be implemented to comply with the DIG64 Recommended: Features marked as recommended need not be implemented to comply with the DIG64, however, implementation is encouraged Optional: Features marked as optional need not be implemented to comply with the DIG64. There should be no dependencies on optional features by other architectural levels. 11

12 Key DIG64 Guidelines DIG64 Scope Configuration Processor, Chipset Applications OS OS Loader FIRMWARE INTERFACE Pre-OS Boot GUIDELINES Device Interfaces CORE SYSTEM GUIDELINES CORE SYSTEM IO Bus Firmware Run- Time Services M e m o r y Software Hardware / Firmware LEGACY MIGRATION GUIDELINES 12

13 Guidelines for Migration of Legacy Technology Melvin Benedict - Compaq, Hardware Architect 13

14 Classic IA-32 Server Design Memory IA-32 Processors Chip Set USB Ports Serial Ports Parallel Port IDE Super IO ISA PCI Slots OS Support DOS* Win98* Win NT* Unix* Linux* K/b and Mouse Ports Floppy Drive BIOS VGA ISA Slot NIC SCSI Definition: Legacy is is the retention of of functions used solely to to support compatibility with older technology. *other brands and names are the property of their respective owners 14

15 Problems with Classic Design Legacy I/O does not scale Slower clock rate and narrow data paths No support for dynamic resource allocation ISA Memory regions Non contiguous memory maps Fixed addresses ISA slot support Uses precious real estate VGA support High end servers moving to headless operation Large OS validation costs 15

16 But, Legacy Removal Does Occur! Lack of usage ISA slots Slow, takes several generations Usually requires a catalyst Check off purchasing The other OEM may still support (fear) IA-64 is a Catalyst! Architectural break in system growth DIG64 accelerates removal process Other Initiatives EASY PC Hardware Design Guide for Microsoft Windows NT Server vers

17 DIG64 Platform and Legacy The retention of legacy in architecture will: Add complexity to new technologies Stifle innovation Add costs DIG64 is the opportunity to make a break with the past Keys to migration Abstraction layers in firmware Extensible Firmware Interface (EFI) boot loader Optional guidelines 17

18 DIG64 Provides Evolution Roadmap Phase out the legacy in servers over time by creating Optional guidelines Feature support is OEM responsibility OEMs dictate own pace of legacy migration Does not forbid features if OEM desires to support Provides a bridge for manufacturing and utilities Abstraction of hardware functions is key enabler EFI boot services at power on of IA-64 systems Abstraction services added over time 18

19 Legacy Removal in the DIG64 Memory Serial Super IO Parallel K/b and Mouse Floppy IDE USB Ports VGA ISA Slot Firmware Core Chip Set Expansion BUS NIC IA-64 Processors SCSI OS Support 64 bit OS 32 bit OS 16 bit OS Guidelines: ISA Expansion Slots Must Not Be Included or Supported Do not include embedded ISA network, storage or graphic adapters 19

20 IA-64 OS support Memory Serial Super IO Parallel K/b and Mouse Floppy USB Ports VGA IDE Firmware Core Chip Set Expansion BUS NIC IA-64 Processors SCSI OS Support 64 bit OS 32 bit OS 16 bit OS Guidelines: EFI Boot loader for 64 bit OS. Required EFI pre-boot environment Recommended EFI option ROM support Recommended 20

21 Non 64bit OS Support Memory Serial Super IO Parallel K/b and Mouse Floppy USB Ports VGA IDE Firmware Core Chip Set Expansion BUS NIC IA-64 Processors SCSI OS Support 64 bit OS 32 bit OS 16 bit OS Guidelines: Optional support for IA-32 Operating Systems Optional support for DOS* and Win98* Operating Systems *other brands and names are the property of their respective owners 21

22 What does this mean? The 64bit platform is NOT required to support non 64 bit OS s for compliance The legacy hardware hooks on the platform can now be removed New 64 bit OS should NOT depend upon legacy hooks! Transition period to allow critical processes time to adjust DOS* is used to support manufacturing tests and other adapter utilities Replace DOS with EFI pre-boot environment *other brands and names are the property of their respective owners 22

23 Legacy I/O Support... Memory Serial Super IO Parallel K/b and Mouse Floppy USB Ports VGA IDE Firmware Core Chip Set Expansion BUS NIC IA-64 Processors SCSI OS Support 64 bit OS 32 bit OS 16 bit OS Guideline: Optional Support for legacy I/O, VGA Utilize IDE, USB, SAPIC, and EFI abstractions 23

24 What does this mean? Serial, parallel, PS2 ports should all be replaced by USB technology USB supports dynamic resource allocation SIO will go the way of the ISA bus Lack of usage! Trend toward headless operation is recognized IDE remains as a useful technology Removable media Abstraction layers insulate the operating systems 24

25 Conclusions Memory DIG64 IDE USB Ports Firmware Core Chip Set IA-64 Processors Expansion BUS NIC SCSI Evolutionary Roadmap for legacy removal Key enablers Abstraction Layers EFI Optional Guidelines for OS s DIG64 is the opportunity 25

26 Key DIG64 Guidelines DIG64 Scope Configuration Processor, Chipset Applications OS OS Loader FIRMWARE INTERFACE Pre-OS Boot GUIDELINES Device Interfaces CORE SYSTEM GUIDELINES CORE SYSTEM IO Bus Firmware Run- Time Services M e m o r y Software Hardware / Firmware LEGACY MIGRATION GUIDELINES 26

27 Guidelines for Firmware Interfaces Dong Wei - Hewlett-Packard, Platform Architect 27

28 Legacy Firmware Model NMI LDR IA-32 OS OS Directly Coupled to HW OS Loader Directly Coupled to HW ACPI BIOS POST & RTS SMM 16 Bit OS/BIOS Interface Saturated Hardware Fixed Address Devices PC-AT Legacy Hardware Processor/Platform Coupled Coupling Slows Down Innovation 28

29 DIG64 Firmware Objectives Enable Boot of IA-64 OSes Decouple the OS and Hardware Development Decouple the Processor and Platform Development Facilitate Technology Migration Support OEM Differentiation Support Platform Scalability, Reliability, and Availability 29

30 DIG64 Firmware Model IA-64 OS MCA LDR OS Abstracted from HW ACPI EFI OS Loader Abstracted from HW RTS MCA System Firmware Uniform Interface Separate Processor & Platform Abstraction Platform Hardware MCA Processor Enable Legacy Removal (e.g., 8259A PIC) EFI = Extensible Firmware Interface ACPI = Advanced Configuration and Power Interface MCA = Machine Check Abort RTS = Runtime Services 30

31 System Firmware IA-64 OS MCA LDR Initialize, Configure and Test the Platform Hardware (UP and MP) EFI Error Recovery (see MCA foils) ACPI RTS MCA System Firmware System Table (e.g., platform features descriptor) Run-time Procedures (e.g., cache flush) Platform Hardware MCA Processor Entry Points (e.g., RESET, CHECK, PMI) Abstract Platform Implementation-specific Features 31

32 System Firmware Guidelines Implementation Provided by OEMs/IBVs Use Run-time Services (RTS) to Access PCI Configuration Space OS Access to PCI Configuration Space not Made Directly to HW Abstract from the CF8h/CFCh CFCh Implementation Provide Resource Locking Enable PCI Segments to Handle >256 Buses 32

33 EFI IA-64 OS MCA LDR Boot & Run-time Services Protocols (e.g., SERIAL_IO) ACPI RTS MCA EFI System Firmware System Partition Boot Manager (Boot Order Menu,...) EFI Drivers EFI Apps (EFI shell, DIAG, MFG,..) Support Legacy-API Free Env. Platform Hardware MCA Processor Evolutionary Path for Legacy Removal Provide an Abstracted Interface to the OS and Enable Technology Migration 33

34 EFI Guidelines EFI Implementation Provided by OEMs/IBVs NV Storage must be Provided for EFI Supports EFI Environment Variables Implement Serial Protocol For Debug Applications and Console Redirection Recommend PXE for Remote Boot Uniform Remote Boot Protocols 34

35 EFI Boot Drivers EFI Provides the Migration Path Non-EFI Option ROM Support is Optional PC-AT Hardware Dependency EFI Option ROM Support is Recommended Enables Legacy Hardware Removal IA-64 Native Instruction Set Model Defined Portable Byte Steam Model is under Investigation Please review EFI presentation at: intel.com/design/ia64/.com/design/ia64/devinfo.htm 35

36 MCA IA-64 OS MCA LDR Check for Error Conditions ACPI EFI Log Errors RTS MCA System Firmware Error Recovery Error Notification Platform Hardware MCA Processor Support More Robust Error Checking and Recovery 36

37 MCA (Cont( Cont.) MCA Implementation Benefits Improved error containment for internal processor errors Many errors are correctable without processor interruption Many errors are recoverable with OS support Abstractions for system error handling Robust error logging for processor and system errors through well-defined structures Enhanced error handling in multiprocessor environments. 37

38 MCA Guidelines Provide Support for Code Resources Robust Error Checking and Recovery Mechanism Use MCA Hooks in Processor, System Firmware and OS Discontinue the PMI (SMI) and NMI Usage Model Provide NV storage for MCA Logging Enable Error Analysis and Recovery 38

39 ACPI ACPI IA-64 OS MCA LDR EFI Server Configuration Mechanism (tables, control methods, IA-64 extensions) RTS MCA System Firmware Obsolete PnP BIOS and MPS Tables Relax ACPI Specification Requirements for Servers (e.g., power button, power policy) Platform Hardware MCA Processor Abstract platform HW from the OS 39

40 ACPI Guidelines ACPI Implementation Provided by OEMs/IBVs Use ACPI for Platform Configuration Use ACPI for Power Management if PM is Supported Provide Multiple SAPIC Description Table Provide PCI Interrupt Routing Info Use ACPI Control Methods for PCI Hot Plug if PHP is Supported 40

41 IA-32 Support Guidelines Provide IA-32 Emulation in System Firmware if: IA-32 Option ROM is Used Portions of POST are Implemented in BIOS 41

42 Conclusions Support DIG64 Firmware Model Decouple the OS and Hardware Development Abstraction of Hardware Implementation and Uniform Interface Decouple the Processor and Platform Development Separate Processor and Platform Abstraction Facilitate Technology Migration Legacy API Removal Legacy Hardware Removal 42

43 Key DIG64 Guidelines DIG64 Scope Configuration Processor, Chipset Applications OS OS Loader FIRMWARE INTERFACE Pre-OS Boot GUIDELINES Device Interfaces CORE SYSTEM IO Bus GUIDELINES Firmware Run- Time Services M e m o r y Software Hardware / Firmware LEGACY MIGRATION GUIDELINES 43

44 Core System Guidelines Tomm Aldridge - Intel, Architecture Manager 44

45 Key elements of a DIG64 Platform OS independent Memory addressability >4GB Designed from ground up to be MP Technology migration enabled in orderly fashion Firmware abstraction of hardware EFI/Firmware Services layers Legacy free boot process Uniform interrupt handling MCA error handling ACPI based configuration Dynamic resource allocation 45

46 System Processors Guidelines: IA-64 Processors System processors must execute the IA- 64 instruction set 46

47 Core Chip Set Core Chip Set IA-64 Processors Guidelines: Must use Symmetric view of system I/O and memory Interrupt delivery mechanism must use the SAPIC compatible programming model Must permit processor to processor interrupt delivery 47

48 Memory Memory Core Chip Set IA-64 Processors Guideline: System should provide for at least 256MB of system memory per attached processor 48

49 Firmware Memory Core Chip Set IA-64 Processors Guidelines: Use EFI (Extensible Firmware Interface) compatible firmware components for IA-64 servers Firmware 49

50 I/O Resources Memory Firmware Core Chip Set I/O Resources IA-64 Processors Guidelines: The hardware implementation of all expansion busses must provide a means for bus agent discovery and identification Use base address registers (BARS) and extent registers to assign system resources 50

51 System Power Considerations Memory System Power Firmware Core Chip Set Expansion BUS IA-64 Processors Guideline: The platform must monitor the status of the primary power source The primary power subsystem should provide hot plug capability The primary power subsystem should provide redundancy 51

52 Networking, Storage and Management Memory System Power Firmware Core Chip Set Expansion BUS NIC IA-64 Processors SCSI Guidelines: Net adapters must be able to transmit packets from buffers aligned on any boundary Option ROMs should use the EFI implementation The platform must provide the capability to log all critical events 52

53 Platform Configuration Memory System Power Firmware Platform Configuration Core Chip Set Expansion BUS NIC IA-64 Processors SCSI Guideline: Provide ACPI hardware for system configuration ACPI control methods to configure devices must be included Support ACPI sleep states : S0 and S5. Recommended to support additional states S2 through S4 53

54 Conclusions Goals supported by core components Common system model which promotes interoperability across various OS s Make migration of applications to IA-64 as easy as possible Enable technology migration DIG64 will intersect the first generation of IA-64 system Many compliant systems will be available at launch of Itanium 54

55 Agenda Introduction to DIG64 Guidelines for Migration of Legacy Technology Guidelines for Firmware Guidelines for Core System Getting Involved with the DIG64 55

56 DIG64 Target Timeline DIG64 DIG64 development development DIG64 Industry DIG64 Review Industry Review DIG64 R1.0 DIG64 R1.0 Become a DIG64 Adopter Now! DIG64 DIG64 OEM, OEM, OSV, OSV, IHV, IHV, ISV ISV adopters adopters DIG64 DIG Compliant Compliant Designs Designs DIG64 DIG64 development development DIG64 DIG Compliant Compliant Products Products Interoperability Interoperability Tools Tools & Events Events DIG64 DIG64 Next Next Release Release 56

57 Becoming a DIG64 Adopter DIG64 Adopters Receive: Early access to future drafts of DIG64 Guidelines Participation in DIG64 interoperability events Promotion of compliant products on DIG64 web site and at DIG64 events Access to DIG64 Adopters web site and tools What s required: Execution of DIG64 Adopters Agreement (one per company) 57

58 DIG64 Guidelines Now Available for Industry Review To review the DIG64 Guidelines document and give your input to the DIG64 working group, go to: Industry review period runs from September 1 through October 31,