![[object Object],[object Object],X64 Workshop – Driving the Platform](https://image.slidesharecdn.com/drivingtheplatform2-100324135844-phpapp01/85/driving-the-platform-2-1-320.jpg)
![Day 1 AM Driving A Platform: Agenda ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Driving The Platform 2
Ähnlich wie Driving The Platform 2 (20)
Driving The Platform 2
- 10. Family - 1st Gen AMD Opteron Systems
- 11. Family - 2 nd Gen AMD Opteron Systems
- 12. AMD Opteron Identification First generation AMD Opteron CPU's use a three digit identifier – XYY; X – Family scalability YY – Relative performance Second generation AMD Opteron CPU's use a four digit identifier – XYZZ; X – Family scalability Y – Socket generation ZZ – Relative performance Model suffixes denote high or low power versions – SE or HE
Hinweis der Redaktion
- Power on -> CPU loads BIOS Boot Program -> POST -> looks for BIOSes on optional cards such as GPU, HDD, etc ->You can break into BIOS at this stage to change or confirm BIOS setting -> memory tests and performs system inventory -> detect plug and play devices -> BIOS searches for a bootable device BIOS determiens whether it is a cold boot or a reboot...if it's a reboot then POST is skipped.
- Global states; G0 normal working G1 is sleep or standby – several levels depending on implementation G2 is soft off – some components retain power – can be woken up by attached device (kbd, etc) – still requires boot so cannot resume OS G3 is mechanical off PIC allows 16 IRQ's APIC requires both IO and Local APICS to create a APIC bus Edge-triggered interrupts result in all associated interrupt sector routines being run against a particular interrupt vector and 'hopes' that whatever caused the interrupt is corrected. Level-triggered interrupts a device 'drives' the signal to it's active level where it is held until serviced, the problem is when you have multiple devices sharing the same interrupt – status change in these devices won't be detected until the original event is serviced.
- We use both IPMI 1.5 (x2100) and IPMI 2.0 IPMI consists of the BMC and satellite controllers around the system, sensors report to the BMC via the IPMB (Intelligent Platform Management Bus – a sort of I2C bus. Adminc use the BMC to remotely control system state
- Galaxy health state = all manage system state remotely only via ipmi, Web and CLI
- KVMS = Keyboard, Video, Mouse & Storage Absolute = grid reference Relative = movement is offset against last known mouse position Relative is considered to allow 'finer' mouse movement but can also lead to mouse jumps and erratic movement.