| Message ID | 20130805193753.9260.35206.stgit@bling.home (mailing list archive) |
|---|---|
| State | New, archived |
| Delegated to: | Bjorn Helgaas |
| Headers | show |
On 08/05/2013 12:37 PM, Alex Williamson wrote: > The PCI spec indicates that with stable power, reset needs to be > asserted for a minimum of 1ms (Trst). Seems like we should be able > to assume power is stable for a runtime secondary bus reset. The > current code has always used 100ms with no explanation where that > came from. The aer_do_secondary_bus_reset() function uses 2ms, but > that seems to be a misinterpretation of the PCIe spec, where hot > reset is implemented by TS1 ordered sets containing the hot reset > command. After a 2ms delay the state machine enters the detect state, > but to generate a link down, only two consecutive TS1 hot reset > ordered sets are requred. 1ms should be plenty for that. The reason for doing a 2ms sleep is because the are supposed to be sending the Hot Reset TS1 Ordered-Sets continuously for 2ms per all of the documents I have read. The 1ms number you quote is the minimum time for a conventional PCI bus. I'm not completely sure of that applies as well to PCIe, nor does it represent the maximum recommended value. If we stop early we risk not resetting the full device tree on the secondary bus which is the bug I was resolving by adding the 2ms delay. Previously we saw that some devices were only getting their PCIe link retrained without performing a hot reset when the bit was not held for long enough. I would prefer to keep this at 2 ms in order to account for the fact that PCIe has to go though link recovery states before it can perform the hot reset. Thanks, Alex -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, 2013-08-06 at 16:27 -0700, Alexander Duyck wrote: > On 08/05/2013 12:37 PM, Alex Williamson wrote: > > The PCI spec indicates that with stable power, reset needs to be > > asserted for a minimum of 1ms (Trst). Seems like we should be able > > to assume power is stable for a runtime secondary bus reset. The > > current code has always used 100ms with no explanation where that > > came from. The aer_do_secondary_bus_reset() function uses 2ms, but > > that seems to be a misinterpretation of the PCIe spec, where hot > > reset is implemented by TS1 ordered sets containing the hot reset > > command. After a 2ms delay the state machine enters the detect state, > > but to generate a link down, only two consecutive TS1 hot reset > > ordered sets are requred. 1ms should be plenty for that. > > The reason for doing a 2ms sleep is because the are supposed to be > sending the Hot Reset TS1 Ordered-Sets continuously for 2ms per all of > the documents I have read. Could you point to one of those references? In the PCIe v3 spec I'm seeing things like 4.2.6.11 Hot Reset: * If two consecutive TS1 Ordered Sets are received on any Lane with the Hot Reset bit asserted and configured Link and Lane numbers, then: * LinkUp = 0b (False) * If no higher Layer is directing the Physical Layer to remain in Hot Reset, the next state is Detect * Otherwise, all Lanes in the configured Link continue to transmit TS1 Ordered Sets with the Hot Reset bit asserted and the configured Link and Lane numbers. * Otherwise, after a 2 ms timeout next state is Detect. The next section has something similar for propagation of hot resets. Nowhere there does it say TS1 Ordered Sets need to be sent continuously for 2ms. A hot reset is initiated only by two consecutive TS1 Ordered Sets with the Hot Reset bit asserted. The 2ms timeout seems to be the delay before the link moves to the Detect state after we stop asserting hot reset. 1ms seems like more than enough time for two TS1 Ordered Sets to propagate down a multi-level hierarchy at 2.5GT/s. > The 1ms number you quote is the minimum time > for a conventional PCI bus. I'm not completely sure of that applies as > well to PCIe, nor does it represent the maximum recommended value. Correct, 1ms comes from conventional PCI. PCIe is designed to be software compatible with conventional PCI so it makes sense that PCIe would do something within the timing boundaries of conventional PCI. I didn't see any reference to a maximum recommended value for this parameter. > If we stop early we risk not resetting the full device tree on the > secondary bus which is the bug I was resolving by adding the 2ms delay. > Previously we saw that some devices were only getting their PCIe link > retrained without performing a hot reset when the bit was not held for > long enough. I would prefer to keep this at 2 ms in order to account > for the fact that PCIe has to go though link recovery states before it > can perform the hot reset. I'm not going to sweat over 1ms or 2ms but I do want to be able to document why we're setting it to one or the other. If it's warm fuzzies, so be it, but I'd prefer if we could find actual spec or hardware examples to back it up. Thanks, Alex -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 08/06/2013 07:56 PM, Alex Williamson wrote: > On Tue, 2013-08-06 at 16:27 -0700, Alexander Duyck wrote: >> On 08/05/2013 12:37 PM, Alex Williamson wrote: >>> The PCI spec indicates that with stable power, reset needs to be >>> asserted for a minimum of 1ms (Trst). Seems like we should be able >>> to assume power is stable for a runtime secondary bus reset. The >>> current code has always used 100ms with no explanation where that >>> came from. The aer_do_secondary_bus_reset() function uses 2ms, but >>> that seems to be a misinterpretation of the PCIe spec, where hot >>> reset is implemented by TS1 ordered sets containing the hot reset >>> command. After a 2ms delay the state machine enters the detect state, >>> but to generate a link down, only two consecutive TS1 hot reset >>> ordered sets are requred. 1ms should be plenty for that. >> The reason for doing a 2ms sleep is because the are supposed to be >> sending the Hot Reset TS1 Ordered-Sets continuously for 2ms per all of >> the documents I have read. > Could you point to one of those references? In the PCIe v3 spec I'm > seeing things like 4.2.6.11 Hot Reset: > > * If two consecutive TS1 Ordered Sets are received on any Lane > with the Hot Reset bit asserted and configured Link and Lane > numbers, then: > * LinkUp = 0b (False) > * If no higher Layer is directing the Physical Layer to > remain in Hot Reset, the next state is Detect > * Otherwise, all Lanes in the configured Link continue to > transmit TS1 Ordered Sets with the Hot Reset bit > asserted and the configured Link and Lane numbers. > * Otherwise, after a 2 ms timeout next state is Detect. > > The next section has something similar for propagation of hot resets. > > Nowhere there does it say TS1 Ordered Sets need to be sent continuously > for 2ms. A hot reset is initiated only by two consecutive TS1 Ordered > Sets with the Hot Reset bit asserted. The 2ms timeout seems to be the > delay before the link moves to the Detect state after we stop asserting > hot reset. 1ms seems like more than enough time for two TS1 Ordered > Sets to propagate down a multi-level hierarchy at 2.5GT/s. > My original implementation is actually based on page 536 of the "PCI Express System Architecture". However based on the PCIe spec itself I think the point is that the port is supposed to stay in Hot Reset for 2ms after receiving the in-band message. For a bridge port it means that is supposed to be sending the Hot Reset message for those 2ms on all downstream facing ports. After the timer expires then it stops sending the Hot Reset TS1 Ordered Sets and then will transition to the Detect state. My main concern here is that the previous code was not triggering a Hot Reset on all ports previously. What was happening was that some of the ports would only get as far as Recovery as the upstream port was only sending a couple of TS1 frames and not allowing the downstream ports time to switch to Recovery themselves and discover the Hot Reset. >> The 1ms number you quote is the minimum time >> for a conventional PCI bus. I'm not completely sure of that applies as >> well to PCIe, nor does it represent the maximum recommended value. > Correct, 1ms comes from conventional PCI. PCIe is designed to be > software compatible with conventional PCI so it makes sense that PCIe > would do something within the timing boundaries of conventional PCI. I > didn't see any reference to a maximum recommended value for this > parameter. I don't want to implement things to minimum specification as there are too many marginal parts where the minimum doesn't work. I would rather not have to add a ton of quirks for all of the parts out there that didn't quite meet up to the specification. By using a value of 2ms we are matching what the PCIe bridge behavior is supposed to be by sending the Hot Reset TS1 ordered sets for 2ms. >> If we stop early we risk not resetting the full device tree on the >> secondary bus which is the bug I was resolving by adding the 2ms delay. >> Previously we saw that some devices were only getting their PCIe link >> retrained without performing a hot reset when the bit was not held for >> long enough. I would prefer to keep this at 2 ms in order to account >> for the fact that PCIe has to go though link recovery states before it >> can perform the hot reset. > I'm not going to sweat over 1ms or 2ms but I do want to be able to > document why we're setting it to one or the other. If it's warm > fuzzies, so be it, but I'd prefer if we could find actual spec or > hardware examples to back it up. Thanks, > > Alex I think our difference is that I based my value on the in-band message behavior and your value is based on the recommended minimum time for the Secondary Bus Reset. The downstream ports of a bridge that receives the in-band Hot Reset notification are supposed to send a continuous stream of TS1 Ordered sets with the Hot Reset bit set for 2ms. Based on all of the conditions in the spec the device should start a 2ms timer, and all downstream ports should begin transmitting the TS1 Ordered sets with the Hot Reset bit asserted, then after the 2ms timer expires it should switch to the detect state. I verified with a PCIe analyzer that this was what the AER code was doing after I had changed it and added the sleep. What I found is that most parts will stop transmitting the TS1 ordered sets as soon as you clear the Secondary Bus Reset bit. So if you set the bit and clear it 1 ms later you might only get to send a few ordered sets and that may not be enough depending on how fast the part can transition between L0/L0s/L1, Recovery, and Hot Reset. Thanks, Alex -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, 2013-08-07 at 11:30 -0700, Alexander Duyck wrote: > On 08/06/2013 07:56 PM, Alex Williamson wrote: > > On Tue, 2013-08-06 at 16:27 -0700, Alexander Duyck wrote: > >> On 08/05/2013 12:37 PM, Alex Williamson wrote: > >>> The PCI spec indicates that with stable power, reset needs to be > >>> asserted for a minimum of 1ms (Trst). Seems like we should be able > >>> to assume power is stable for a runtime secondary bus reset. The > >>> current code has always used 100ms with no explanation where that > >>> came from. The aer_do_secondary_bus_reset() function uses 2ms, but > >>> that seems to be a misinterpretation of the PCIe spec, where hot > >>> reset is implemented by TS1 ordered sets containing the hot reset > >>> command. After a 2ms delay the state machine enters the detect state, > >>> but to generate a link down, only two consecutive TS1 hot reset > >>> ordered sets are requred. 1ms should be plenty for that. > >> The reason for doing a 2ms sleep is because the are supposed to be > >> sending the Hot Reset TS1 Ordered-Sets continuously for 2ms per all of > >> the documents I have read. > > Could you point to one of those references? In the PCIe v3 spec I'm > > seeing things like 4.2.6.11 Hot Reset: > > > > * If two consecutive TS1 Ordered Sets are received on any Lane > > with the Hot Reset bit asserted and configured Link and Lane > > numbers, then: > > * LinkUp = 0b (False) > > * If no higher Layer is directing the Physical Layer to > > remain in Hot Reset, the next state is Detect > > * Otherwise, all Lanes in the configured Link continue to > > transmit TS1 Ordered Sets with the Hot Reset bit > > asserted and the configured Link and Lane numbers. > > * Otherwise, after a 2 ms timeout next state is Detect. > > > > The next section has something similar for propagation of hot resets. > > > > Nowhere there does it say TS1 Ordered Sets need to be sent continuously > > for 2ms. A hot reset is initiated only by two consecutive TS1 Ordered > > Sets with the Hot Reset bit asserted. The 2ms timeout seems to be the > > delay before the link moves to the Detect state after we stop asserting > > hot reset. 1ms seems like more than enough time for two TS1 Ordered > > Sets to propagate down a multi-level hierarchy at 2.5GT/s. > > > > My original implementation is actually based on page 536 of the "PCI > Express System Architecture". However based on the PCIe spec itself I > think the point is that the port is supposed to stay in Hot Reset for > 2ms after receiving the in-band message. For a bridge port it means > that is supposed to be sending the Hot Reset message for those 2ms on > all downstream facing ports. After the timer expires then it stops > sending the Hot Reset TS1 Ordered Sets and then will transition to the > Detect state. Conveniently page 536 is available for preview on google :) What that suggests to me is that the minimum "nobody home", unconnected link timeout is 2ms. Downstream ports may exit to the Detect state after either a 2ms timeout expires or after two hot-reset-TS1s are received from the downstream device. The other 2ms case is that an upstream port in the Hot Reset state will always wait for the 2ms timeout to expire after the last pair of hot-reset-TS1s is received before entering the Detect state. > My main concern here is that the previous code was not triggering a Hot > Reset on all ports previously. What was happening was that some of the > ports would only get as far as Recovery as the upstream port was only > sending a couple of TS1 frames and not allowing the downstream ports > time to switch to Recovery themselves and discover the Hot Reset. Was that the original code that had no delay between set and clear of the bridge control register? 1ms is pretty long time vs no delay. > >> The 1ms number you quote is the minimum time > >> for a conventional PCI bus. I'm not completely sure of that applies as > >> well to PCIe, nor does it represent the maximum recommended value. > > Correct, 1ms comes from conventional PCI. PCIe is designed to be > > software compatible with conventional PCI so it makes sense that PCIe > > would do something within the timing boundaries of conventional PCI. I > > didn't see any reference to a maximum recommended value for this > > parameter. > > I don't want to implement things to minimum specification as there are > too many marginal parts where the minimum doesn't work. I would rather > not have to add a ton of quirks for all of the parts out there that > didn't quite meet up to the specification. By using a value of 2ms we > are matching what the PCIe bridge behavior is supposed to be by sending > the Hot Reset TS1 ordered sets for 2ms. The minimum requirement is 2 hot-reset-TS1. We're sending ~2.5 million (if we can assume 1 per transfer cycle). > >> If we stop early we risk not resetting the full device tree on the > >> secondary bus which is the bug I was resolving by adding the 2ms delay. > >> Previously we saw that some devices were only getting their PCIe link > >> retrained without performing a hot reset when the bit was not held for > >> long enough. I would prefer to keep this at 2 ms in order to account > >> for the fact that PCIe has to go though link recovery states before it > >> can perform the hot reset. > > I'm not going to sweat over 1ms or 2ms but I do want to be able to > > document why we're setting it to one or the other. If it's warm > > fuzzies, so be it, but I'd prefer if we could find actual spec or > > hardware examples to back it up. Thanks, > > > > Alex > > I think our difference is that I based my value on the in-band message > behavior and your value is based on the recommended minimum time for the > Secondary Bus Reset. The downstream ports of a bridge that receives the > in-band Hot Reset notification are supposed to send a continuous stream > of TS1 Ordered sets with the Hot Reset bit set for 2ms. Based on all of > the conditions in the spec the device should start a 2ms timer, and all > downstream ports should begin transmitting the TS1 Ordered sets with the > Hot Reset bit asserted, then after the 2ms timer expires it should > switch to the detect state. I verified with a PCIe analyzer that this > was what the AER code was doing after I had changed it and added the sleep. > > What I found is that most parts will stop transmitting the TS1 ordered > sets as soon as you clear the Secondary Bus Reset bit. If what I state above is correct, then the downstream port of the Bridge is able to immediately move to Detect after it receives two hot-reset-TS1s from the downstream device. I suspect this is what you were seeing. > So if you set > the bit and clear it 1 ms later you might only get to send a few ordered > sets and that may not be enough depending on how fast the part can > transition between L0/L0s/L1, Recovery, and Hot Reset. I would guess what you were seeing previously with a back-to-back set/clear of the bridge control register was that the bridge never really entered Hot Reset. Perhaps it wasn't even set long enough to be latched into the hardware. As long as we get the bridge to enter Hot Reset, I think the protocol takes care of itself. For example: root port switch endpoint +-----+ +-----+ +-----+ | X |<---A'----| Y |<---B'----| Z | | |----A---->| |----B---->| | +-----+ +-----+ +-----+ Say root port X makes it into the Hot Reset state and we have some way to immediately detect this and clear the bridge control register. X will still continue to send hot-reset-TS1 until either a) the 2ms timer expires or b) it receives two hot-reset-TS1s on link A'. If link A is up, switch Y will certainly receive two host-reset-TS1s within that 2ms and enters the Hot Reset state on it's upstream port. Switch Y then begins sending hot-reset-TS1s on link A'. At the same time, Y directs it's downstream ports to enter Hot Reset "as soon as possible", and begins sending hot-reset-TS1s on link B. Once X receives two hot-reset-TS1s on link A', X enters the Detect state. hot-reset-TS1s on link A cease. 2ms after the upstream port of Y receives the last two hot-reset-TS1s, those ports also enter the detect phase. The downstream port of Y behaves the same. We left off with Y's downsteam port in Hot Reset sending hot-reset-TS1s down link B. It continues to do this for 2ms or until two hot-reset-TS1s are received on link B'. The protocol takes care of propagating the Hot Reset to subordinate devices regardless of whether we're still directing the original bridge to stay in Hot Reset. If the above is a correct interpretation, the the only requirement on how long we assert the secondary bus reset bit is how long it takes the bridge to enter the Hot Reset state. Intuitively, 1ms seems like more than enough time and is software compatible with conventional PCI which is generally a design goal for PCIe. If we factor in link recovery time, the maximum L1 latency is 64us, which is a pretty small fraction of 1ms. Did you experiment at all with 1ms? I'm trying to come up with a reason to make it 2ms, but the spec isn't supporting it. Maybe the comment should be "This could probably be 1ms, but we're more comfortable with 2ms.". Thanks, Alex -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 08/07/2013 10:23 PM, Alex Williamson wrote: > On Wed, 2013-08-07 at 11:30 -0700, Alexander Duyck wrote: >> On 08/06/2013 07:56 PM, Alex Williamson wrote: >>> On Tue, 2013-08-06 at 16:27 -0700, Alexander Duyck wrote: >>>> On 08/05/2013 12:37 PM, Alex Williamson wrote: >>>>> The PCI spec indicates that with stable power, reset needs to be >>>>> asserted for a minimum of 1ms (Trst). Seems like we should be able >>>>> to assume power is stable for a runtime secondary bus reset. The >>>>> current code has always used 100ms with no explanation where that >>>>> came from. The aer_do_secondary_bus_reset() function uses 2ms, but >>>>> that seems to be a misinterpretation of the PCIe spec, where hot >>>>> reset is implemented by TS1 ordered sets containing the hot reset >>>>> command. After a 2ms delay the state machine enters the detect state, >>>>> but to generate a link down, only two consecutive TS1 hot reset >>>>> ordered sets are requred. 1ms should be plenty for that. >>>> The reason for doing a 2ms sleep is because the are supposed to be >>>> sending the Hot Reset TS1 Ordered-Sets continuously for 2ms per all of >>>> the documents I have read. >>> Could you point to one of those references? In the PCIe v3 spec I'm >>> seeing things like 4.2.6.11 Hot Reset: >>> >>> * If two consecutive TS1 Ordered Sets are received on any Lane >>> with the Hot Reset bit asserted and configured Link and Lane >>> numbers, then: >>> * LinkUp = 0b (False) >>> * If no higher Layer is directing the Physical Layer to >>> remain in Hot Reset, the next state is Detect >>> * Otherwise, all Lanes in the configured Link continue to >>> transmit TS1 Ordered Sets with the Hot Reset bit >>> asserted and the configured Link and Lane numbers. >>> * Otherwise, after a 2 ms timeout next state is Detect. >>> >>> The next section has something similar for propagation of hot resets. >>> >>> Nowhere there does it say TS1 Ordered Sets need to be sent continuously >>> for 2ms. A hot reset is initiated only by two consecutive TS1 Ordered >>> Sets with the Hot Reset bit asserted. The 2ms timeout seems to be the >>> delay before the link moves to the Detect state after we stop asserting >>> hot reset. 1ms seems like more than enough time for two TS1 Ordered >>> Sets to propagate down a multi-level hierarchy at 2.5GT/s. >>> >> My original implementation is actually based on page 536 of the "PCI >> Express System Architecture". However based on the PCIe spec itself I >> think the point is that the port is supposed to stay in Hot Reset for >> 2ms after receiving the in-band message. For a bridge port it means >> that is supposed to be sending the Hot Reset message for those 2ms on >> all downstream facing ports. After the timer expires then it stops >> sending the Hot Reset TS1 Ordered Sets and then will transition to the >> Detect state. > Conveniently page 536 is available for preview on google :) What that > suggests to me is that the minimum "nobody home", unconnected link > timeout is 2ms. Downstream ports may exit to the Detect state after > either a 2ms timeout expires or after two hot-reset-TS1s are received > from the downstream device. The other 2ms case is that an upstream port > in the Hot Reset state will always wait for the 2ms timeout to expire > after the last pair of hot-reset-TS1s is received before entering the > Detect state. > >> My main concern here is that the previous code was not triggering a Hot >> Reset on all ports previously. What was happening was that some of the >> ports would only get as far as Recovery as the upstream port was only >> sending a couple of TS1 frames and not allowing the downstream ports >> time to switch to Recovery themselves and discover the Hot Reset. > Was that the original code that had no delay between set and clear of > the bridge control register? 1ms is pretty long time vs no delay. > >>>> The 1ms number you quote is the minimum time >>>> for a conventional PCI bus. I'm not completely sure of that applies as >>>> well to PCIe, nor does it represent the maximum recommended value. >>> Correct, 1ms comes from conventional PCI. PCIe is designed to be >>> software compatible with conventional PCI so it makes sense that PCIe >>> would do something within the timing boundaries of conventional PCI. I >>> didn't see any reference to a maximum recommended value for this >>> parameter. >> I don't want to implement things to minimum specification as there are >> too many marginal parts where the minimum doesn't work. I would rather >> not have to add a ton of quirks for all of the parts out there that >> didn't quite meet up to the specification. By using a value of 2ms we >> are matching what the PCIe bridge behavior is supposed to be by sending >> the Hot Reset TS1 ordered sets for 2ms. > The minimum requirement is 2 hot-reset-TS1. We're sending ~2.5 million > (if we can assume 1 per transfer cycle). Yes, but there are multiple states that must be transitioned through in order to get to the hot-reset state. >>>> If we stop early we risk not resetting the full device tree on the >>>> secondary bus which is the bug I was resolving by adding the 2ms delay. >>>> Previously we saw that some devices were only getting their PCIe link >>>> retrained without performing a hot reset when the bit was not held for >>>> long enough. I would prefer to keep this at 2 ms in order to account >>>> for the fact that PCIe has to go though link recovery states before it >>>> can perform the hot reset. >>> I'm not going to sweat over 1ms or 2ms but I do want to be able to >>> document why we're setting it to one or the other. If it's warm >>> fuzzies, so be it, but I'd prefer if we could find actual spec or >>> hardware examples to back it up. Thanks, >>> >>> Alex >> I think our difference is that I based my value on the in-band message >> behavior and your value is based on the recommended minimum time for the >> Secondary Bus Reset. The downstream ports of a bridge that receives the >> in-band Hot Reset notification are supposed to send a continuous stream >> of TS1 Ordered sets with the Hot Reset bit set for 2ms. Based on all of >> the conditions in the spec the device should start a 2ms timer, and all >> downstream ports should begin transmitting the TS1 Ordered sets with the >> Hot Reset bit asserted, then after the 2ms timer expires it should >> switch to the detect state. I verified with a PCIe analyzer that this >> was what the AER code was doing after I had changed it and added the sleep. >> >> What I found is that most parts will stop transmitting the TS1 ordered >> sets as soon as you clear the Secondary Bus Reset bit. > If what I state above is correct, then the downstream port of the Bridge > is able to immediately move to Detect after it receives two > hot-reset-TS1s from the downstream device. I suspect this is what you > were seeing. > >> So if you set >> the bit and clear it 1 ms later you might only get to send a few ordered >> sets and that may not be enough depending on how fast the part can >> transition between L0/L0s/L1, Recovery, and Hot Reset. > I would guess what you were seeing previously with a back-to-back > set/clear of the bridge control register was that the bridge never > really entered Hot Reset. Perhaps it wasn't even set long enough to be > latched into the hardware. As long as we get the bridge to enter Hot > Reset, I think the protocol takes care of itself. For example: > > root port switch endpoint > +-----+ +-----+ +-----+ > | X |<---A'----| Y |<---B'----| Z | > | |----A---->| |----B---->| | > +-----+ +-----+ +-----+ > > Say root port X makes it into the Hot Reset state and we have some way > to immediately detect this and clear the bridge control register. X > will still continue to send hot-reset-TS1 until either a) the 2ms timer > expires or b) it receives two hot-reset-TS1s on link A'. If link A is > up, switch Y will certainly receive two host-reset-TS1s within that 2ms > and enters the Hot Reset state on it's upstream port. Switch Y then > begins sending hot-reset-TS1s on link A'. At the same time, Y directs > it's downstream ports to enter Hot Reset "as soon as possible", and > begins sending hot-reset-TS1s on link B. Once X receives two > hot-reset-TS1s on link A', X enters the Detect state. hot-reset-TS1s on > link A cease. 2ms after the upstream port of Y receives the last two > hot-reset-TS1s, those ports also enter the detect phase. Are you sure about the flow of Hot Reset TS1 ordered sets along the A' and B' paths? My understanding was that the flowed downstream, not upstream. It's been so long ago that I don't have the trace with me from when I was working on this so I don't remember the exact behavior though so I could be wrong. The issue is that the secondary reset bit doesn't quite work like you have described. From what I have seen in the past setting the bit will hold the root port in the Hot Reset state with it pumping out the hot-reset TS1 ordered sets until we clear the bit. When we clear the bit then all of the ports will cascade from the Hot Reset state to detect. > The downstream port of Y behaves the same. We left off with Y's > downsteam port in Hot Reset sending hot-reset-TS1s down link B. It > continues to do this for 2ms or until two hot-reset-TS1s are received on > link B'. The protocol takes care of propagating the Hot Reset to > subordinate devices regardless of whether we're still directing the > original bridge to stay in Hot Reset. This is where I derived my 2ms value from. The simple thought is if the downstream ports wait 2ms before giving up why shouldn't we do the same for the Secondary Bus Reset bit. > If the above is a correct interpretation, the the only requirement on > how long we assert the secondary bus reset bit is how long it takes the > bridge to enter the Hot Reset state. Intuitively, 1ms seems like more > than enough time and is software compatible with conventional PCI which > is generally a design goal for PCIe. If we factor in link recovery > time, the maximum L1 latency is 64us, which is a pretty small fraction > of 1ms. 1ms should be more than enough for most parts, however if that is the case why do the downstream ports on most bridges have a 2ms timeout on Hot Reset? > Did you experiment at all with 1ms? I'm trying to come up with a reason > to make it 2ms, but the spec isn't supporting it. Maybe the comment > should be "This could probably be 1ms, but we're more comfortable with > 2ms.". Thanks, > > Alex I recall I did experiment with 1ms. It did reset the part I was working with. My concern as I recall was the fact that as soon as I cleared the secondary bus reset the root port stopped transmitting the hot reset ordered sets. The key thing that I think is the point of contention here between you and I is the line that "Software must ensure a minimum reset duration (Trst) as defined in the PCI Local Bus Specification". To me that is the lower bounds of acceptable values, and it seems like you are assuming that to be the recommended value. My preference is the 2ms value with a comment stating that the value can be no less than 1ms. This way it gives us a bit of wiggle room for any bus delays and such and we are more or less guaranteed to have at least 1ms with the bit set. If you go the 1ms route we really need a comment that we are running tight on the tolerance for the msleep since the spec says we must have at least 1ms. Thanks, Alex -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, 2013-08-08 at 09:46 -0700, Alexander Duyck wrote: > On 08/07/2013 10:23 PM, Alex Williamson wrote: > > On Wed, 2013-08-07 at 11:30 -0700, Alexander Duyck wrote: > >> On 08/06/2013 07:56 PM, Alex Williamson wrote: > >>> On Tue, 2013-08-06 at 16:27 -0700, Alexander Duyck wrote: > >>>> On 08/05/2013 12:37 PM, Alex Williamson wrote: > >>>>> The PCI spec indicates that with stable power, reset needs to be > >>>>> asserted for a minimum of 1ms (Trst). Seems like we should be able > >>>>> to assume power is stable for a runtime secondary bus reset. The > >>>>> current code has always used 100ms with no explanation where that > >>>>> came from. The aer_do_secondary_bus_reset() function uses 2ms, but > >>>>> that seems to be a misinterpretation of the PCIe spec, where hot > >>>>> reset is implemented by TS1 ordered sets containing the hot reset > >>>>> command. After a 2ms delay the state machine enters the detect state, > >>>>> but to generate a link down, only two consecutive TS1 hot reset > >>>>> ordered sets are requred. 1ms should be plenty for that. > >>>> The reason for doing a 2ms sleep is because the are supposed to be > >>>> sending the Hot Reset TS1 Ordered-Sets continuously for 2ms per all of > >>>> the documents I have read. > >>> Could you point to one of those references? In the PCIe v3 spec I'm > >>> seeing things like 4.2.6.11 Hot Reset: > >>> > >>> * If two consecutive TS1 Ordered Sets are received on any Lane > >>> with the Hot Reset bit asserted and configured Link and Lane > >>> numbers, then: > >>> * LinkUp = 0b (False) > >>> * If no higher Layer is directing the Physical Layer to > >>> remain in Hot Reset, the next state is Detect > >>> * Otherwise, all Lanes in the configured Link continue to > >>> transmit TS1 Ordered Sets with the Hot Reset bit > >>> asserted and the configured Link and Lane numbers. > >>> * Otherwise, after a 2 ms timeout next state is Detect. > >>> > >>> The next section has something similar for propagation of hot resets. > >>> > >>> Nowhere there does it say TS1 Ordered Sets need to be sent continuously > >>> for 2ms. A hot reset is initiated only by two consecutive TS1 Ordered > >>> Sets with the Hot Reset bit asserted. The 2ms timeout seems to be the > >>> delay before the link moves to the Detect state after we stop asserting > >>> hot reset. 1ms seems like more than enough time for two TS1 Ordered > >>> Sets to propagate down a multi-level hierarchy at 2.5GT/s. > >>> > >> My original implementation is actually based on page 536 of the "PCI > >> Express System Architecture". However based on the PCIe spec itself I > >> think the point is that the port is supposed to stay in Hot Reset for > >> 2ms after receiving the in-band message. For a bridge port it means > >> that is supposed to be sending the Hot Reset message for those 2ms on > >> all downstream facing ports. After the timer expires then it stops > >> sending the Hot Reset TS1 Ordered Sets and then will transition to the > >> Detect state. > > Conveniently page 536 is available for preview on google :) What that > > suggests to me is that the minimum "nobody home", unconnected link > > timeout is 2ms. Downstream ports may exit to the Detect state after > > either a 2ms timeout expires or after two hot-reset-TS1s are received > > from the downstream device. The other 2ms case is that an upstream port > > in the Hot Reset state will always wait for the 2ms timeout to expire > > after the last pair of hot-reset-TS1s is received before entering the > > Detect state. > > > >> My main concern here is that the previous code was not triggering a Hot > >> Reset on all ports previously. What was happening was that some of the > >> ports would only get as far as Recovery as the upstream port was only > >> sending a couple of TS1 frames and not allowing the downstream ports > >> time to switch to Recovery themselves and discover the Hot Reset. > > Was that the original code that had no delay between set and clear of > > the bridge control register? 1ms is pretty long time vs no delay. > > > >>>> The 1ms number you quote is the minimum time > >>>> for a conventional PCI bus. I'm not completely sure of that applies as > >>>> well to PCIe, nor does it represent the maximum recommended value. > >>> Correct, 1ms comes from conventional PCI. PCIe is designed to be > >>> software compatible with conventional PCI so it makes sense that PCIe > >>> would do something within the timing boundaries of conventional PCI. I > >>> didn't see any reference to a maximum recommended value for this > >>> parameter. > >> I don't want to implement things to minimum specification as there are > >> too many marginal parts where the minimum doesn't work. I would rather > >> not have to add a ton of quirks for all of the parts out there that > >> didn't quite meet up to the specification. By using a value of 2ms we > >> are matching what the PCIe bridge behavior is supposed to be by sending > >> the Hot Reset TS1 ordered sets for 2ms. > > The minimum requirement is 2 hot-reset-TS1. We're sending ~2.5 million > > (if we can assume 1 per transfer cycle). > > Yes, but there are multiple states that must be transitioned through in > order to get to the hot-reset state. > > >>>> If we stop early we risk not resetting the full device tree on the > >>>> secondary bus which is the bug I was resolving by adding the 2ms delay. > >>>> Previously we saw that some devices were only getting their PCIe link > >>>> retrained without performing a hot reset when the bit was not held for > >>>> long enough. I would prefer to keep this at 2 ms in order to account > >>>> for the fact that PCIe has to go though link recovery states before it > >>>> can perform the hot reset. > >>> I'm not going to sweat over 1ms or 2ms but I do want to be able to > >>> document why we're setting it to one or the other. If it's warm > >>> fuzzies, so be it, but I'd prefer if we could find actual spec or > >>> hardware examples to back it up. Thanks, > >>> > >>> Alex > >> I think our difference is that I based my value on the in-band message > >> behavior and your value is based on the recommended minimum time for the > >> Secondary Bus Reset. The downstream ports of a bridge that receives the > >> in-band Hot Reset notification are supposed to send a continuous stream > >> of TS1 Ordered sets with the Hot Reset bit set for 2ms. Based on all of > >> the conditions in the spec the device should start a 2ms timer, and all > >> downstream ports should begin transmitting the TS1 Ordered sets with the > >> Hot Reset bit asserted, then after the 2ms timer expires it should > >> switch to the detect state. I verified with a PCIe analyzer that this > >> was what the AER code was doing after I had changed it and added the sleep. > >> > >> What I found is that most parts will stop transmitting the TS1 ordered > >> sets as soon as you clear the Secondary Bus Reset bit. > > If what I state above is correct, then the downstream port of the Bridge > > is able to immediately move to Detect after it receives two > > hot-reset-TS1s from the downstream device. I suspect this is what you > > were seeing. > > > >> So if you set > >> the bit and clear it 1 ms later you might only get to send a few ordered > >> sets and that may not be enough depending on how fast the part can > >> transition between L0/L0s/L1, Recovery, and Hot Reset. > > I would guess what you were seeing previously with a back-to-back > > set/clear of the bridge control register was that the bridge never > > really entered Hot Reset. Perhaps it wasn't even set long enough to be > > latched into the hardware. As long as we get the bridge to enter Hot > > Reset, I think the protocol takes care of itself. For example: > > > > root port switch endpoint > > +-----+ +-----+ +-----+ > > | X |<---A'----| Y |<---B'----| Z | > > | |----A---->| |----B---->| | > > +-----+ +-----+ +-----+ > > > > Say root port X makes it into the Hot Reset state and we have some way > > to immediately detect this and clear the bridge control register. X > > will still continue to send hot-reset-TS1 until either a) the 2ms timer > > expires or b) it receives two hot-reset-TS1s on link A'. If link A is > > up, switch Y will certainly receive two host-reset-TS1s within that 2ms > > and enters the Hot Reset state on it's upstream port. Switch Y then > > begins sending hot-reset-TS1s on link A'. At the same time, Y directs > > it's downstream ports to enter Hot Reset "as soon as possible", and > > begins sending hot-reset-TS1s on link B. Once X receives two > > hot-reset-TS1s on link A', X enters the Detect state. hot-reset-TS1s on > > link A cease. 2ms after the upstream port of Y receives the last two > > hot-reset-TS1s, those ports also enter the detect phase. > > Are you sure about the flow of Hot Reset TS1 ordered sets along the A' > and B' paths? My understanding was that the flowed downstream, not > upstream. It's been so long ago that I don't have the trace with me > from when I was working on this so I don't remember the exact behavior > though so I could be wrong. I don't know for certain, my interpretation is purely from reading the spec. This is the only way I can make sense of (4.2.6.11): If two consecutive TS1 Ordered Sets are received on any Lane with the Hot Reset bit asserted and configured Link and Lane numbers,... The wording specifically uses "transmit" and "receive" and given that the links are bi-directional, I come to the above interpretation that both ends drive hot-reset-TS1s in both directions on the link. > The issue is that the secondary reset bit doesn't quite work like you > have described. From what I have seen in the past setting the bit will > hold the root port in the Hot Reset state with it pumping out the > hot-reset TS1 ordered sets until we clear the bit. When we clear the > bit then all of the ports will cascade from the Hot Reset state to detect. That's exactly how I describe. Once the upper layer stops directing the physical layer to stay in Hot Reset and two hot-reset-TS1s are received, the bridge immediately stops sending hot-reset-TS1s. This causes downstream devices to cascade into the Detect state. What I was trying to illustrate above is that regardless of how long we direct the physical layer to stay in Hot Reset, once it enters Hot Reset the protocol ensures that it cascades all the way down the chain. > > The downstream port of Y behaves the same. We left off with Y's > > downsteam port in Hot Reset sending hot-reset-TS1s down link B. It > > continues to do this for 2ms or until two hot-reset-TS1s are received on > > link B'. The protocol takes care of propagating the Hot Reset to > > subordinate devices regardless of whether we're still directing the > > original bridge to stay in Hot Reset. > > This is where I derived my 2ms value from. The simple thought is if the > downstream ports wait 2ms before giving up why shouldn't we do the same > for the Secondary Bus Reset bit. The downstream port has no way to confirm that the upstream port received the hot-reset-TS1s that the downstream port was sending. Using the example above, X sends hot-reset-TS1s down link A. X has positive confirmation that the downstream device Y has entered Hot Reset when it receives two hot-reset-TS1s on link A'. It can then exit early from the Hot Reset state if not held in Hot Rest by a higher layer. The downstream device Y has no such positive confirmation that X ever saw the hot-reset-TS1s that were pushed out through link A'. Thus, Y waits the full timeout after the last two hot-reset-TS1s before entering Detect. This is all from my interpretation of the spec, so it could be very wrong. For instance, the spec isn't clear on whether the hot-reset-TS1s being send on A' keep X in Hot Reset. That would obviously cause deadlock given my interpretation, so I assume not. > > If the above is a correct interpretation, the the only requirement on > > how long we assert the secondary bus reset bit is how long it takes the > > bridge to enter the Hot Reset state. Intuitively, 1ms seems like more > > than enough time and is software compatible with conventional PCI which > > is generally a design goal for PCIe. If we factor in link recovery > > time, the maximum L1 latency is 64us, which is a pretty small fraction > > of 1ms. > > 1ms should be more than enough for most parts, however if that is the > case why do the downstream ports on most bridges have a 2ms timeout on > Hot Reset? Without any response from the downstream device, the hardware is still going to do a full 2ms timeout, so what does it matter if we hold the device in Hot Reset for 1ms or 2ms? That translates to 3ms or 4ms of hot-reset-TS1s on a dead link. We're only allowing for an early exit if the link is live and the downstream device has entered Hot Reset. > > Did you experiment at all with 1ms? I'm trying to come up with a reason > > to make it 2ms, but the spec isn't supporting it. Maybe the comment > > should be "This could probably be 1ms, but we're more comfortable with > > 2ms.". Thanks, > > > > Alex > > I recall I did experiment with 1ms. It did reset the part I was working > with. My concern as I recall was the fact that as soon as I cleared the > secondary bus reset the root port stopped transmitting the hot reset > ordered sets. I think you would have to sever the return path (A') to see otherwise. As long as there are hot-reset-TS1s on link A', X is able to immediately transition to Detect. > > The key thing that I think is the point of contention here between you > and I is the line that "Software must ensure a minimum reset duration > (Trst) as defined in the PCI Local Bus Specification". To me that is > the lower bounds of acceptable values, and it seems like you are > assuming that to be the recommended value. > > My preference is the 2ms value with a comment stating that the value can > be no less than 1ms. This way it gives us a bit of wiggle room for any > bus delays and such and we are more or less guaranteed to have at least > 1ms with the bit set. If you go the 1ms route we really need a comment > that we are running tight on the tolerance for the msleep since the spec > says we must have at least 1ms. Ok, I can agree to that and I think the justification is more from adhering to the conventional PCI minimum timing rather than anything added by PCIe. 2ms is simply a fudge-factor to ensure that RST# on the bus is actually asserted for at least 1ms. I'll send an update. Thanks, Alex -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c index b204206..ba64a7e 100644 --- a/drivers/pci/pci.c +++ b/drivers/pci/pci.c @@ -3230,11 +3230,22 @@ void pci_reset_bridge_secondary_bus(struct pci_dev *dev) pci_read_config_word(dev, PCI_BRIDGE_CONTROL, &ctrl); ctrl |= PCI_BRIDGE_CTL_BUS_RESET; pci_write_config_word(dev, PCI_BRIDGE_CONTROL, ctrl); - msleep(100); + /* + * PCI spec v3.0 7.6.4.2 requires minimum Trst of 1ms. + */ + msleep(1); ctrl &= ~PCI_BRIDGE_CTL_BUS_RESET; pci_write_config_word(dev, PCI_BRIDGE_CONTROL, ctrl); - msleep(100); + + /* + * Trhfa for conventional PCI is 2^25 clock cycles. + * Assuming a minimum 33MHz clock this results in a 1s + * delay before we can consider subordinate devices to + * be re-initialized. PCIe has some ways to shorten this, + * but we don't make use of them yet. + */ + ssleep(1); } EXPORT_SYMBOL_GPL(pci_reset_bridge_secondary_bus);
The PCI spec indicates that with stable power, reset needs to be asserted for a minimum of 1ms (Trst). Seems like we should be able to assume power is stable for a runtime secondary bus reset. The current code has always used 100ms with no explanation where that came from. The aer_do_secondary_bus_reset() function uses 2ms, but that seems to be a misinterpretation of the PCIe spec, where hot reset is implemented by TS1 ordered sets containing the hot reset command. After a 2ms delay the state machine enters the detect state, but to generate a link down, only two consecutive TS1 hot reset ordered sets are requred. 1ms should be plenty for that. After reset is de-asserted we must wait for devices to complete initialization. The specs refer to this as "recovery time" (Trhfa). For PCI this is 2^25 clock cycles or 2^26 for PCI-X. For minimum bus speeds, both of those come to 1s. PCIe "softens" this requirement with the Configuration Request Retry Status (CRS) completion status. Theoretically we could use CRS to shorten the wait time. We don't make use of that here, using a fixed 1s delay to allow devices to re-initialize. Signed-off-by: Alex Williamson <alex.williamson@redhat.com> --- drivers/pci/pci.c | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html