Browse Prior Art Database

S3 logging to check on Enterprise power saving guidelines being followed

IP.com Disclosure Number: IPCOM000029765D
Original Publication Date: 2004-Jul-12
Included in the Prior Art Database: 2004-Jul-12
Document File: 1 page(s) / 6K

Publishing Venue

IBM

Abstract

A method is disclosed to enable enterprise system administrators to check on compliance with corporate energy saving guidelines as they apply to desktop computer usage.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 69% of the total text.

Page 1 of 1

S3 logging to check on Enterprise power saving guidelines being followed

Any major company with 200+ employees incurs considerable expenses associated with powering personal computer systems they own. Often an enterprise will provide employees with systems that have been set up to follow certain power saving schemes (such as "go into low power standby (S3 state) after 20 minutes of inactivity") to accomplish corporate power saving goals. Unfortunately, it is easy for end users to change these schemes and replace the standby state with an entertaining screen saver that kicks in after a period of inactivity and keeps the system in full power mode while it is running. It is also difficult for the IT person to instrument their corporate pre loads to determine how much power they will be drawing. In order to monitor such changes, it may be necessary for the system administrator to actually visit the system to check for changes to the power scheme made by the user. A method of tracking system power usage that is independent of the operating system and immune to end user tampering is needed.

A function is provided by system BIOS that accurately tracks total (life of the product) full power time and total low power standby (S3) time. When the system enters S3 state, a BIOS routine is called that resets and starts a hardware timer that is powered by standby voltage (i.e., voltage that is present during low power states ). When the system exits S3 state and returns to full...