On Fri, May 31, 2013 at 03:18:56AM +0000, Gonglei (Arei) wrote:
IDE_TIMEOUT is defined 32s. But we encountered its timeout in some cases, and then loading disk failed in VM. In order to reduce the probability of timeout, we want to enlarge the IDE_TIMEOUT, such as 120s. We verified this modification worked for us. But we are wondering if this modification may cause other potential issues. Why set IDE_TIMEOUT to 32s? Thanks!
The ATA specification specifies the maximum response time for many commands to be 30 seconds. The extra 2 seconds were thrown in for safety.
-Kevin
Sounds like something that should be commented in the source code.
IDE_TIMEOUT = 32; // 30 seconds per ATA specification +2 seconds thrown in for safety
On Sat, Jun 1, 2013 at 3:21 PM, Kevin O'Connor kevin@koconnor.net wrote:
On Fri, May 31, 2013 at 03:18:56AM +0000, Gonglei (Arei) wrote:
IDE_TIMEOUT is defined 32s. But we encountered its timeout in some cases, and then loading disk failed in VM. In order to reduce the probability of timeout, we want to enlarge the IDE_TIMEOUT, such as 120s. We verified this modification worked for us. But we are wondering if this modification may cause other potential issues. Why set IDE_TIMEOUT to 32s? Thanks!
The ATA specification specifies the maximum response time for many commands to be 30 seconds. The extra 2 seconds were thrown in for safety.
-Kevin
SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios
-
Fred . -
Kevin O'Connor