Jose Alberto Reguero wrote: >> The flag is there primarily for ICH ahci's. Marvell might be different. >> Care to remove SKIP_D2H_BSY and test a LOT of hotplugging with several >> different devices? :-) > > With SKIP_D2H_BSY I have a old dmesg -> dmesg1 (2.6.20 I think) > I test with and a external sata disk without SKIP_D2H_BSY -> dmes2 > (2.6.21-rc4) > Both takes ~8 seconds. I see. Was the disk spun up when you hotplugged it? The condition doesn't trigger always and more importantly, there is no way to reliably wait for the condition in ahci. ahci's TF status register is read from the received D2H Reg FIS area and there is no mechanism to set the BSY bit on a PHY event, so no matter what we do in the driver, there is an inherent race. ie. we can try to set the BSY bit in the interrupt handler right after a PHY event but the hardware can always beat us and when that happens we set BSY after the first D2H Reg FIS is received which will in turn cause wait timeout, so I'm voting for keeping the flag. Thanks. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
